Why Do WebLogic-Deployed Applications Still Prompt For Login After Configuring OAM Security Provider For WebLogic Server?
(Doc ID 1183375.1)
Last updated on MARCH 08, 2017
Applies to:COREid Access - Version: 10.1.4.2 to 18.104.22.168 - Release: 10g to
Information in this document applies to any platform.
Login to the WebLogic Administration console using OAM credentials is successful.
However, Single Sign-On (SSO) to WebLogic-deployed applications is not working. The WebLogic-deployed applications always prompt for login even if authentication with OAM credentials has previously been performed for a different application in the same browser session. Some applications will not accept credentials valid for OAM authentication, despite the WebLogic-OAM integration.
1. How to configure custom Java applications deployed in WebLogic so that the OAM Provider/Connector in WebLogic is used by the applications for login?
2. How to configure WebLogic-OAM integration so that the login page from an OAM form-based authentication scheme is displayed for WebLogic-deployed application login instead of the application login page?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|