Authentication Settings
{% if result %}
{{ result['msg'] }}
{% endif %}
- Enable LDAP Authentication
- Turn on / off the LDAP authentication.
- Type
- Select your current directory service type.
- OpenLDAP - Open source implementation of the Lightweight Directory Access Protocol.
- Active Directory - Active Directory is a directory service that Microsoft developed for the Windows domain networks.
- ADMINISTRATOR INFO
- Your LDAP connection string and admin credential used by PDA to query user information.
- LDAP URI - The fully qualified domain names of your directory servers. (e.g. ldap://127.0.0.1:389)
- LDAP Base DN - The point from where a PDA will search for users.
- LDAP admin username - Your LDAP administrator user which has permission to query information in the Base DN above. Not needed for Active Directory authentication.
- LDAP admin password - The password of LDAP administrator user. Not needed for Active Directory authentication.
- Active Directory domain - Active Directory domain used.
- FILTERS
- Define how you want to filter your user in LDAP query.
- Basic filter - The filter that will be applied to all LDAP query by PDA. (e.g. (objectClass=inetorgperson) for OpenLDAP and (objectClass=organizationalPerson) for Active Directory)
- Username field - The field PDA will look for user's username. (e.g. uid for OpenLDAP and sAMAccountName for Active Directory)
- Group filter - The filter that will be applied to all LDAP group queries by PDA. (e.g. (objectClass=groupOfNames) for OpenLDAP)
- Group name field - The field PDA will look for group names. (e.g. member for OpenLDAP)
- GROUP SECURITY
- User can be assigned to PDA's User or Admin group by matching following LDAP Group.
- Status - Turn on / off group security feature.
- Admin group - Your LDAP admin group.
- Operator group - Your LDAP operator group.
- User group - Your LDAP user group.
Fill in all the fields in the left form.
Make sure you add PDA redirection URI (e.g http://localhost:9191/google/authorized) to your Google App Credentials Restriction.
Fill in all the fields in the left form.
Fill in all the fields in the left form.
You first need to define an Application Registration in your Azure Active Directory, with the appropriate HTTPS URL for this endpoint, and with the appropriate rights, as explained in the documentation.
- Under the Azure Active Directory, select App Registrations, and create a new one. Give it any name you want, and the Redirect URI shoule be type 'Web' and of the format https://powerdnsadmin/azure/authorized (replace the host name approriately).
- Select the newly-created registration
- On the Overview page, the Application ID is your new Client ID to use with PowerDNS-Admin
- On the Overview page, make a note of your Directory/Tenant ID - you need it for the API URLs later
- Ensure Access Tokens are enabled in the Authentication section
- Under Certificates and Secrets, create a new Client Secret. Note this secret as it is the new Client Secret to use with PowerDNS-Admin
- Under API Permissions, you need to add permissions. Add permissions for Graph API, Delegated. Add: email, openid, profile, GroupMember.Read, User.Read and possibly User.Read.All. You then need to grant admin approval for your organisation.
- For the Scope, use User.Read openid mail profile
- Replace the [tenantID] in the default URLs for authorize and token with your Tenant ID.
Fill in all the fields in the left form.