What is your primary use case for One Identity Manager?

I use One Identity Manager in a few different projects for the Air Force, and I have also used it for the commercial business that I currently work for, covering both government and commercial environments. I do not use One Identity Manager to help me manage SAP. I don't use One Identity Manager for IGA regarding the difficult-to-manage aspects of T-codes, profiles, and rules. I do not use One Identity Manager to extend governance to cloud applications through custom interfaces.

The use cases for One Identity Manager include multiple aspects of identity and access management. One of the most interesting features I wanted to utilize was the user's access review, UAR module. The idea was to create a quarterly review process to review the entitlements and the access and controls in place, initially targeted towards Active Directory and later extended to other local systems. One Identity Manager can connect SAP accounts to employee identities under governance. It is possible to map company structures for application provisioning through dynamic application provisioning using role-based access control. Mapping roles to users is a seamless experience that offers a lot of leverage in terms of speed and compliance, making it a very useful feature.

My use case with One Identity Manager is both access management and identity management. The main tasks I perform involve solving issues when users receive roles but cannot access applications. During these situations, I debug within One Identity Manager to find and resolve the issues according to required actions. This is my daily use case.

I use One Identity Manager for IAM processes, governance, and policies.

My use case for One Identity Manager is identity governance and administration. I am an implementation partner for One Identity Manager.

Our primary use case for One Identity Manager ( /products/one-identity-manager-reviews ) is focused on automatization and digitalization, specifically in introducing identities with appropriate permissions across various IT systems.

I am a consultant for One Identity Manager and implement it for clients. They use it for ordering permissions, attestation of permissions, and reporting on permissions.

The overall purpose for using this product is for identity management, which is our core requirement.

We are using One Identity Manager to change our previous old identity access management platform. Currently, the separation of duties is the most important aspect.

We use One Identity Manager for access management and provisioning, as well as onboarding target system applications. It focuses on identity management and providing access. We use different tools like Web Designer and Synchronization Editor, and we do implementation, customization, and configuration based on our requirements.

I use One Identity Manager for RBAC in my current project. We do provisioning and de-provisioning. After running certification campaigns, it automatically aggregates. I also onboard several applications in One Identity Manager. We also use it for audits, recordings, and activities like entitlements or policies with segregation of duties.

One Identity Manager's primary use is managing employee identities, encompassing the entire lifecycle from onboarding and role changes to offboarding, including lifecycle management, certification, segregation of duties, and identity retirement.

I am certified as both Technical Specialist and Implementation Professional on the product. I assist various clients in diverse sectors, mostly finance, industry companies and municipalities. I have quite a broad background in implementing it in different scenarios.

We use One Identity Manager for classic identity management tasks like provisioning and de-provisioning. It is employed for user requests and identity governance. It supports a comprehensive setup that includes user access, requesting functionalities, and identity governance measures.

We utilize One Identity Manager for user identity access management and troubleshooting, all founded upon dynamic roles.

Our company uses it internally to request access to different customer environments. We use it as a centralized RGA for distributing different kinds of VR-managed service providers.

One Identity Manager is our primary tool for managing identities and access, encompassing the entire employee lifecycle from onboarding to offboarding. This includes managing entitlements, requests, and approvals, enforcing segregation of duties, and conducting regular access recertification. We are currently utilizing a hybrid model, where our primary SQL Server remains on-premises while some web servers have already been migrated to the cloud, with further cloud migration in progress.

I use One Identity Manager to implement an identity governance and administration solution for end users.

One Identity is an IGA tool for identity and access governance. One Identity has another product called Safeguard for privileged access management. Our organization is a startup, so we don't have any cloud applications in One Identity Manager. We manage the Active Directory, LDAP, JDBC applications, and CSV files.

