Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 12.1.4, 184.108.40.206, 12.1.5, 220.127.116.11, 18.104.22.168, 22.214.171.124, 12.1.6
Opened: Oct 21, 2013
Related Article: K51400321
Pressing the 'Clear Local Config Cache' button on the Access :: Oracle Access Manager properties page, will delete the /config/aaa/oam/config.cache file.
Pressing the 'Clear Local Config Cache' button will incorrectly delete the template file, but not the actual local config.cache generated for the configured AccessGate. Deletion of the template file has no impact to the admin or the system. However, since the system does not delete the correct file for a specific AccessGate, the system will not force Access Policy Manager to bootstrap the AccessGate, nor will it be reinitialized against the OAM access server.
When Oracle Access Manger is configured along with one or more AccessGates, the system generates a config.cache file under a file path that includes Partition and AccessGate name. For example, for an AccessGate named AccessGate1 configured in the /Common partition, the system generates a local cache file at the following path: /config/aaa/oam/Common/oampd/AccessGate1/config.cache. By default the system has a template cache file found at: /config/aaa/oam/config.cache.
The 'Clear Local Config Cache' button has been removed from the Oracle Access Manager properties page, and has moved to the AccessGate Properties page. Additional handling was added to process the request and delete the appropriate local config.cache file for the specific AccessGate.