[MGNLSSO-37] Test integrating a foreign IDP into Keycloak, preferrably Azure Created: 31/Jul/20  Updated: 31/Jan/23  Resolved: 30/Jan/23

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

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

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Magnolia SSO w/ pac4j
Team: AdminX

 Description   

One of the assumptions we currently have about Keycloak is that we will be able to connect it to clients' identity providers, and that the users will get an easy access to Magnolia thanks to that.

But we have never tested that in practice. It would be interesting to do so:

  1. with an Azure setup because this is where we expect the most difficulty
  2. with actual data so that we see real-world problems


 Comments   
Comment by Matt Rajkovic [ 30/Jan/23 ]

Very old request - Closing. If needed, can be reopened.

Comment by Maxime Michel [ 31/Jan/23 ]

I just confirmed with Adrien this was actually solved on the PaaS. AzureAD into Keycloak (via SAML) into Magnolia via SSO module.

Comment by Matt Rajkovic [ 31/Jan/23 ]

Thanks a lot, mmichel

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