We use Identity Manager for several things, such as automating our XML process, user provisioning and reprovisioning, and governance-related activities like access reviews and degradation of duties. Identity Manager sits at the center of the organization. We integrate our systems, like Workday, into other HR systems for employees and contractors. If there are any vendors and customer-related identities, we feed the data from those systems into One Identity. One Identity Manager is configured to the initial access established when someone joins the organization, such as email, Active Directory, desktop logins, timesheets, and common apps that everybody in the organization requires. We also have request systems in ServiceNow integrated with One Identity Manager on the back end. The request tool goes through ServiceNow, and One Identity creates a notification that a user has requested access to an application. Identity Manager will provision those users on those systems. Some requests are automated and others are semi-automated. When a ticket is opened in ServiceNow, the team will pick up the ticket and work on it. Once they do that, an update comes into the IDM system saying that this user has been granted this access. One Identity Manager is the central book of records or identities and their access levels.

I designed and implemented One Identity Manager for clients across various companies. This involved a wide range of use cases, including standard employee lifecycle processes like onboarding, transfers, offboarding, and location changes. I also implemented more sophisticated use cases, such as automatically creating Active Directory groups and service accounts based on user requests and approval workflows.

One Identity Manager is a software tool specifically designed to manage and govern employee identities throughout their entire lifecycle within a company. Similar to other governance tools, it ensures employees have the right access to data and applications based on their role, from the moment they are hired until they leave the organization.

One Identity Manager streamlines our entire identity lifecycle management. It handles onboarding new joiners, assigning and controlling roles with role-based access control, and automates user access reviews twice a year. Additionally, the system facilitates reporting for audits, providing auditors with necessary information on demand. This centralized system acts as a one-stop shop, managing everything from onboarding and role assignment to offboarding and emergency access control.

We use One Identity to integrate our internal and external applications into SSO.

One Identity is used to create, sync, and delete accounts automatically across multiple systems. The product allows employees to be managed from our Human Resources system, while consultants and temporary personnel can be managed manually. The system provides automated workflows and birthright assignments for easier management of similar accounts or those in the same department or role. With the system synchronized with our HR database, new account creations are automated and include an email to managers providing users with their credentials for initial login. Only the hiring manager will receive a copy of the initial username and password, helping further secure this information and have it readily available before the employee begins.

One of our largest clients in the food and beverage industry uses One Identity Manager to manage its user identities and access controls. They have several applications that require user accounts, and for this purpose, we implemented One Identity Manager. This system effectively manages over 200,000 user accounts and provides access to these applications. Additionally, some applications are integrated with One Identity Manager to streamline account creation, such as setting up Exchange mailboxes.

In terms of the use case, the traditional use case related to IAM is to synchronize the accounts to the user ID. Most of the time, we connect it to Active Directory, Azure AD, SAP One, and one or two other systems at the first stage of the project. At the next stage, we start to integrate it with other systems. My company is an integrator and a partner. I am not the final customer. I deliver solutions to our customers. I also have other solutions in my portfolio, but my strength is Identity Management.

Its main purpose is identity management. It is an IGA tool. The organization where I am currently working is mainly using One Identity Manager for identity management and access control. We are also using it for various types of provisioning such as Azure AD, Exchange Online, or SAP account creations. When we talk about identity management, we also consider the various access recertifications. All those are being carried out as part of One Identity Manager.

The primary use case involves overseeing comprehensive identity and access provisioning, along with managing the onboarding and de-provisioning processes for users. This includes orchestrating the creation of new projects, conducting simulations, and ensuring synchronization between a core solution and other target systems.

My clients use One Identity Manager to streamline and enhance their identity and access management processes. Whether it is a university simplifying student onboarding, or a global corporation managing employees across multiple branches worldwide, One Identity Manager helps them efficiently onboard, move within the organization, and offboard individuals.

We primarily use the solution for background management. It's used for provisioning and license management.

We provide IT services for several European clients, so their individual use cases vary. For example, one is a research center in Sweden.

We use One Identity Manager for identity governance.

I install it for other companies, and one of them uses it for custom processes.

The purpose of the solution is to add customers with identity and access management. We build software for them and configure everything, however, we're more on the consulting side.

Like any other identity manager product, the best use cases for One Identity Manager are where you need to use a lot of business logic, and you'll have to configure the processes the way the business wants. In my opinion, One Identity Manager is the best product for business logic and administration. The solution is pretty scalable and can be used in finance, health care, and higher education. One Identity Manager would help if you have an SAP in your environment. It's a top product related to active directory and integration.

