Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-16416

AM/IDM integration should not use realm oauth2provider service

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 7.0.0
    • Fix Version/s: None
    • Component/s: IAM
    • Labels:

      Description

      At the moment, the AM/IDM integration relies on the OAuth2Provider service settings. However, I customer may want to configure their external-facing OAuth2 AS differently to settings that would be compatible with this integration.

      The AM/IDM integration OAuth2 functionality should be fulfilled by internal oauth clients (a different agent/application type?), and an internal set of OAuth 2 AS settings, in the same way as we do so for Java and Web Agents.

      This would then allow customers to change the settings of their external OAuth2 AS without impacting the AM/IDM integration. It would also substantially simplify the CDM/FRaaS base configurations.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jamesphillpotts James Phillpotts
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: