What is your primary use case for OneLogin by One Identity?

The main reason we use OneLogin is to securely manage employee access to different applications from a single platform. It helps us streamline logins through single sign-on, so users do not have to remember multiple passwords. At the same time, it strengthens security with features like multi-factor authentication. Overall, it is a combination of improving user convenience and ensuring secure access to all internal applications.One specific example of how OneLogin helped with this was during employee onboarding. Earlier, when a new employee joined, we had to manually create accounts for multiple applications and share separate login credentials. It was time-consuming and sometimes led to delays or errors. After implementing OneLogin, we streamlined this process using centralized user provisioning. Now, when a new employee is added, they automatically get access to all the required applications through single sign-on. It made onboarding much faster and more efficient. Apart from onboarding, offboarding is another area where OneLogin has been really useful. When an employee leaves, we can instantly revoke their access to all applications from a single dashboard. This is critical from a security standpoint. It removes the risk of any leftover or unauthorized access.

My main use case for OneLogin is managing all my logins in one place securely. It has really helped me with single sign-on, so I do not have to remember multiple passwords. For example, earlier I had to switch between multiple tools such as email, dashboard, and internal apps. With SSO, I just log in once and get access to everything instantly, which saves a lot of time and avoids repeated logins. Apart from SSO, I also use OneLogin for secure access management and keeping all credentials organized in one place. It just makes things smoother and more secure without much effort on my end.

In my role, I use OneLogin mainly to connect users with different applications through a single login flow. OneLogin acts like a bridge between our directory and the cloud applications. This is really helpful to manage access without handling multiple credentials. Our use cases include one portal for all applications, the Smart Factor Authentication, and the sync with directory services. In a real example, a user logs in from an office network and gets access without any issues. If the same user accesses or tries from a different country, additional verification is triggered. This automatically works without manual checks.

My full name is Dhiren Jetva, and I'm currently working at Digital Track Solution Private Limited as a Network and Security Team lead. I have been working in my current field for more than three years. I have been using OneLogin for between six to 10 months. My main use cases for OneLogin include Single Sign-On, Multi-Factor Authentication, user provisioning and deprovisioning, direct integration with LDAP, secure remote work access, and role-based access control, among others. For example, in my organization, I have over 20 SaaS tools that employees log into using OneLogin instead of accessing each one separately. Instead of managing separate usernames and passwords for each application, OneLogin provides a single credential that allows me to log into any of the 20 applications. This illustrates one of the use cases for Single Sign-On.

I typically use OneLogin for single sign-on and multifactor authentication. I use OneLogin to provide single sign-on access to my users for multiple apps in my day-to-day work. We basically rely on SSO and MFA with OneLogin. Most of our team connects OneLogin with Active Directory and HR SSO, so new joiners automatically get access to the required apps, and role changes update permissions instead.

In day-to-day operations, the main use case for OneLogin is to implement single sign-on and unified central authentication for my application. It connects directly to services like Active Directory and SaaS platforms, which helps manage user access from a single point.OneLogin allows users to authenticate once and access multiple systems using federation protocols such as SAML, which reduces credential management. Additionally, it employs policy-based authentication where authentication rules are defined based on conditions such as user role, device, and location to control how users log in, thereby improving security.

Our primary use case for OneLogin is to have central management of the solution across all our cloud and on-premises applications. For example, an employee logs in once and gets access to all their approved applications such as Salesforce, Zoom, or Workplace, and we use it to provision access automatically based on their roles when someone joins.

Our main use case for OneLogin is managing secure and centralized access across our HealthTech and FinTech platforms, primarily in real-life scenarios when team members need access to tools like the patient management system, financial dashboard, or different admin panels. OneLogin allows us to help them log in and securely access everything they need, and it also helps us enforce role-based security access controls, ensuring sensitive data points are protected. OneLogin helps us manage role-based security controls by allowing us to define and enforce different access policies based on various user roles, scopes, and attributes, with a primary focus on security. In practice, we generally map users, such as clinicians and support staff or the finance team, to specific roles, with a focus on the HealthTech workflow. For example, whenever a clinician needs to access patient records at the treatment tool, the finance team should not have access to that data, while the finance team would have access to financial data. These are straightforward scenarios, and OneLogin also supports automated user provisioning and de-provisioning, which is really helpful. Whenever a user role changes or they leave the organization, their access is updated or revoked instantly, depending on the workflow.

