Skip to main content

WebLogic (SP-initiated) Integration Guide


Use this guide to enable Multi-Factor Authentication and Single Sign-on (SSO) access via SAML to Oracle WebLogic.


1. Have a WebLogic account

2. Ensure the SAML SSO is enabled before configuring SecureAuth IdP

Contact the Oracle administrator to enable SAML SSO

3. Create a New Realm for the WebLogic integration

4. Configure the following tabs in the Web Admin before configuring the Post Authentication tab:

  • Overview – the description of the realm and SMTP connections must be defined

  • Data – an enterprise directory must be integrated with SecureAuth IdP

  • Workflow – the way in which users will access this application must be defined

  • Multi-Factor Methods – the Multi-Factor Authentication methods that will be used to access this page (if any) must be defined

SecureAuth IdP Configuration Steps



1. In the Profile Fields section, map the directory field that contains the user's WebLogic ID to the SecureAuth IdP Property

For example, add the WebLogic ID Field to the Email 2 Property if it is not already contained somewhere else


Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes

Post Authentication


2. Select SAML 2.0 (SP Initiated) Assertion Page from the Authenticated User Redirect dropdown in the Post Authentication tab in the Web Admin

3. An unalterable URL will be auto-populated in the Redirect To field, which will append to the domain name and realm number in the address bar (Authorized/SAML20SPInit.aspx)

4. A customized post authentication page can be uploaded, but it is not required

User ID Mapping


5. Select the SecureAuth IdP Property that corresponds to the directory field that contains the WebLogic ID (Email 2)

6. Select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified from the Name ID Format dropdown (default)

Select a different option if WebLogic requires it, which the Service Provider (SP) will provide

7. Select False from the Encode to Base64 dropdown

SAML Assertion / WS Federation


8. Set the SAML Consumer URL to the value provided by WebLogic

9. Set the WSFed/SAML Issuer to the Fully Qualified Domain Name (FQDN) of the SecureAuth IdP appliance, which will be shared with WebLogic, e.g. https://secureauth.<company>.com

The WSFed/SAML Issuer must match exactly on the SecureAuth IdP side and the WebLogic side

10. Set the SAML Recipient to the value provided by WebLogic

11. Set the SAML Audience to https://wls01.<domain>.com:7001/saml2

12. Provide the SP Start URL to enable SSO and to redirect users appropriately to access WebLogic

For example, the SP Start URL would be https://wls01.<domain>.com/app01/app.jsp

13. Set the SAML Offset Minutes to make up for time difference between devices

14. Set the SAML Valid Hours to limit for how long the SAML assertion is valid


No configuration is required for the WSFed Reply To/SAML Target URL field


15. Leave the Signing Cert Serial Number as the default value, unless there is a third-party certificate being used for the SAML assertion

If using a third-party certificate, click Select Certificate and choose the appropriate certificate

16. Provide the Domain in order to Download the Metadata File, which will be sent to WebLogic


Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changes

Forms Auth / SSO Token


Optionally, in the Forms Auth / SSO Token section, click the View and Configure FormsAuth keys/SSO token link to configure the token/cookie settings and configure this realm for SSO.

WebLogic Configuration Steps

Once Oracle has enabled SAML SSO and provided the information for the SecureAuth IdP configuration, contact Oracle and provide to them the Signing Certificate (step 15) and the Metadata File (step16) to complete the integration.