BOMGAR JUMP CLIENT LOGS PASSWORD

Inevat technicians have been using the Bomgar solution fmany ears and never looked back. Be aware if you use an external keyboard. The only way I can type is using the on-board keyboard with a half height window. I just hope Bomgar see's the bug and fixes it quickly as this version is next to unusable for me now. The old version worked great and I'm sure the future version should work as well. However since the IPAD is smart enough to know that I have an external keyboard it has nothing in that space unless I press the keyboard symbol on my external keyboard that then fills the empty space with the on-screen keyboard. Now, with this version, touching the keyboard symbol shrinks the viewable window in half and brings up an empty space where the keyboard would normally be. With the previous version I was able to touch the keyboard symbol in the app and it would allow my external keyboard to be used without issue.

I use an external BluTooth keyboard with the IPAD. My typical use is JumpClients and this version works very well with one new exception. LDAP Server for User Authentication and Group LookupBomgar IPAD app helps me with fast access to what I need. This would mean you configure something entirely separate from the RSA server as your LDAP group provider, and then configure RSA server as the security provider. Default Group Policy Each user who authenticates against an external server must be a member of at least one group policy in order to authenticat If you want users on this security provider to be associated with their groups on a separate LDAP server, choose one or more LDAP group servers to use for group lookup. One group security provider can be used to authorize users from multiple servers, including LDAP, RADIUS, and Kerberos. You then must enable group lookup from the user provider's configuration page. To define group policies based upon groups within a remote server, you must configure both the LDAP group provider and the RADIUS user provider. On Bomgar site, there is this note mentioned about doing Securid radius auths. We are not able to function as any LDAP or user sync or user lookup mechanism for Bomgar.

BOMGAR JUMP CLIENT LOGS PASSWORD

an incoming userid is valid and not locked out, and that whatever was in the password field is a passcode (pin+token) and we send back access-accept or access-reject (and we could append radius return attributes for that userid if needed). So be sure that you know the RSA server will only confirm if a user and passcode is valid. Went back and forth with Bomgar support and the customer, and indicated the RSA server only uses LDAP to confirm the userid for an incoming authentication, we will not do any sort of lookups to LDAP and provide outgoing data about LDAP.

I have worked on a case with another customer and Bomgar, and the type and setup of Bomgar they wanted required some sort of LDAP lookup from Bomgar through the device doing the 2-factor auth (the RSA server). as an RSA server cannot provide any sort of 'list of users' (unless you were using RSA admin api's and that would be on a TCP port). Your picture of log messages about 'syncing users'.that sort of functionality would be solely within the Bomgar device and it's own configuration. Refer to the article mentioned by Erica, it has detailed troubleshooting steps if radius user authentication is not working. Anything accessing the RSA server on port 1812 udp is only doing a single user radius authentication.there is no listing of users or 'syncing' anything else that occurs on port 1812 udp.

Bomgar jump client logs