Page Comparison

1. In Connection string, enter the URL of the LDAP server and base address in the directory service, for example:

   Panel
   title Example: Connection string
   Connection string: ldap://localhost:389/ou=NexusEmployees,dc=nexus,dc=local

   where

   ou = organizationalUnitName
   dc = domainComponent
   
   For more information on LDAP string attributes, see RFC 2253, LDAP (v3): UTF-8 String Representation of Distinguished Names.

2. In Username and Password, enter the Active Directory domain user name and password. 

1. Select Direct binding or With password comparison. Direct binding attempts to bind to the LDAP with the user entered. With password comparison the data of the LDAP entry is retrieved and the password is compared with the entered password.

2. Enter a Search pattern. Here are two examples:

   Panel
   title Example: Search pattern
   Search pattern: (userPrincipalName={0})

   
   

   Panel
   title Example: Search pattern using Distinguished Name (DN) of user
   Search pattern: cn={0},ou=users

   
   

3. If password comparison was selected, enter the Attribute for password used in LDAP and, if applicable, the mechanism that LDAP uses for Password encryption.

1. In Basis for group search, enter the subpath to the group information in LDAP.
   For example, if you find the group information under ou = groups, dc = myCompany, dc = de, enter the following:

   Panel
   title Example: Basis for group search
   Basis for group search: ou=groups

   
   

2. In Filter for group search, enter a filter expression, that defines the search starting with the subpath above.
   

   For example, if the group membership of users is stored in a multi-value attribute member (via the DN), enter the following:

   Panel
   title Example: Filter for group search
   Filter for group search: (member={0})

   
   

3. In Attribute for group, enter an attribute with unique values to define the group belonging. The groups to which the user belongs are compared in the last step with the assignment to the roles in the system and access to the system is assigned based on the assigned roles.

   For example, enter the following:

   Panel
   title Example: Attribute for group
   Attribute for group: cn

   
   

1. Go to the LDAP Group Permissions tab to map the LDAP groups to internal Identity Manager roles.
2. Click + to add an LDAP group to the Groups list
3. Select the roles that should be assigned to that LDAP group in the Roles list.
   
   

1. In Connection string, enter the URL of the LDAP server and base address in the directory service, for example:

   Panel
   title Example: Connection string
   Connection string: ldap://localhost:389/ou=NexusEmployees,dc=nexus,dc=local

   where

   ou = organizationalUnitName
   dc = domainComponent
   
   For more information on LDAP string attributes, see RFC 2253, LDAP (v3): UTF-8 String Representation of Distinguished Names.

2. In Username and Password, enter the Active Directory domain user name and password. 

1. Select Direct binding or With password comparison. Direct binding attempts to bind to the LDAP with the user entered. With password comparison the data of the LDAP entry is retrieved and the password is compared with the entered password.

2. Enter a Search pattern. Here are two examples:

   Panel
   title Example: Search pattern
   Search pattern: (userPrincipalName={0})

   
   

   Panel
   title Example: Search pattern using Distinguished Name (DN) of user
   Search pattern: cn={0},ou=users

   
   

3. If password comparison was selected, enter the Attribute for password used in LDAP and, if applicable, the mechanism that LDAP uses for Password encryption.

1. User Principal Name (UPN)
2. SAN Email (RFC822Name)
3. Subject CN
4. Subject Email
5. Object Security Identifier (objectSid)

1. In Connection string, enter the URL of the LDAP server and base address in the directory service, for example:

   Panel
   title Example: Connection string
   Connection string: ldap://localhost:389/ou=NexusEmployees,dc=nexus,dc=local

   where

   ou = organizationalUnitName
   dc = domainComponent
   
   For more information on LDAP string attributes, see RFC 2253, LDAP (v3): UTF-8 String Representation of Distinguished Names.

2. In Username and Password, enter the Active Directory domain user name and password. 

1. Enter a Search pattern. Here are two examples:

   Panel
   title Example: Search pattern
   Search pattern: (userPrincipalName={0})

   
   

   Panel
   title Example: Search pattern using Distinguished Name (DN) of user
   Search pattern: cn={0},ou=users

   
   

2. If password comparison was selected, enter the Attribute for password used in LDAP and, if applicable, the mechanism that LDAP uses for Password encryption.

1. In Basis for group search, enter the subpath to the group information in LDAP.
   For example, if you find the group information under ou = groups, dc = myCompany, dc = de, enter the following:

   Panel
   title Example: Basis for group search
   Basis for group search: ou=groups

   
   

2. In Filter for group search, enter a filter expression, that defines the search starting with the subpath above.
   

   For example, if the group membership of users is stored in a multi-value attribute member (via the DN), enter the following:

   Panel
   title Example: Filter for group search
   Filter for group search: (member={0})

   
   

3. In Attribute for group, enter an attribute with unique values to define the group belonging. The groups to which the user belongs are compared in the last step with the assignment to the roles in the system and access to the system is assigned based on the assigned roles.

   For example, enter the following:

   Panel
   title Example: Attribute for group
   Attribute for group: cn

   
   

