Uploaded image for project: 'Single Sign On'
  1. Single Sign On
  2. MGNLSSO-60

User attributes mapping should be more smart/flexible

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Neutral
    • 2.0
    • 1.1.1
    • None
    • None

    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

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              mmichel Maxime Michel
              mmichel Maxime Michel
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD