...
Note |
---|
Yarngate MUST use a LDAP authentication policy, local DB authentication policy cannot be used and if configured the Yarngate service will not start |
Yarngate Authentication Database
Create an authentication database
Name the LDAP authentication database
Configure the required roles
Configure the required roles for yarngate it is expected that there would be both a Yarngate-Admin and Yarngate-User. These permissions control what options are availible in the yarngate application after a user is Authenticated and Authorised. Repease this process for as many roles as required
Yarngate Authentication Policy
Create Authentication Policy
Name the authentication policy and select Authentication Method LDAP + Database with Roles
Select Linked authentication Database created previously for Yarngate
Configure LDAP authentication
The LDAP server address should be in the format LDAPS://<FQDN>:<port> - Note that LDAP:// can be used but passwords will not be encrytped in transit
Verify TLS/SSL certificates can be enabled - Note that the LDAPS server certificate or trusted root CA certificate must be uploaded via the administration app
LDAP username match regex can be used to match username formats - This is a generic username match regex that can be adjusted as needed(^[A-Za-z0-9]+(?:[ _-][A-Za-z0-9]+)*$)
LDAP replace regex allows to adding prefixes/suffices to suite the authentication requirements such as adding a domain suffix
Save the authentication policy - Note that new tabs will now become visable
Configure LDAP authorisation and roles
The LDAP interface field is optional - this can be used if an out of band check using another LDAP user is required for LDAP user group search on LDAP, If this option is not selected the LDAP groups are retreived using the authenticated LDAP user
Base DN - provide the base DN for LDAP searches
Username Match Field - this is the LDAP username field used typically sAMAccountName
LDAP group to role mapping - this provide a mapping from LDAP groups to the Autentication Database roles defined previously. The LDAP groups can be entered in as global group name of LDAP distingushed name
Configure Yarngate Service and Browser Access
Infonote |
---|
It is recommended to add a local authentication administration app on a dedicated port if LDAP access will be used on the default HTTPS TCP/443 access - The process is described hereAdding Secondary Local Auth Administration Access as this provides access to yarnman incase of LDAP issues. The following process assumes that LDAP authentication will be used for the default proxy and administration application |
...