How to configure OAM No-Cache Configuration Only For Authenticated Users And Not For Anonymous Users?
(Doc ID 1633999.1)
Last updated on AUGUST 09, 2018
Applies to:COREid Access - Version 10.1.4.3.0 and later
Information in this document applies to any platform.
There is a business requirement for Oracle Access Manager (OAM)-protected application pages to be served with the Cache Control HTTP Header set to no-cache only for authenticated users.
Customer want cache for only authenticated users and not for anonymous users. Currently we have set cache parameter as below.
Can OAM be configured to only set the Cache* headers for authenticated users and not for anonymous users?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!