OneLogin is used to access customer relationship management analytics tools and internal tools. I log in with a single set of credentials, which allows me to quickly access all necessary applications without entering separate usernames and passwords for each tool. After login, I can directly open the CRM dashboard through the portal, and this saves time and reduces password fatigue.

My main use case is centered around single sign-on and multi-factor authentication across all of our critical business apps. It allows our team to log in once and securely access everything they need, which boosts efficiency and security. A specific example is that every morning when our team logs in, they use OneLogin to access our project management tools, email, and internal dashboards. For sensitive operations such as accessing financial reports, the adaptive MFA triggers, so they confirm with a push notification or a code. The customization options in OneLogin really let us tailor the security to our exact needs.

OneLogin serves as our centralized identity and access management solution, enabling features such as single sign-on for multiple cloud and on-premises applications, multi-factor authentication, user provisioning, and integration with Active Directory so that our users are unified in an IAM solution with role-based access control. OneLogin enables our users and organization to enforce single sign-on so that no security breaches occur for our on-cloud or on-premises applications. It also enables our IT team to enforce MFA for enhanced security in our environment. OneLogin offers a simplified solution that gives users a one-time login for multiple applications, which significantly improves user experience. It also enforces secured MFA and provides centralized control to manage users and their access on the platform.

As a customer of this solution, I mainly use OneLogin for identity and access management. My usual use cases include identity and access management functions like single sign-on (SSO) for internal tools such as Jira, ITSM, and CRM.

My main use case for OneLogin is to provide secure single sign-on access to multiple applications for our users. This simplifies user access by reducing the need for passwords and helps decrease password-related issues. OneLogin also manages user provisioning and de-provisioning to ensure users have the right access at the right time. Additionally, it implements multi-factor authentication and policy control to enhance security. A specific example of how my team uses OneLogin for single sign-on and user provisioning in our day-to-day work is when we onboard a new employee. We use OneLogin to quickly provision their user account across multiple applications. We create their account in OneLogin, which automatically grants them access to email, the HR system, and project management tools without needing separate logins. This saves time and reduces errors compared to manual account creation in each application. We also enforce security policies such as multi-factor authentication for sensitive applications. This provides protection against unauthorized access and enhances our overall security posture.

OneLogin's use case in my organization is for the entire infrastructure because it was very outdated, not secure, and it was built Windows heavy despite us being a Mac environment. I decided to go completely cloud-based instead. I rebuilt the whole school infrastructure into being fully cloud-based and software as a service most of the time, so we don't have any on-premise infrastructure for anything. OneLogin was one tool that I compared to two other tools, and it did everything I needed to do. It made our life much easier to switch to completely cloud-based authentication and everything.

My main use cases for OneLogin are vaulting and secure authorization. I use password vaulting to securely save our passwords so that we can log in without any hassle with only one click, which saves our time and keeps our passwords safe. This leads to our systems being robust without any outside attacks, making it very beneficial for us.

My main use case for OneLogin is app aggregation and SSO. I use OneLogin for app aggregation, which is utilized for a single point of access, so it is used in facilitation of SSO.My main use case fits into my team's workflow as it reduces the work, decreases the time required, and increases the flexibility of the team.

