Does OWSM Cache Authentication Results for a Username Token Service Policy?
(Doc ID 1633878.1)
Last updated on AUGUST 01, 2023
Applies to:
Oracle Web Services Manager - Version 11.1.1.4.0 to 11.1.1.7.0 [Release 11gR1]Information in this document applies to any platform.
Symptoms
WebLogic plus OWSM.
A Web Service is secured with a username+token based OWSM policy such as oracle/wss_username_token_service_policy.
The users accessing the Web Service are stored in a non-default LDAP provider configured as an Authentication Provider.
Caching is enabled for this non-default LDAP provider.
Despite the caching settings, for each Web Service request carrying a username token, there is an LDAP bind.
Cause
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
| Symptoms |
| Cause |
| Solution |
| Caching is configured in the LDAP provider configuration in the WebLogic Server (WLS) Admin Console |
Authentication results are NOT cached |
| References |