Our primary use case was to onboard certain applications for a customer.

We utilize One Identity Manager to oversee all the identities within the company, and we are constructing workflows to enable self-service keys for compliance and access matters.

We are tech consultants who deploy One Identity for our clients. Our clients use One Identity for provisioning and deep provisioning users. It is also used for the recertification process and access review. We have integrated One Identity for 15 to 20 clients. Soon, we expect to deploy it for another five to 10.

The purpose of One Identity Manager is to implement identity and access management tools. For on-premises use, we must connect various target systems and trusted sources with the central identity and access management tools. This involves integrating Workday or other HR management systems with One Identity Manager and linking authentication sources, such as Active Directory or Azure AD, with One Identity Manager. Additionally, One Identity Manager has a specialized connector library for SAP solutions. This solution can be deployed on the cloud and on-premise.

Currently, we are using the One Identity Manager solution for user feeding from the HR database to target systems such as Microsoft Active Directory, Microsoft Exchange, and other protocols and servers. In our organization, One Identity's main use case is user feeding, user onboarding, and user offboarding. We have created job flows for users, and One Identity listens to our HR database to see if there are any changes. It detects any changes and then synchronizes with the target systems or feeds the target systems. We have created a custom workflow based on our organization's requirements, and then we are managing our users with One Identity. One Identity has a single sign-on solution. If you want to use single sign-on or auth providers in your organization, you can use it, but currently, we are not using it for the single sign-on features. We are using it for privileged accounts. We have created custom rule sets for access reviews, attestation, etc. We have also created flows for the segregation of duties and job rotations. We are handling these operations or regulations with One Identity. We are completely working with an on-prem solution. As per Turkish financial regulations, we can't use cloud services for financial services. That's why we didn't test any scenarios related to the cloud and any software on the cloud. We are currently using its latest version.

The primary use case is the JML role-based access provisioning and access re-certification.

The use case is like any other identity management solution: to provision and de-provision software accounts and entitlements for new hires and terminations, and to update name changes, leaves of absence, and those kinds of business cases. The goal of the tool is to automate processes of updating or modifying user access.

We use it to manage the roles that everybody receives for our network. We use it to create an overarching business role and then we have individual, direct assignments to provide extra permissions where needed.

Our company hosts our on-premises application with this solution. It is not a complete SaaS product but rather a hosted environment in their tenancy.

We use One Identity Manager for every need. We use it for provisioning, cataloging, approvals, connecting to systems, and also for trying to figure out what's going on, governance, reporting, and provisioning changes. It's also for leavers, joiners, and movers. The solution is for everybody.

One Identity Manager is a central identity provider and authorization provider, and I've been using it for multiple customers who use it as a central identity provider.

We use the solution for creating and completing enhancements and other features. Personally, I have experience working as a .NET developer and working with the SQL server database. When I joined Wipro, I worked mainly with One Identity Manager tool as a developer. In addition, I do web design and object browsers, job queues, and use other tools.

My company has a lot of use cases for One Identity Manager. In my previous company, I've been maintaining the tool, so I used to go to clients who needed improvements and support in terms of provisioning, and I provided those services. Now, in my current company, I'm in the Identity Management team, and my company is using its old Identity system with One Identity Manager, particularly for provisioning, access management, compliance, and certification, apart from identity management.

This solution creates the roles for the NDSS, including onboarding of accounts. It's an end-to-end solution in that the customer will request some permissions, and it will enter treatment for that user, then push the data or automatically onboard admin accounts for that user.

We are a company in the health sector, with about 50,000 employees from six different health organizations. We use the solution to help automate all the processes around hiring and firing. We have automated as many processes as possible around user accounts and mailboxes, and file and folder administration. And with the IT Shop, customers can request permissions themselves.

We used One Identity Management for 15,000 employees of a financial services firm. In addition to the IM functionality, we leveraged One ID for Identity Governance - including access certifications. We had automated provisioning of users based on HR data. This automatically created 4-5 base accounts and birthright access for users. In addition to that, we leveraged the IT shop to request roles for users which, for the most part, automatically provisioned access to users. In addition to this, we used the Attestation features of the product to aid in our User Access Reviews.

