Any plans for oAuth 2.0/OpenID Connect 1.0 or SAML 2.0

Aloha! I think there’s definitely interest in doing so. Primarily we follow the needs of our own institution (hawaii.edu), but we’re also a member of the InCommon Federation so we tend to follow the larger trends. I can check in with them to see what their roadmap is.

What’s your timeline for your migration, and do you have any docs or best practices for doing the authentication handshaking in PHP? Having access to a test oAuth2 or SAML2 server might help too. I think the ideal case is bundling a 3rd party library in Authorizer, since that’s already what we do for CAS and Google authentication:
https://github.com/apereo/phpCAS
https://github.com/googleapis/google-api-php-client

FYI we have a github issue tracking this, but it’s a little stale:
https://github.com/uhm-coe/authorizer/issues/32

Thanks, so much for the quick response @figureone! I don’t have details on the SSO change timetable or best practices, so I’m going to share this thread with my colleagues that are working on these SSO changes so that they can respond with the pertinent info. Thanks again and have a great weekend!

Aloha, just updating that we have a pre-release version (3.0.1) of authorizer available at github for testing.
https://github.com/uhm-coe/authorizer/archive/master.zip

We’ve been coordinating with your IAM folks so hopefully they will be able to test soon.
https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app

Cheers!