System Engineer at a media company with 1-10 employees
Real User
Top 10
Sep 27, 2026
OneLogin Customer Identity by One Identity serves as our main authentication solution for logins to third-party applications such as AWS, Secret Server, Jamf, and SCCM, where we use SAML login to authenticate to our third-party applications. I have been using OneLogin Customer Identity by One Identity since my experience at Zinga, where we implemented it for authenticating multiple systems in the Zinga infrastructure.
IAM Analyst at a tech services company with 51-200 employees
Real User
Top 10
Sep 25, 2026
My main use case for OneLogin Customer Identity by One Identity is that I was one of the administrators of it, besides also using it as an employee of the company. I was assisting in user and application provisioning, as well as troubleshooting for those.A specific example of how I used OneLogin Customer Identity by One Identity in my admin role involves using an external multi-factor authentication like Duo as my MFA. One instance for user account troubleshooting involved creating the user account where I needed to unregister the MFA factor and ask the user to re-register again in order for OneLogin Customer Identity by One Identity to pick it up and exchange a new token, making sure it was now validated. From an application side, I was also using OneLogin Customer Identity by One Identity to integrate for single sign-on. For example, users who needed Adobe access, I would go into the Adobe application and create a linked connection to OneLogin Customer Identity by One Identity. OneLogin Customer Identity by One Identity already had the pre-setup out of the shelf that I could connect. From there, I would set up the callback URL and choose for SCIM provision and de-provision, so users would automatically receive a license assignment and be assigned Adobe at the time. Users would jump into their main OneLogin Customer Identity by One Identity page and from there they would just navigate and browse through the listed applications and sign in to whatever they needed. OneLogin Customer Identity by One Identity was my main tool, so everything was behind OneLogin Customer Identity by One Identity. Even for in-house applications, for example, with LDAP authentication or some other type of authentication, I would put it behind OneLogin Customer Identity by One Identity so that it was more secure and more reliable in terms of a token exchange and user authentication and authorization. I was having OneLogin Customer Identity by One Identity as my main tool and it was hosting thousands of applications within my company.
Analista de Suporte at a consultancy with 11-50 employees
Real User
Top 10
Sep 22, 2026
My main use case for OneLogin Customer Identity by One Identity is that as a support analyst and part of the consulting team, we mainly use it for services integrating into corporate environments, integrating MFA and SSO for some companies that need access control, both to unify accesses within a company for a person, make it easier for the person to access several applications they use in their daily life, optimize their time, make their access easier, and control these accesses. We have several authentication factors where you can ensure your company is not being hacked, from the user with the lowest privilege up to the most privileged user possible. A specific example of how this MFA and SSO integration helped a client is when a company had many employees that needed to control their access and unify their accesses because the HR team, for example, needed to access the HR app, the HR system, their email, Canva, spreadsheets, and various other applications every day. Each application had a login and password, so for the person to keep remembering them, many wrote them on Post-it notes and left them on their desks, others had a notepad file saved on the computer. This was a big headache for the company, and they wanted to avoid it because they could face a breach, which could harm the company since the HR team controls the company's financial side. SSO and MFA were integrated effectively in this situation, helping employees have less friction in their daily routines, so they did not need to memorize login and password. They could set a more robust password that was harder to crack, and at the same time, there was security around this with MFA, with the authentication factors that helped a lot with the service for the client.
My main use case for OneLogin Customer Identity involves addressing the integration of applications and resolving access issues that customers may experience. If customers face access problems, we must reach out to the IDM team, Identity and Access Management, to investigate what is wrong with their access process. A specific example of using OneLogin Customer Identity to resolve an access problem occurred when a customer of mine was using an application and encountered access issues. We checked everything, such as his email and whether his SSO was configured correctly, and then reported the issue to the IDM team, which enabled access. The customer had only read access, so it was modified to provide him with modify access allowing him to use those applications effectively and complete his work on time. While my main use case for OneLogin Customer Identity is quite positive, I can also say that the tool is really good, with continuous enhancements each year. Now, we are more frequently utilizing the AI tool, which will likely have a significant impact on the applications.
OneLogin Customer Identity has multiple use cases. I deployed this customer identity platform for about one and a half years with a customer whose primary use case was wanting a seamless customer experience that could provide customized branded registration and login experiences according to their wishes. We defined it according to their requirements. They also wanted feasible customer authentication and authorization that implements MFA options such as biometrics, passkeys, and SMS. There can also be use cases for centralized identity management, which consolidates identities across multiple brands or applications into a single directory for better management and insights. In this case, the customer had three different environments and wanted central management. For that, we used OneLogin Customer Identity. They also wanted better and secure migration of legacy users. They had very old user data, so we used the migration hook, which is the best feature in OneLogin. It allows users to log in with their old credentials which are validated against an external database, and it is easily migrated seamlessly to OneLogin during the login process.
My main use case for OneLogin Customer Identity is to ensure security and privacy on HIPAA and PCI-compliant platforms while easily storing employee passwords so that the tech team is not consistently bombarded by forgetfulness from the employees. This has solved both our privacy concerns as well as improved the flow of priority tickets for our technology team. OneLogin Customer Identity helps us securely store our credentials, which is vital because strong, long passwords are a must for security nowadays but almost impossible for humans to remember. Storing passwords in notes is a security breach by itself, so when OneLogin Customer Identity encrypts all the sensitive data before saving it, it also gives us easy access whenever we need to log in to our applications. It is very easy to use OneLogin Customer Identity. Logging in and accessing all the business applications under one tool is very straightforward, which provides sufficient security for all our applications and keeps everyone focused because they can open tabs of how they will be doing what they will be doing during the day, thereby improving productivity in my organization.
Learn what your peers think about OneLogin Customer Identity by One Identity. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
My main use case for OneLogin Customer Identity is that it is a very easy-to-use platform with a great design, making it accessible for everyone in my organization. Every employee in our company uses OneLogin because it helps us securely store our credentials. Strong, long passwords are a must for security nowadays, but it is almost impossible for humans to remember them, and storing them in notes is a security breach by itself. When OneLogin encrypts all the sensitive data before saving it, it also gives us easy access whenever we need to log into our apps. A specific example of how my team uses OneLogin Customer Identity in our daily workflow is when we are working remotely and we want to collaborate on a certain project. We use different apps that are integrated into OneLogin, so we have access despite working remotely. We can access it at any time because we use one strong password, which is very easy to manage, and it is easy to access our apps easily, thus enhancing our collaboration while keeping away unauthorized users. OneLogin Customer Identity helps us manage our different accounts, and it also assists with our single sign-on.
OneLogin Customer Identity streamlines identity and access management through secure access solutions. It addresses businesses' needs for a centralized platform to manage customer identities efficiently and securely.
Designed for companies seeking robust customer identity management, OneLogin Customer Identity facilitates secure environments by offering advanced features like multifactor authentication and real-time monitoring. It supports seamless integration with a wide array of...
OneLogin Customer Identity by One Identity serves as our main authentication solution for logins to third-party applications such as AWS, Secret Server, Jamf, and SCCM, where we use SAML login to authenticate to our third-party applications. I have been using OneLogin Customer Identity by One Identity since my experience at Zinga, where we implemented it for authenticating multiple systems in the Zinga infrastructure.
My main use case for OneLogin Customer Identity by One Identity is that I was one of the administrators of it, besides also using it as an employee of the company. I was assisting in user and application provisioning, as well as troubleshooting for those.A specific example of how I used OneLogin Customer Identity by One Identity in my admin role involves using an external multi-factor authentication like Duo as my MFA. One instance for user account troubleshooting involved creating the user account where I needed to unregister the MFA factor and ask the user to re-register again in order for OneLogin Customer Identity by One Identity to pick it up and exchange a new token, making sure it was now validated. From an application side, I was also using OneLogin Customer Identity by One Identity to integrate for single sign-on. For example, users who needed Adobe access, I would go into the Adobe application and create a linked connection to OneLogin Customer Identity by One Identity. OneLogin Customer Identity by One Identity already had the pre-setup out of the shelf that I could connect. From there, I would set up the callback URL and choose for SCIM provision and de-provision, so users would automatically receive a license assignment and be assigned Adobe at the time. Users would jump into their main OneLogin Customer Identity by One Identity page and from there they would just navigate and browse through the listed applications and sign in to whatever they needed. OneLogin Customer Identity by One Identity was my main tool, so everything was behind OneLogin Customer Identity by One Identity. Even for in-house applications, for example, with LDAP authentication or some other type of authentication, I would put it behind OneLogin Customer Identity by One Identity so that it was more secure and more reliable in terms of a token exchange and user authentication and authorization. I was having OneLogin Customer Identity by One Identity as my main tool and it was hosting thousands of applications within my company.
My main use case for OneLogin Customer Identity by One Identity is that as a support analyst and part of the consulting team, we mainly use it for services integrating into corporate environments, integrating MFA and SSO for some companies that need access control, both to unify accesses within a company for a person, make it easier for the person to access several applications they use in their daily life, optimize their time, make their access easier, and control these accesses. We have several authentication factors where you can ensure your company is not being hacked, from the user with the lowest privilege up to the most privileged user possible. A specific example of how this MFA and SSO integration helped a client is when a company had many employees that needed to control their access and unify their accesses because the HR team, for example, needed to access the HR app, the HR system, their email, Canva, spreadsheets, and various other applications every day. Each application had a login and password, so for the person to keep remembering them, many wrote them on Post-it notes and left them on their desks, others had a notepad file saved on the computer. This was a big headache for the company, and they wanted to avoid it because they could face a breach, which could harm the company since the HR team controls the company's financial side. SSO and MFA were integrated effectively in this situation, helping employees have less friction in their daily routines, so they did not need to memorize login and password. They could set a more robust password that was harder to crack, and at the same time, there was security around this with MFA, with the authentication factors that helped a lot with the service for the client.
My main use case for OneLogin Customer Identity involves addressing the integration of applications and resolving access issues that customers may experience. If customers face access problems, we must reach out to the IDM team, Identity and Access Management, to investigate what is wrong with their access process. A specific example of using OneLogin Customer Identity to resolve an access problem occurred when a customer of mine was using an application and encountered access issues. We checked everything, such as his email and whether his SSO was configured correctly, and then reported the issue to the IDM team, which enabled access. The customer had only read access, so it was modified to provide him with modify access allowing him to use those applications effectively and complete his work on time. While my main use case for OneLogin Customer Identity is quite positive, I can also say that the tool is really good, with continuous enhancements each year. Now, we are more frequently utilizing the AI tool, which will likely have a significant impact on the applications.
OneLogin Customer Identity has multiple use cases. I deployed this customer identity platform for about one and a half years with a customer whose primary use case was wanting a seamless customer experience that could provide customized branded registration and login experiences according to their wishes. We defined it according to their requirements. They also wanted feasible customer authentication and authorization that implements MFA options such as biometrics, passkeys, and SMS. There can also be use cases for centralized identity management, which consolidates identities across multiple brands or applications into a single directory for better management and insights. In this case, the customer had three different environments and wanted central management. For that, we used OneLogin Customer Identity. They also wanted better and secure migration of legacy users. They had very old user data, so we used the migration hook, which is the best feature in OneLogin. It allows users to log in with their old credentials which are validated against an external database, and it is easily migrated seamlessly to OneLogin during the login process.
My main use case for OneLogin Customer Identity is to ensure security and privacy on HIPAA and PCI-compliant platforms while easily storing employee passwords so that the tech team is not consistently bombarded by forgetfulness from the employees. This has solved both our privacy concerns as well as improved the flow of priority tickets for our technology team. OneLogin Customer Identity helps us securely store our credentials, which is vital because strong, long passwords are a must for security nowadays but almost impossible for humans to remember. Storing passwords in notes is a security breach by itself, so when OneLogin Customer Identity encrypts all the sensitive data before saving it, it also gives us easy access whenever we need to log in to our applications. It is very easy to use OneLogin Customer Identity. Logging in and accessing all the business applications under one tool is very straightforward, which provides sufficient security for all our applications and keeps everyone focused because they can open tabs of how they will be doing what they will be doing during the day, thereby improving productivity in my organization.
My main use case for OneLogin Customer Identity is that it is a very easy-to-use platform with a great design, making it accessible for everyone in my organization. Every employee in our company uses OneLogin because it helps us securely store our credentials. Strong, long passwords are a must for security nowadays, but it is almost impossible for humans to remember them, and storing them in notes is a security breach by itself. When OneLogin encrypts all the sensitive data before saving it, it also gives us easy access whenever we need to log into our apps. A specific example of how my team uses OneLogin Customer Identity in our daily workflow is when we are working remotely and we want to collaborate on a certain project. We use different apps that are integrated into OneLogin, so we have access despite working remotely. We can access it at any time because we use one strong password, which is very easy to manage, and it is easy to access our apps easily, thus enhancing our collaboration while keeping away unauthorized users. OneLogin Customer Identity helps us manage our different accounts, and it also assists with our single sign-on.