Earlier, customers used to authenticate the user before they used the application. With the help of Single Sign On, the customer logs in and uses all of the customer's applications without authenticating every time.
Solutions Architect at a tech services company with 5,001-10,000 employees
Real User
2019-03-31T10:49:00Z
Mar 31, 2019
We have our suite of applications and are using this product to integrate with most of the enterprise solutions or the identity providers solutions for authentication. Therefore, we are using it for authentication and single sign-on. For example, we are using the OpenID Connect protocol for authentication and receiving identity tokens from solutions. We wanted to test a single sign-on solution, which we can build up on, then later possibly provide as a solution to our customers. We started off with the community edition for our own uses. The community edition has an open source community, and the product over there is named Keycloak. We started off using the 3.4.3 version, then we went for the paid subscription. That is when we bought the Red Hat Single Sign On version 7.2. Version 7.2 has been enough for us as a single sign-on product.
Single Sign-On (SSO) enables users to access multiple applications with one set of login credentials, simplifying the authentication process. It enhances security and user experience, reducing the need for multiple passwords.
SSO integration helps organizations streamline access management by centralizing authentication. This reduces the administrative burden of password resets and improves compliance with security policies. Users benefit from a seamless experience, switching between...
Earlier, customers used to authenticate the user before they used the application. With the help of Single Sign On, the customer logs in and uses all of the customer's applications without authenticating every time.
We use Red Hat Single Sign On for login and password security.
I use Red Hat SSO for security and application authentication.
The primary use case of this solution is for single sign-on for a set of applications that we had developed. I'm a solutions architect.
We have our suite of applications and are using this product to integrate with most of the enterprise solutions or the identity providers solutions for authentication. Therefore, we are using it for authentication and single sign-on. For example, we are using the OpenID Connect protocol for authentication and receiving identity tokens from solutions. We wanted to test a single sign-on solution, which we can build up on, then later possibly provide as a solution to our customers. We started off with the community edition for our own uses. The community edition has an open source community, and the product over there is named Keycloak. We started off using the 3.4.3 version, then we went for the paid subscription. That is when we bought the Red Hat Single Sign On version 7.2. Version 7.2 has been enough for us as a single sign-on product.