We use the solution for AWS single sign-on because we have not enabled federation for Symantec SiteMinder. We use Symantec SiteMinder for all the legacy on-premises systems.
Middleware System Engineer at a insurance company with 11-50 employees
Real User
2020-10-19T09:33:00Z
Oct 19, 2020
We use Siteminder to protect our portal site subscribers. In our case, this refers to people who have dental insurance. We're a dental insurance company and we've got millions of subscribers. We have thousands of dentists. We have millions of subscribers who use our dental insurance. There are a couple hundred thousand providers (dentists) in the network.
Cyber Security Specialist at a manufacturing company with 11-50 employees
Real User
2020-01-12T07:22:00Z
Jan 12, 2020
The primary use case of this solution is a single sign-on to gain access to users and servers. The security from the logistics team has required us to have a single sign-on solution. We implemented several single sign-on servers and we integrated them into one. The users would use it as a jump server. They would connect to it and from there, they would access the main server.
Customer was looking for initially an automated self user registration through a secure channel. Apparently it looks like a very easy going requirements but if you look in the detail they want to authenticate before registration process. A user came to create an Identity and customer wants to authenticate and securly takes the same data. Another issue was localization and reporting
Symantec® SiteMinder is designed to secure the modern enterprise through a unified access management platform that applies the appropriate authentication mechanism to positively identify users; provides single sign-on and identity federation for seamless access to any application; enforces granular security policies to stop unauthorized access to sensitive resources; and monitors and manages the entire user session to prevent session hijacking. Finally, Symantec SiteMinder is battle-tested...
The solution is used for single sign-on (SSO) authentication.
We use the solution for AWS single sign-on because we have not enabled federation for Symantec SiteMinder. We use Symantec SiteMinder for all the legacy on-premises systems.
I use it for authentication and authorization.
My primary use case of Siteminder was single sign-on. Siteminder was deployed on cloud.
This is a web single sign-on product.
We use this solution for applications and portals for a bank in Colombia.
We use Siteminder to protect our portal site subscribers. In our case, this refers to people who have dental insurance. We're a dental insurance company and we've got millions of subscribers. We have thousands of dentists. We have millions of subscribers who use our dental insurance. There are a couple hundred thousand providers (dentists) in the network.
We primarily want to use the solution to implement our SSO, Single Sign-On solution.
The primary use case of this solution is a single sign-on to gain access to users and servers. The security from the logistics team has required us to have a single sign-on solution. We implemented several single sign-on servers and we integrated them into one. The users would use it as a jump server. They would connect to it and from there, they would access the main server.
Our primary use is for client demo on authentication/authorization, federation, and ease of use.
Customer was looking for initially an automated self user registration through a secure channel. Apparently it looks like a very easy going requirements but if you look in the detail they want to authenticate before registration process. A user came to create an Identity and customer wants to authenticate and securly takes the same data. Another issue was localization and reporting