What it does:
- Adds users.
- Users who are added by PAP are given a role, primary group and secondary group by the PAP settings.
What it does not do:
- Remove users.
- Implement LDAP integration. This needs to be set up separately.
- Secure which users will get added. Anyone that has access to the URL, supplies their network username and password, and is LDAP authenticated will be given access to iDashboards provided there is an available license. (related to What it does #2)
- Control the number of licenses that get taken up. (related to What it does not do #3)
- Doesn’t map iDashboards groups to LDAP groups.
#PostAuthenticationProcessor code below
Please add the following lines to the ivizgroup.properties file to properly configure PAP: All lines are commented out with the '#' symbol. Please remove the '#' in order for the iDashboards server to read those lines.
#PostAuthenticationProcessor.connectionURL= ldap://<domain name>:389
#PostAuthenticationProcessor.default.USER_ROLE=<N, A, U, V>
#PostAuthenticationProcessor.default.PRIMARY_GROUP_ID=<Primary Group ID>
#PostAuthenticationProcessor.default.SECONDARY_GROUP_IDS=<Secondary Group ID>
#Other optional additions to the code:
#PostAuthenticationProcessor.connectionName=<username to connect to AD>
In smaller user account quantities the Post Authentication Process can cause your user that has been successfully authenticated in LDAP to not gain access to iDashboards if no licenses are available. This can result into a poor user experience.
- Enterprise Suite