Tips for debugging the DevPortal OpenID Connect module

We have configured our developer Portal with Open ID connect using our VDS IDP . It has been working very well. However we are seeing issues with different users and in different browsers where the login will not work. The user will hit the login button and you can see the the browser url change to IDP then back to developer Portal URL with no change. There isn't an error displayed but just goes back to developer portal home page with the User not logged in. Same user can use a different browser (Chrome/Safari) and login successfully. Our IDP sees the flow in their logs as successful so we would like to see some debug logging from the Open ID Connect module but don't know if that is possible or if there may be other logs we are not aware of that would help figure out the issue. Another variable is that we went from 4.17.05 to 4.17.09 and changed from the tar based (apache) install to RPM (nginx).

Thanks in advance for any insight on this and debugging techniques.

0 1 102
1 REPLY 1

Seems it may be related to the apache TAR based install using MySQL as underlying database and RPM/nginx using Postgres . The subject that is getting passed for Liberty IDs is n# or N# dependending on browser. Seems that Postgres is case sensitive and MySQL is not. So only one browser type will work now. Still trying to debug but wondering in OpenID Connect module may need to be modified to force a case.