SAML Bindings

Identity Provider to Service Provider Binding

Oracle Utilities accepts SAML logout messages from Identity Providers using the HTTP POST Binding method. This means all SAML logout messages are sent as HTTP POST requests to the Oracle Utilities federation server. Oracle Utilities the use of HTTP POST and the browser transmits the SAML logout message to the Oracle Utilities federation server. For this reason, Oracle Utilities does not support Artifact Binding for SAML 2.0.

Service Provider to Identity Provider Binding

Oracle Utilities supports either HTTP Redirect Binding, or HTTP POST Binding when sending logout requests to the Identity Provider. By default, Oracle Utilities will use HTTP Redirect Binding. This means that when Oracle Utilities begins the SP Initiated SLO process, Oracle Utilities will issue an HTTP Redirect to the user’s browser directing them to the Identity Provider. The Identity Provider federation service will then receive an HTTP POST request from the consumer and initiate the Authorization process. Oracle Utilities does not support Artifact Binding on communication from Oracle Utilities to the Identity Provider.