[MGNLSSO-15] Add support for filtering params when requesting graph api Created: 13/Jan/20  Updated: 30/Jan/23  Resolved: 30/Jan/23

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

Type: Improvement Priority: Neutral
Reporter: Ondrej Chytil Assignee: Unassigned
Resolution: Outdated Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Team: AdminX

 Description   

Magnolia uses graph api for retrieving user group information from Azure. The graph API has filtering params but Magnolia makes the base url request(https://graph.microsoft.com/v1.0/me/memberOf) without any param added to it. 

When there are more than 100 group information for the user, magnolia ignores the second page of response and doesn't allows user login.

Magnolia must support filtering params, so the application doesn't have to process all the group response from Azure.



 Comments   
Comment by Pat Hills [ 31/Mar/20 ]

assign test

 

Comment by Lars Fischer [ 11/Aug/20 ]

Starting with version 2.6.7 I added a workaround that allows fetching 500 groups. I tested with having 200 groups on Azure and this works, I had no performance problems. Note that the memberOf API call does not support all query parameters.

Later I also created 200 groups on Magnolia to test if they are actually assigned (all created manually by myself).

Note: This module was and is experimental and meant as a blueprint for implementing your own solutions, there is no guarantee to support all existing environments because there are too many possible configurations.

Comment by Matt Rajkovic [ 30/Jan/23 ]

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

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