As most people have probably heard by now, a serious vulnerability related to the use of Log4j has been discovered. It didn’t impact any of our SiteMinder customers, but they were still required by their management to mitigate the issue. Broadcom published a resolution to
In this week’s post, we will outline a few of the Windows registry settings that we use for Windows-based CA Access Gateway (CAG) servers.
We have a customer that aggregates all their SiteMinder audit logs using a log parser tool named NxLog. It is configured to parse the smaccess.log and send the data to a centralized Syslog server. By default, SiteMinder will not include any details about the SAML assertion generation.
This week we have a post about policy troubleshooting. As always, we present the reported issue, what we found during troubleshooting, and how the problem was remedied.
This week we have a post about troubleshooting a web agent that is ‘unable to resolve agent name’. As always, we present the reported issue, what we found during troubleshooting, and how the problem was remedied.
This week we have a post about troubleshooting an Apache web agent on Centos 8.x. As always, we present the reported issue, what we found during troubleshooting, and how the problem was remedied.
This week we have a post about troubleshooting a new CAG 12.8.04 deployment on RHEL 8. As always, we present the reported issue, what we found during troubleshooting, and how the problem was remedied. Issue CA Access Gateway (CAG) on RHEL 8: 503 Error After
This week we have a post about troubleshooting custom login forms for an authentication channel. As always, we present the reported issue, what we found during troubleshooting, and how the problem was remedied. Issue Authentication Channel: Custom Login Page Failing with 500 Error Symptoms The
In another installment of the troubleshooting IAM system issues series, this week we have a post about fixing failed web services calls that use a cookieless session scheme. As always, we present the reported issue, what we found during troubleshooting, and how the problem was remedied.