Hi,
Previously I have RT::Authen::OAuth2 working with RT 4.4.1 with no problems. I am testing an upgrade to RT 6.0.0. Everything seems to be working well except for OAuth2. Using the configuration in RT-Authen-OAuth2/etc/OAuth2_Config.pm that was working in RT 4.4.1, RT 6.0.0 just bounces back to the Login screen after authenticating with the IdP successfully. The log shows the following line with no other errors:
Successful OAuth2 login for XXXX@cornell.edu from XXX.XXX.XXX.XXX
Does anyone have RT::Authen::OAuth2 working with RT 6.0.0? Any ideas is appreciated.
Yes!
Co-incidentally I’ve been working on switching our RT 5.0.8 site over to using only Authentik SSO.
The current release of RT::Authen::OAuth2 was a bit limited - it could add new users, but our setup requires users to be in certain groups for access to various RT queues etc.
So I added a few new features, so it can get the group information from the Identity Provider (if it supports groups), and do various other things, including disabling any existing RT password after a successful SSO login etc.
RT6 has changed the way sessions are created:
https://docs.bestpractical.com/rt/6.0.0/Developer-UPGRADING-6.0.html
It needed a few lines of code shoving in just after it creates the new session, so it actually gets saved.
If you want to test out my version of RT::Authen::OAuth2:
Hi Rob,
I didn’t try the new features, but I can confirm your version fixed compatibility issues with RT 6.0.0. I am using Globus Auth (Globus Auth service) as the idP.
Thank you!
Steven
1 Like