CustomIPHeader in ACO. Restart?
Article ID: 195621
Updated On:
Products
CA Single Sign On Secure Proxy Server (SiteMinder)
CA Single Sign On Agents (SiteMinder)
CA Single Sign On Federation (SiteMinder)
CA Single Sign On SOA Security Manager (SiteMinder)
SITEMINDER
Issue/Introduction
If we change CustomIPHeader in ACO, do we need to restart anything?
Environment
Release : 12.52
Component : SITEMINDER -WEB AGENT FOR APACHE
Resolution
You do not need to restart anything.
Changes in the ACO are not picked up immediately, it will take a minute or two.
You can flush cache:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-identity-and-access-management/single-sign-on/12-8/using/administrative-ui/cache-management-dialog.html
Which will cause the change to be picked up more quickly, but please take heed of:
"Note:
Flushing all caches can adversely affect access times for protected resources, because all requests immediately following the cache flush are required to retrieve information from user directories. This action can be necessary if critical user privileges and policy changes are required to go into effect immediately."
Changes in the ACO are not picked up immediately, it will take a minute or two.
You can flush cache:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-identity-and-access-management/single-sign-on/12-8/using/administrative-ui/cache-management-dialog.html
Which will cause the change to be picked up more quickly, but please take heed of:
"Note:
Flushing all caches can adversely affect access times for protected resources, because all requests immediately following the cache flush are required to retrieve information from user directories. This action can be necessary if critical user privileges and policy changes are required to go into effect immediately."
Feedback
Powered by
