Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
ldap [2021_01_14 01:13] – steven | ldap [2024_03_05 19:11] – [LDAP Integration] steven | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | # LDAP Integration |
- | See also [[iam]]. | + | #### Last Updated January 7, 2022 |
- | To setup LDAP integration | + | The Access Anywhere supports |
- | In your account you can add multiple | + | This document describes integration with LDAP. For SAML see [[: |
- | ===== Setup Authentication Provider ===== | + | This document describes configuration via LDAP for: |
- | From the dropdown list select LDAP provider {{:/ | + | * Microsoft Active Directory |
+ | * Azure AD Domain Services | ||
- | You can complete | + | <WRAP center round important 100%> |
+ | If you remove an authentication system that is in use by an SMB Multi User or Nasuni provider, | ||
+ | </WRAP> | ||
- | ==== Connection Settings ==== | ||
- | **Auth System Name:** This will be the displayed name of the ldap system when importing users **LDAP Server host or IP:** The IP or hostname of the LDAP server **LDAP Server port:** The port to use default is 389 **Connection Encryption: | ||
- | ==== Users Import Settings ==== | ||
- | **Update user roles/ | + | ### Adding |
- | **Use Custom User Email Field:** By default mail or email field will be used. By selecting this checkbox you can use a custom filed for email mapping. | + | Directory services are managed by an Organization administrator under **Organization** \> **Auth Systems**. Multiple auth systems |
- | **Group (Role) Id Field:** The group mapping to use. | + | {{ :iam: |
- | **Restrict import of users from the following groups:** Restrict import of users to a certain groups | + | ## Active Directory (via LDAP) |
- | **Group (Role) Object Class:** The Group class to use | + | If you need to connect to: |
- | **Custom Group (Role) Object Classes:** You can enter multiple Group classes separated by comma. | + | * ADFS (Active Directory Federation Services) - see [[organisationcloud/ |
+ | * Azure Active Directory - see [[organisationcloud/ | ||
+ | * Active Directory without secure LDAP - see the [[: | ||
- | **Role Name Field:** The field to use for role mapping. You can enter custom field for by selecting //Use Custom Role Name Field// | + | ### Choose Auth System Type |
- | ===== Importing Users and Roles ===== | + | For any LDAP directory service choose **Active Directory via LDAP**. |
- | After LDAP and the SME Cloud File Server have been successfully connected navigate to the " | + | {{ : |
- | {{:/ | ||
- | ===== Choosing Users to Import ===== | + | ### Connection Information |
+ | The first section provides connection information | ||
- | Select the recently added auth system from the dropdown list if you have added more than one auth systems. | + | {{ ::ldap_ad_auth_connsettings.png?600 |}} |
- | Once the users from LDAP are visible users can be selected for import (and roles separately if required) from the set by selecting the role drop down. If multiple roles are required choose shift-select to select more than one role. | + | __Auth System Name__ |
- | {{:/LDAP:.: | + | __LDAP Server host or IP__ - This is the dns resolvable hostname, or the IP address for your AD servers which are listening for LDAP connections. |
- | When complete click the " | + | For high availability you can enter multiple addresses. Enter the host like you would normally then subsequent hosts separated by a space and include the protocol. |
+ | |||
+ | ``` | ||
+ | server1 ldap:// | ||
+ | ``` | ||
- | The SME user login ID will be **username@orgname** | + | In case NAA can not connect to the first AD, next one will be tried. |
- | ===== Importing Roles Directly ===== | + | __LDAP Server Port__ - Can leave the default (port 389) if the Connection Encryption is none or TLS. Use port **636** for SSL. Or other port if you are using non-standard ports for your AD environment. |
- | If the Cloud File Server users have been setup directly it is still possible to import roles separately from Active Directory. To do this login as the Cloud Administrator on the web, click on the Roles menu option in the right sidebar and click the link, " | + | __Connection Encryption__ - Select the encryption method your AD environment supports. |
- | {{:/LDAP:.: | + | __Base DN__ - Enter the Base DN for your enviornment. This is dependent on your AD environment setup. |
- | ===== Managing Users and Roles ===== | + | __Administrator User DN__ - Enter the DN for a service account in your AD environment that we will use to connect. |
- | User role mappings can be managed from the User option | + | __Administrator |
- | ===== Assiging Permissions to Roles ===== | + | ==== User Import Settings |
- | Once Users and Roles are set up then permissions can be set against | + | The next three boxes should |
- | * At a Folder lever | + | If you do not check these, you must import the Users and Roles you want to have access to the system. |
- | * At a Roles level | + | {{ : |
- | * At a user level | + | |
- | The precedence is applied in the following order (lowest first) | + | ==== User Directory Settings ==== |
- | | + | The next section will describe how your directory defines the users we will use in Access Anywhere. |
- | * Role permissions | + | |
- | * User permissions | + | {{:: |
+ | |||
+ | __User Object Class__ - For Active Directory we will select " | ||
+ | |||
+ | __Additional Custom User Object Classes__ - If you have additional classes which represent the users on your system, you can enter them here in a comma separated list. Standard AD installations will leave this blank. | ||
+ | |||
+ | __Login Field__ - This defines the attribute which NAAwill use for the NAALogin attribute in Access Anywhere. Standard AD installations should use either sAMAccountName or userPrincipalName | ||
+ | |||
+ | __Use Customer User Login Field__ - If Checked then you can select a custom field for the NAALogin. Standard AD installations will leave this blank. | ||
+ | |||
+ | __Unique User Attribute__ - This defines which field will be used as the unique user ID with Access Anywhere. Standard AD installations should use either sAMAccountName or userPrincipalName. | ||
+ | |||
+ | __User Name Field__ - This defines which field will be used for the NAAUser Name attribute. Standard AD installations should use displayName. | ||
+ | |||
+ | __Use Custom User Name Field__ - If Checked then you can select a custom field for the NAAUser Name. Standard AD installations will leave this blank. | ||
+ | |||
+ | __Use Custom User Email Field__ - If Checked then you can select a custom field for the NAAemail. Standard AD installations will leave this blank. | ||
+ | |||
+ | ==== Group Directory Settings ==== | ||
+ | |||
+ | The next section will describe how your directory defines the groups we will use for the roles within Access Anywhere. | ||
+ | |||
+ | {{:: | ||
+ | |||
+ | __Group (Role) id Field__ - This will define which field to use in the directory to create the Roles within Access Anywhere. Standard AD installations will select cn. | ||
+ | |||
+ | __Restrict import of users from the following groups__ - Enter any group DNs for groups within your directory which you want to limit which users can access Access Anywhere. | ||
+ | |||
+ | __Group(Role) Object Class__ - This defines the object class the directory users for group objects. Standard AD installations will select group. | ||
+ | |||
+ | __Custom Group (Role) Object Classes__ - Here you can add additional classes which represent groups in your Directory, in a comma separated list. Standard AD installations will leave this blank. | ||
+ | |||
+ | __Role Name Field__ - This defines which field will be used to set the Group name in Access Anywhere. Standard AD installations will use cn. | ||
+ | |||
+ | __Use Custom Role Name Field__ - If checked then you will be able set a custom field name to be used for Access Anywhere group Names. Standard AD installations will leave this blank. | ||
+ | |||
+ | ==== Auto-Config Provider (Optional) ==== | ||
+ | |||
+ | This optional setting will allow you to define Private Providers for each user in your directory. This can be used for user home directories for example. | ||
+ | |||
+ | |||
+ | ## Azure AD Domain Services (via LDAP) | ||
+ | |||
+ | Azure AD Domain Services can be used as an LDAP provider. | ||
+ | |||
+ | We recommend enabling and configuring Secure LDAP using TLS with port 389. (You could also use SSL with port 636). | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Other Settings: | ||
+ | |||
+ | * User Object Class: user | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | * User Name Field: cn | ||
+ | |||
+ | * Group (Role) Id Field: cn | ||
+ | |||
+ | * Group (Role) Object Class: group | ||
+ | |||
+ | * Role Name Field: cn | ||
- | Where a user is in multiple roles then least restrictive permissions apply. | ||
- | {{:/ | ||
- | ===== User Login ===== | ||
- | Once the users have been setup they can login directly using their normal LDAP to login through the SME Cloud File Server. On login their user credentials are sent to LDAP if the user is authorised then this is passed back to the SME Cloud File Server which issues a token for access. This token will then be used for SME File Server access for the users sessions and will be passed with each request. | ||