We usually try to recommend to our customers which different access typologies they have, and based on that, we recommend implementing policies that check the risk in real time, the context of the user, the behavior, and based on that, we apply MFA policies.
The sign-in and authentication process is simple in the way that it is a very intuitive login experience, but the main problem is that we cannot customize a lot, so we cannot provide a 100% seamless experience. Sometimes we cannot customize to adapt to the customer use case, for example, so I am not 100% happy about that.
The impact of the integration of phishing-resistant device trust on the authentication process is good because it adds a really good security layer. You can evaluate a lot of the context of the user login and you can integrate with security devices such as YubiKeys and hardware tokens. Therefore, you are adding a really good security layer for any authentication in any application.
I use the single sign-on feature and I would say it is easy to integrate because it has a really high catalog of predefined connectors. This is good and really easy to use.
I have used the adaptive login flows with Vigilance AI for some basic use cases. When we had the requirement to adapt the login process or customize the login experience, we need to use this to customize it. The main problem is that you sometimes cannot customize as much as desired, but we use that and it covers most use cases, although I would like it to be a bit more flexible.
The HR identity management plays a good role in streamlining identity handling for employees because it covers the joiner-mover-leaver flows in a company. We usually integrate that use case with the human resource tool, so we automate the process where a new employee joining in the human resource tool allows OneLogin to get that identity and propagate it. The basic use case is covered and is good enough. This is not a governance solution, so you cannot expect more, but it covers the identity synchronization with human resources.
The advice I would give others looking to implement OneLogin is that before trying to integrate and deploy OneLogin or any access management solution, you need to train your internal teams extensively and make them aware of what is coming and what this solution is about. You need all the teams in your company to be aware of why OneLogin is being implemented and what that means because once you start integrating applications and having people access and log into the product, you need to make them agile. I will focus on internal communications and internal trainings more than the technical part.
My overall rating for OneLogin is an 8.