Ldap ad

Active Directory & LDAP

Before you begin:

  • This authentication method integrates with your company’s LDAP or AD infrastructure.
  • User authentication and user search requests will be directed to the LDAP/AD server.

  • Support for LDAP and AD has the following constraints:

    Constraint Description
    LDAP/AD user objects User objects must contain a user’s first name, last name, email address, and username.
    Changes to a user When changes are made to a user's name, email address, or username that are in your LDAP/AD system, the changes do not automatically propagate to RStudio Connect. However, the user information updates the next time that the user logs into RStudio Connect after the LDAP/AD update is made.
    Single bind When using single bind, the DN of a user must contain their username (i.e., it must utilize the UsernameAttribute). Using a different attribute for username, such as CN only to match the DN, may cause users to have to type their full name to log in. For example, it is not supported if the DN for a user is cn=SueJacobs, ou=People, dc=company, dc=com but their actual username is stored in the uid or SAMAccountName LDAP attribute. You must use double bind when the DN does not contain the username. If the DN doesn't contain a username, then use double bind.
    Single-bind searches When using single-bind configuration, the searches only include users who have previously logged in to RStudio Connect.
    Single-bind groups When using single-bind configuration, groups are not available.

The RStudio Connect Admin Guide provides configuration information and examples for the following supported on-premise Active Directory and LDAP options:

Additionally, the full list of external authentication options that are available are provided in the RStudio Connect Authentication Overview.