[MGNLSSO-20] Decouple the module from Keycloak thanks to pac4j's own config by file Created: 08/May/20  Updated: 25/Mar/21  Resolved: 08/Feb/21

Status: Closed
Project: Single Sign On
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSSO-35 Allow Magnolia to be used as pac4j mi... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Initial description

Currently, pac4j configuration is done based off Magnolia YAML values. Maybe it would be easier (in the long run) to let pac4j be configured by its own config-by-file mechanism, as seen here: http://www.pac4j.org/4.3.x/docs/config.html

Ticket result

Thanks to the work done here, PD's SSO module is no longer coupled to Keycloak, but can be used with any 'OpenID Connect' Identity Provider. We have proved this in practice on the new cloud, where we have plugged the module to Okta. This is a big milestone for the module, making it ready to be published to the outside.



 Comments   
Comment by Maxime Michel [ 11/May/20 ]

I couldn't find any reference on how to do this in practice. Let's retry when/if it becomes urgent. Would be nice but for sure isn't critical.

Comment by Maxime Michel [ 28/Jan/21 ]

For the records, I just updated the link in the ticket description because it was pointing to pac4j 5.0 docs, and those do not have a section about '2) The pac4j-config module'. I believe the feature is still there, it's just been omitted from the latest documentation. The Maven module is still on the master branch and it doesn't appear in the list of features that got removed in the following page: http://www.pac4j.org/blog/what_s_new_in_pac4j_v5.html

Comment by Maxime Michel [ 29/Jan/21 ]

Found the URL in the 5.x docs: http://www.pac4j.org/docs/config-module.html

Generated at Mon Feb 12 10:50:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.