CA Siteminder: Difference between revisions

From Cramsession
Jump to navigationJump to search
✍️ Verified Author: Mflavell • Click to view professional profile & credentials
(Created page with "[SMPS does not start after installing Oneview monitor on Linux]] <h3>Problem:</h3> Site minder sm.registry was updated as ROOT SMPS was starting as SMUSER <h3>Solution:</h3> chown sm.registry to smuser chgroup sm.registry to smuser use find /opt/siteminder -group root to check for root access delete the .pid file restart policy server <h3>Root cause:</h3> Oneview was installed as root NEVER install anything siteminder related as root. During the install of oneview the...")
 
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
[SMPS does not start after installing Oneview monitor on Linux]]
[[Computer Notes]] > CA Siteminder


<h3>Problem:</h3>
=Oneview Monitor=
Site minder sm.registry was updated as ROOT
SMPS was starting as SMUSER


<h3>Solution:</h3>
[[SMPS does not start after installing Oneview monitor on Linux]]
chown sm.registry to smuser
chgroup sm.registry to smuser
use find /opt/siteminder -group root to check for root access
delete the .pid file
restart policy server


<h3>Root cause:</h3>
[[Installing OneView Monitor on Windows]]
Oneview was installed as root
 
NEVER install anything siteminder related as root.
 
During the install of oneview the sm.regitery file was updated as root
 
smps could not read sm.registry due to permissions.
=Secure Proxy=
[[Replicate proxy Rules]]

Latest revision as of 02:09, 2 June 2025

Computer Notes > CA Siteminder

Oneview Monitor

SMPS does not start after installing Oneview monitor on Linux

Installing OneView Monitor on Windows


Secure Proxy

Replicate proxy Rules

Retrieved from "https://cramsession.net/index.php?title=CA_Siteminder&oldid=1099"