...
- set security.auth.kerberos and naming.ldap parameter values to true
- update the security.auth.kerberos.realm parameter value to the Kerberos realm to use if the user does not enter it in the CAST Engineering Dashboard/Discovery Portal login screen. E.g.:CORP INTERNAL.MYCOMPANY.COM
- update the security.auth.kerberos.kdc parameter value with the name of the server that hosts your Key Distribution Center
- update the security.auth.login.config parameter value with the path where you deployed the Web application or if you decided to store the login module configuration file in a different directory
- update the security.auth.login.client parameter value
- update the naming.ldap.url paramater value with the URL of your Active Directory (LDAP). E.g.:
...
- Your Active Directory and Kerberos are likely to be case sensitive: use extra care when entering the configuration details
- You can activate the integration with Kerberos alone. In this case, Kerberos will serve to authenticate the user trying to log in to the CAST Engineering Dashboard/Discovery Portal and the user name entered will be use to enter the CAST Engineering Dashboard/Discovery Portal (you will therefore need to declare your user in the CAST Engineering Dashboard. E.g.: USER@CORPUSER@INTERNAL.CASTSOFTWAREMYCOMPANY.COM
- You can activate the integration with Active Directory (LDAP) alone. In this case, the authentication is performed by Active Directory (LDAP) as the entered user name and password will be used to log in to the Active Directory.
...