-
HI Michael,
To troubleshoot SAML, we might be able to find more information in tomcat logs, which is located usually in "/export/logs/orion/tomcat/tomcat/latest".
However, if you got more than one node in your environment, please check all nodes if possible.
Reply -
Hi Michael,
The logs are usually called callosum.log. They might be rotated to another name, but the naming convention would be the similar.
Reply -
Pei-Hsiang Vuong thank you. I ran a tail -f callosum.log
then I tried to saml authenticate.
I got error loggings.
Here are the important lines (I think)
org.apache.shiro.authc.AuthenticationException: LDAP naming error while attempting to authenticate user.
at org.apache.shiro.realm.ldap.AbstractLdapRealm.doGetAuthenticationInfo(AbstractLdapRealm.java:197)
Caused by: javax.naming.CommunicationException: ldap.state.in.us:389
...
Caused by: java.net.UnknownHostException: ldap.state.in.us
Reply -
Hi Michael,
This is more on the setup side. I believe you have a support ticket opened for this, please attach the error message there.
Reply