OneLogin by One Identity serves the purpose of SSO, which we used in partnership with Kaseya. I forgot the original name of the program, but we used it because it stored all of our devices and client information. This allowed us to avoid having anyone share passwords.I used SmartFactor Authentication to adjust the flow in real time depending on the risk score associated with login attempts. My phone functioned almost as a key. I appreciated the ability to get access codes, which was particularly useful when I was away from my computer and needed to access the system through the client portal using codes generated specifically for me. The integration of phishing-resistant device trust makes the authentication processes stronger and safer because of the complexity it uses. It relies solely on your data, which makes it harder for someone to hack into because it used multiple layers of authentication through one portal. With the SSO feature, it was easy to integrate with third-party authentication providers.

My main use case for OneLogin at Maya's 24 is related to general user access. I use OneLogin for user access across various applications seamlessly. My main use case revolves around enhancing security while simplifying the login experience for my team. For example, multiple tools my team relies on daily, including project management software and document collaboration tools, are accessed through OneLogin.

I have been using OneLogin for a year now for its access management capabilities and as an authenticator. We integrate with customers that want MFA, so we are mostly using OneLogin for it. For a customer who needed MFA, they wanted to integrate OneLogin as an additional way to authenticate to Safeguard for external employees. We basically integrated OneLogin as an authentication provider to Safeguard. To connect via the Safeguard SPP UI, customers would be redirected to OneLogin.

My main use case for OneLogin is managing all admin tasks related to OneLogin, which includes SSO integration, mapping, and role creations. A specific example of an SSO integration is the SSO integration with the SAML or OIDC protocol with third-party and internal applications. I handle the mapping feature, which is helpful for Google Groups data syncing via mapping to OneLogin role. We manage it ourselves, allowing us to bulk upload and bulk remove users in the Google Group, including roles and access review and user reconciliation processes.

OneLogin is our main identity and access management tool. We use Active Roles for user provisioning, which allows us to delegate the provisioning to other people. OneLogin manages user access permissions and includes creating mailboxes.

My main use case for OneLogin is enhancing system security by storing all passwords and system credentials in one place. OneLogin integrates with different tools, such as Google Workspace and other active directory systems, and I have been using it mostly for the purpose of enhancing security. For example, in enhancing security in my organization using OneLogin, I enable single sign-on, which helps me improve security. OneLogin also supports multi-factor authentication, allowing me to use a strong authenticator to improve my login credentials for other software. What I think is important about my main use case for OneLogin is that it can accommodate many integrations on a single platform, which allows me to manage all the credentials of my activities without delay or loss. It helps detect weak passwords and enhances the security system.

I have been using OneLogin for about a month, and it has been a valuable experience as I have seen it integrate with our existing system and enhance our overall security posture. One of our main use cases is streamlining user access across multiple applications, and the Single Sign-On feature has been a game-changer for us. It simplifies the login process for users, allowing them to access various applications with just one set of credentials. Additionally, we are leveraging Multi-Factor Authentication to add an extra layer of security, which has been crucial given the sensitive nature of the data we handle. Integrating OneLogin with our existing systems was an interesting process. We primarily focused on a few applications that our users access frequently, including project management tools, internal communication platforms, and customer relationship management systems.

My main use case for OneLogin revolves around application integration and user authentication. I primarily utilize it to implement Single Sign-On across internal and external applications, which significantly simplifies the login process for users. I use OneLogin for Single Sign-On with an internal project management tool that our team uses alongside a customer relationship management CRM system. Before integrating OneLogin, users had to remember separate login credentials for each application, which was a hassle and often led to frustration. The process has become much smoother with login pages, authentication, and access granted.

My main use case for OneLogin by One Identity involves single sign-on, multifactor authorization, and role-based access. For example, we have an email platform called DID Mail where we use single sign-on from OneLogin by One Identity to authenticate our users and use that same authentication on our different platforms such as virtual info and different mail platforms. The important thing we use about OneLogin by One Identity is role-based access, where our employees sign up and can see a different interface on the same platform according to their roles.

We use OneLogin by One Identity to provide SAML authentication and single sign-on for all of our SaaS apps.

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 used single sign-on, multifactor authentication, lifecycle management, and connectors.

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 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 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.

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

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.

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.

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.

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.