Hi Kyra, > I'm not sure the problem is the OIDC authentication protocol. The problem could be in any component, so you will need to look into all of them. I suggest it might be OIDC only because of my suspection, I don't actually have solid reason to support myself......
As for the log, The tomcat debug log won't give you too much detail even for yourself, you need to enable CAS debug log. You can see how to enable it here: https://apereo.github.io/cas/6.0.x/installation/Troubleshooting-Guide.html#review-logs CAS Debug log will be formatted something like the following: 2018-07-28 24:12:25,879 DEBUG [org.apereo.cas.services.DefaultServiceRegistryExecutionPlan] - <Registering service registry [OAuth20Ser viceRegistry] into the execution plan> 2018-07-28 24:12:25,836 DEBUG [org.apereo.cas.services.AbstractServicesManager] - <Registering service registry [OAuth20ServiceRegistry ] into the execution planorg.apereo.cas.services.ChainingServiceRegistry@ 7a9f1582]> ........ So there will be more information for you to examine. -Andy -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/877246cf-7b9c-44ff-a33c-95a8d1908efe%40apereo.org.
