The issue is resolved by adding SSOZoneName parameter in ACO for the agent. It was requirement based on the setting we have in our environment. Since authentication was going in loop due to cookie issue related to SSOZoneName, it was not reaching authorization step.
Hi all, we are having a very strange issue with siteminder. We have siteminder 6.x and kerberos authscheme and it is working perfectly fine. Now we are migrating to siteminder 12.8. I configured siteminder 12.8 with kerberos and checked all principalname and tokens and policy server is...
I'm a recruiter who is currently hiring for a #siteminder Specialists in the #Raleigh , NC area. It's been a very difficult skillset to locate. Any idea of good resources to use to find these professionals in that area? or anyone on here located in #Raleigh or willing to relocate open for an...
Summary : Sometimes CA SSO Access Gateway (Ag) can return a 302 redirect to a HTTP (port 80) location, when a HTTPS (port 443) location was expected. In Access Gateway Apache mod headers module can be used to fix the returned Location: header - as explained below. Issue : ...
1 Comment - no search term matches found in comments.
Hi, Username contains & character and logic.fcc is not allowing to login with vaild credentials. I have checked the logs but couldnt find why this is happening. Could someone help me out? Regards- Yashpal #ssositeminder #ssosecurity
We have 3 different environments, Dev,Test and Production. For some reason, Client wants to access them in the same browser. If Client has accessed test environment and then he logs in to the production environment then Production smsession cookie overrides the existing cookie for Test however...