How to Configure SAML2 SP SSO when Applications are Deployed to Different Managed Servers using a Web Server as Front End

(Doc ID 1904991.1)

Last updated on DECEMBER 12, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.


The goal of this note is to explain the steps to configure SAML2 Service Provider (SP) when two or more applications are running on different managed servers. For example, an application called App1 is deployed to a managed server MS1 and another application called App2 is deployed to a managed server MS2. In addition, the requests are coming through a web server (like OHS or Apache).

Please note that this note does not explain all the steps to configure SAML2. If you need the steps for the whole configuration of SSO with SAML, please refer to the following Documentation:

Oracle® Fusion Middleware Securing Oracle WebLogic Server
11g Release 1 (10.3.6)
Part Number E13707-09
Chapter 7 Configuring Single Sign-On with Web Browsers and HTTP Clients
Configuring SAML 2.0 Services


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms