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 188.8.131.52 - 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?
NOTE: This document does not cover configuration of other Oracle application products deployed in WebLogic Server with OAM e.g. Oracle WebCenter. For details of how to configure Oracle application products with OAM please reference the product-specific documentation e.g. the Oracle WebCenter product documentation.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!