SAML Single Logout Configuration Information

When implementing SLO, most clients choose to contract with a federation server provider and configure settings through the provider’s interface. Configuration details are provided below.

Oracle Utilities Opower SAML Information

Oracle Utilities provides the utility with SAML metadata for production and staging servers. The metadata provided by Oracle Utilities includes the following information:

• Oracle Utilities Opower SAML Entity ID
• Oracle Utilities Opower SLO URL

Information Required by Oracle Utilities from the Utility

Oracle Utilities requires that a Utility defines their SAML specification or extracts a SAML metadata definition, and provides either resource to Oracle Utilities. Refer to your IdP third-party documentation for steps on completing a SAML metadata extraction. The information in the specification or metadata file must include the following:

• Client SAML Entity ID: Same concept as the Oracle Utilities Opower entity ID.
• Client Public Key: Oracle Utilities requires the Public Key for the corresponding Private Key the utility is using to sign their SAML requests. SAML requires the Identity Provider to sign all requests submitted via POST with a Private Key. Oracle Utilities needs the Public keys to verify the requests were sent by the utility client.
• Client SAML SLO URL: This is required for SAML SLO. It is the URL to which Oracle Utilities will send SAML SLO messages.
• Logout Redirect URL: This is an optional parameter. It is the URL Oracle Utilities will redirect the user to after they click the Logout link or make requests to the Oracle Utilities Logout URL.