1. Go to the LDAP Group Permissions tab to map the LDAP groups to internal Identity Manager roles.
2. Click + to add an LDAP group to the Groups list
3. Select the roles that should be assigned to that LDAP group in the Roles list.

1. User Principal Name (UPN)
2. SAN Email (RFC822Name)
3. Subject CN
4. Subject Email
5. Object Security Identifier (objectSid)

1. User Principal Name (UPN)
2. SAN Email (RFC822Name)
3. Subject CN
4. Subject Email
5. Object Security Identifier (objectSid)

1. In Identity template, select one or more core object types, for example, Employee and Contractor, on which the core object search will be performed. The first matching template will be used.
   
2. In User name field, select the core object field to match the user, for example UPN or Email. Identity Manager will use it to search the core object in the selected identity template.
   
3. In User display, enter fields in a comma separated list, for example FirstName,LastName. These fields are used to display the logged in user in Identity Manager Operator or Smart ID Self-Service.

1. You need one metadata file for each Service Provider, that is, one file for Identity Manager Operator, one file for Smart ID Self-Service and one file for other Service Providers that you configure.
2. You also need the metadata file of your Identity Provider and a keystore containing all the keys you would like to use for encryption or signing.

1. In Identity Provider Configuration:

   1. Upload a Configuration file 
      Here you can upload and delete the metadata file for an identity provider. The metadata file must contain only one identity provider configuration and no service provider configurations.

   2. Select an Attribute Type
      This is the identifying element of a SAML response. Despite the name, it can contain other elements than attributes. It can have two values, Name ID and Attribute Statement. Name ID refers to the subject of a SAML response, Attribute Statement refers to attributes associated with the subject of a SAML response.

   3. Enter Attribute Name
      This field is only active when Attribute Statement is selected as Attribute Type. It can be any arbitrary value.

2. In Keystore Configuration:
   1. Upload a Configuration file
      Here you can upload and delete key store file. The key store file must contain the certificates and the private key used for signing and decryption. A key store is mandatory.  When a key store is uploaded, the key store's password must be entered. Objects in the key store, if protected with a password, must have the same password as the key store itself.
   2. Available key aliases
      List of the aliases that mark private keys in the key store.
3. In Service Provider Configurations:
   
   1. Click on the + button to add a service provider. 
   2. This view lists the aliases of the service providers. Any arbitrary number of service providers is allowed but at least one service provider is required. An uploaded service provider must use only private keys available in the key store. If you upload a service provider metadata file that violates the SAML metadata schema, this triggers an error message.
4. In Service Provider Details:

   1. Alias
      In this context, Alias refers to the location and thus the service provider to use when sending the SAML response to the application for processing. An Alias is mandatory.
      
      This is an example of an excerpt from a typical metadata file that defines the Assertion Consumer Service responsible for processing the SAML response. The Alias in this case is "explorer".
      

      Code Block
      title Example: Excerpt from a metadata file
      ... <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="http://hostname:8080/prime_explorer/saml/SSO/alias/explorer" index="0" isDefault="true"/> ...

       

   2. Configuration File
      Click on the upload symbol and select the metadata file. 
      
      This field is mandatory. The metadata file must contain only one service provider configuration and no identity provider configurations. If the file is deleted and re-uploaded, Alias must be reset according to the metadata file.
   3. Alias for Signing Key
      The alias from the key store for the private key to use for signing. This field is mandatory.
   4. Alias for Encryption Key
      The alias from the key store for the private key to use for encryption purposes. This field is mandatory.

Optional:

Go to the Authentication Method tab and do the following settings:

1. In Authentication Method, click + to add the reference (AuthnContextClassRef) for the authentication method you want to add. You can find the reference in the Identity Provider, or in the SAML response. If a role has no AuthnContextClassRef assigned, the authentication method check will be skipped.

   This is an example of an AuthnContextClassRef snippet in a SAML response. (The value here is: urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport):  

   Code Block
   title Example: SAML response
   <saml:AuthnContext> <saml:AuthnContextClassRef> urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport </saml:AuthnContextClassRef> </saml:AuthnContext>

   
   These AuthnContextClassRef examples are based on OASIS Standard documentation. See https://docs.oasis-open.org/security/saml/v2.0/saml-authn-context-2.0-os.pdf for more information.

   Code Block
   title Examples: AuthnContextClassRef
   urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport urn:oasis:names:tc:SAML:2.0:ac:classes:Smartcard urn:oasis:names:tc:SAML:2.0:ac:classes:X509 urn:oasis:names:tc:SAML:2.0:ac:classes:TimeSyncToken urn:oasis:names:tc:SAML:2.0:ac:classes:MobileOneFactorContract

   
   

   Note
   Custom string can also be configured as an AuthnContextClassRef. See the Identity Provider configuration.

   
   

2. Map the added authentication method to a role by selecting the role you want to use and checking the check box for the authentication method.

   Note
   By mapping authentication methods to roles, you will restrict a user of certain roles depending on the authentication method used to log in. This adds an extra layer of security. If no authentication method is configured, all roles are allowed to be assigned to the user regardless of how the user is authenticated with the Identity Provider.