We used single sign-on, multifactor authentication, lifecycle management, and connectors.

We use it to deliver single sign-on services for both our company employees and our customers.

We use OneLogin for single sign-on to provide a consistent user experience with our in-house and external third-party applications. In addition to single sign-on, we use two additional modules: two-factor authentication and self-service password reset. It's a SaaS product.

We use OneLogin to log in to all our different systems. This means I only need to go to the OneLogin portal to access all my frequently used applications, like our CRM, Greenhouse for recruiting, Jira for ticketing, Workday for HR, Tableau for data visualization, and even Slack. It's a one-stop shop for everything I need!

We use this solution predominantly as our authentication provider for most or all SAML single sign-on services. We also use it as a tool to share passwords between users that need to have a centralized password database.

They are the authentication provider but we use it for multifactor authentication as well.

The service we use is where the users are on-premise with the network, then they bypass any single sign-on features. It just logs in.

We have six locations that are all connected by WAN VPN tunnels. Active Directory is being used to replicate the user accounts, and that replicates up to both Mircosoft, which is our primary single sign-on solution, and then to OneLogin. We use Microsoft for email, SharePoint, etc., and we use OneLogin as the authentication provider currently for that.

Our goal was to eliminate our on-site Active Directory and legacy Windows infrastructure since we operate solely on Macs. We considered two options: one that precisely aligned with our needs, and another that functioned more like a public solution. Ultimately, I chose OneLogin due to its enterprise-grade features and the professionalism of its representatives. It provided a seamless transition to the cloud, consolidating all our access needs onto a single platform.

We use it primarily as an identity provider. Beyond that, we use the SSO and SAML components. Additionally, we utilize their SmartFactor Authentication to prevent dictionary attacks. This is an additional security measure.

We primarily use Onelogin for SSO, but have been using the service for device trust as well.

The solution is a single sign-on for a control systems integrator startup that I was the systems administrator for. We linked it with several other applications just to give our employees a one-stop-shop portal to get to all of the other applications they needed to use, based on their role within the company and who needed access to what.

Our use case is to connect the users to the IDE and other endpoints. That is the basic use case that we have for OneLogin.

Currently, we use the solution for identity management. We wanted to have our own identity management on-premises as we did not want to use any third-party cloud solutions.