Table of Contents |
---|
...
A common path among these is CN=Users,DC=test,DC=windows,DC=frevvo,DC=com and that is what you can configure in the Users Base field.
How do I enable frevvo to retrieve users under nested AD groups (as opposed to just the users under the parent group)?
The solution is to include the string ":1.2.840.113556.1.4.1941:" as part of the groupMemberAttribute parameter of the LDAP connector in the frevvo.xml:
Code Block |
---|
<Parameter name="com.frevvo.security.ldap.groupMemberAttribute" value="member:1.2.840.113556.1.4.1941:" override="false"/> |
Can I have more than one LDAP tenant?
...
- The primary source of information is the log file. In most cases, the LDAP connector will try to indicate what the problem is in the logs. In the log file, look for lines with LDAPSecurityManager or LdapDao.
- It is useful to have an LDAP browser at hand, for instance, the Apache Directory Studio. With the browser you can:
- Check if the connection parameters that you configured in are correct.
- Run queries against LDAP and make sure that the expressions you configured in are correct and returning what you expect.
- If you can't spot the problem and need to contact frevvo support:
- Stop
- Go to <frevvo-home>/tomcat/logs/frevvo.log.
- Follow these steps to change the log level from INFO to DEBUG
- Restart
- Execute the steps that is causing problems.
- Send the log file (zip) to Live Forms support (support@frevvo.com) with a description of the problem.
- Restore the log level to INFO.
...