We do employee lifecycle management through One Identity Manager with the source being SAP. We do not just do human accounts, like SAP accounts, but we also do non-human accounts, e.g., service accounts, shared mailboxes, distribution lists, and mail contact objects. We also use the API feature of One Identity Manager to provision from ServiceNow. These are its core functionalities.

One of the key use cases is certifications for SOX applications. Another is centralized onboarding and offboarding. Another use case is the Self Service using the IT Shop, which gives us a repository of entitlements that people can request and then have the approval workflows, and document the approvals for SOX and other regulatory requirements. The appliances we use for this solution are VMs. We went with that version because we're forced to. We're not allowed to use physical hardware. Our infrastructure group requires us to use VMs.

Access governance related to audits. BAAN, AX, AS400, AD, Exchange, Footprints, several home-grown applications. We had a relatively small AD (about 5,000 users) but our primary challenge was that all of the legacy systems in place, including multiple instances of BAAN that came from different M&A deals, each with their own configurations and entitlements.

We use it to manage all identities within the company. We use it to monitor users when onboarding and offboarding. We also use it for all the related accounts, such as SAP accounts and AD, to give permissions to our employees within these systems. We do all the privileged management as well within One Identity Manager, which mainly consists of monitoring and control of users, especially who's changing what.

We use it to control identity and access management in our company.

Our primary use case is to control access to our open source Unix and the app store games. This is a banking organization, so you don't want to give all of the rights to one person.

We use it to make requests and show the information that the users have, as well as for attestation.

Our primary use case is for integration to a second system, which will use the role-based access management for the identities and user accounts in the One Identity Manager.

We implement One Identity Manager for our customers.

The primary use case is to allow users to quickly administrate their permissions and data.

The primary use case for this solution is implementing them at the customer site, according to the customer's business needs. E.g., certain customers needs an attestation case. The reason for implementing this solution is the need to become somewhat more in control. There is also the ease of use for connecting products to target systems, like an Active Directory or Exchange.

My primary use case for the solution for the last several years was migrating from version 6 or older to version 7 or 8. Most of the time, we implement new features, optimize existing features, or do project management for the customer.

We use it for the identity lifecycle.

The primary use case is to handle identities.

We using it internally. We are also offering it to our customers as a managed service.

We are using One Identity Manager to manage user access requests. Then we manage the provision, as well as the provision of those users. We get the identities from SAP and then we provide them whatever access they are requesting.

We have chosen the product, especially for its governance for all the processes of the company, onboarding of employees, and lifecycle processes.

We have this process of provisioning and non-provisioning users, depending on our SAP HR database.

We use it to manage identities, We have around 12,000 employees who need to be managed, which is a lot of people worldwide. It is sort of stressful to manage proactively unless you have automated systems.

The primary use case for us is to follow the identity lifecycle, starting from feature improvement up to many accounts along with targeted systems.

We use it to give the right access to the right resources.

We use it for all things related to identity in our organization.

We mostly use One Identity Manager for the tasks of onboarding and offboarding business roles, assigning permissions, and ensuring that we have a record in auditing to fill out compliance needs.

We use it to facilitate our total identity and access management process, from HR to our target systems are using this product.

We use it for meeting compliance requirements.

It manages our Active Directory and SAP user accounts according to HR data and assigns permissions via request or rules.

We had several tools over time to try to gain control of IAM, but none of them were capable enough for our needs. We simply had too many systems to work with. We wanted one digital identity for each user and a comprehensive view of each user’s entitlements.

The primary use case is managing business applications.

We are managing the entire trend for our identity management, from HR hire until offboarding. We use it for managing all the IT accounts in the company, which has hundreds of thousands of identities.

We want to bring our on-premise systems under our control, then our cloud solutions under our control.

We manage companies identities and different legal bodies in it from all over Europe.

As consultants, we use it for provisioning, for access management in SAP, for AD access management. In the future, we may use it for many other applications like SafePoint and Office 365.

This was for customers identity management, where there were a huge number of domains and the customer had unnecessarily complicated the system with a lot of parameters and attributes.