Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 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 FrevvoJNDIRealm.
  2. It is useful to have an LDAP browser at hand, for instance, the Apache Directory Studio. With the browser you can:
    1.  Check if the connection parameters that you configured in  are correct.
    2.  Run queries against LDAP and make sure that the expressions you configured in   are correct and returning what you expect.
  3. If you can't spot the problem and need to contact frevvo support:
    1. Stop 
    2. Go to <frevvo-home>/tomcat/logs/frevvo.log.
    3. Follow these steps to change the log level from INFO to DEBUG
    4. Restart 
    5. Execute the steps that is causing problems.
    6. Send the log file (zip) to Live Forms support (support@frevvo.com) with a description of the problem.
    7. Restore the log level to INFO.

Below are some common cases to help with troubleshooting. All of them assume that the connectivity is working, meaning that you tested, from the same box where  is running and that the connection parameters to the LDAP server you configured in  are correct. 

...

Another potential issue is case sensitivity. Please refer to the topic Mixed or Upper case User Names  topic.

A user that should be an administrator logs in but can't manage the tenant

...

Another potential issue is case sensitivity. Please refer to the topic   Mixed or Upper case User Names topic.

I can authenticate against LDAP via the Live Forms login page but SSO is not working

...