Configuration Data

Configuration data is required to be shared between Oracle Utilities Opower and the third-party partner:

• Information that the third-party partner provides to Oracle Utilities Opower: Prior to Oracle Utilities Opower setting up integration, the third-party partner must provide the redirect_uri for all applicable utilities and tiers relevant to the third-party partner. For a given utility and tier, this value is the URL that Oracle Utilities Identity and Access Management uses to return the authorization code. Identity and Access Management supports only a single URL, which must exactly match the one provided to the /authorize endpoint when the authorization code flow is initiated. For example, a redirect_uri would be of the format https://examplepartner.net/authenticate/redirect.
• Information that Oracle Utilities Opower provides to third-party partners for every client and tier:
  • List of endpoints:
    • The utility-specific OpenId Connect Discovery endpoint for the stage tier. Endpoints are of the format https://idcs-[INSTANCE_ID_Stage].oraclecloud.com/.well-known/openid-configuration.
    • The utility-specific OpenId Connect Discovery endpoint for the production tier. Endpoints are of the format https://idcs-[INSTANCE_ID_Production].oraclecloud.com/.well-known/openid-configuration.
  • Client credentials for a given utility and tier:
    • client_id
    • client secret
  • Scope management: The list of scopes that are allowed for the given utility and tier.