Customer wish to build an extension point in OpenAM for OAuth client validation and settings
Use Case 1: Leverage internal AD service accounts to act as OAuth clients in place of registering clients and having applications maintain two sets of application credentials. Additional information can be hardcoded, obtained from OAuth requests, obtained from OAuth group settings, and/or obtained from attributes on the service account object
Use Case 2: Leverage OAuth clients registered against existing in house solution as part of migration to ForgeRock AM. Validation and client lookup can be performed through REST calls or database lookup of the existing clients.
The goal is to allow existing OAuth client repositories to be leveraged to aid in product transition or to fulfill specialized use cases.