[MGNLSSO-60] User attributes mapping should be more smart/flexible Created: 01/Jun/21  Updated: 15/Jun/21  Resolved: 08/Jun/21

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

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

Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)

 Description   

Both with Google & Azure OIDC setups, we ended up in a situation where the user wasn't assigned a username or an email. Which leads to an NPE in SsoLoginFilter, e.g.: userDetails.put("name", profile.getUsername());

Two solutions:

  • either the module tries to be smart and automatically deduce a value based on what's available
  • or we open up the configuration to the end user

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