One Identity Manager Reviews

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

The product makes it easier for employees to be more productive.

The standard connectors are the most valuable feature.

The product is flexible. For example, it offers cloud features.

We would like the product to integrate with ServiceNow, since One Identity Manager and ServiceNow are two of our better tools. An integration between these two tools would be better for us.

The current product is stable. We are trying to get rid stability issues from the legacy version. We are now implementing version 8.2, which is so much better than version 6.

The product can grow with us.

The initial setup is fairly easy. To set up the workflows, you need good knowledge of the product. One Identity could improve the setup documentation, as it does not support, "How do I start?"

You need a good partner to assist with the implementation.

We are trying to achieve more targeted systems in the future.

We do not use the policy and role management features.

We have not integrated with SAP.

The data is easy to manipulate using SQL queries and commands.

The product was initially brought in to replace an unsupported solution. Later on, it became a partner self-service portal, reducing service desk calls to create accounts for business partners.

There are too many configuration interfaces. They could simplify the design to not require VB/PS coding to draw the workflows.

I have used this solution for three years.

The initial connection to the domain and LDAP trees was painful. However, once configured, it was stable.

The product scaled well. We had approximately 8000 users at the time of implementation.

There is great technical support. No issues there.

We used Novell's DirXML 1.1a. The client opted to migrate instead of upgrading.

The initial setup was complex due to the customer’s complex environment. A third-party service provider was required for deployment.

Licensing can be high. Quest usually bundles with other products, so you can get a better deal.

We only upgraded from the same vendor, Novell at the time.

The product has its challenges, but when well configured, it can provide good results.

In Q1IM, at least the version I worked with, it wasn't very intuitive to create processes and you need to actually add code to the boxes in order to customize. I always compare with NetIQ/Microfocus as they have the designer which is easier to elaborate rules.

About the interface, they have multiple applications, such as report designer, webdesigner, designer, object browser, import tool, manager, identity manager, jobqueue info. Its a suit of apps. It takes time to get familiar with them and know which does what.

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.

This is almost a complete solution for us. The data input to the second system, which has the role-based definitions, has made things easier. This is even with bubble representation.

The features are open and have a good tabular structure for the data, as well as the connected relational/relative topology.

The support documents and data sheets should be made available to the implementation of folks the product website. There's is less documentation available to the public.
There should be installer version available than a portable/web-portal which will be more useful during the testing.

We did not use a solution previous to this one.

It's costlier than some other products and there is nothing that fits every solution. You have to plan your design in advance based on your needs and user base.

We did not evaluate other options.

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. 

Larger customization has made the system complex and confusing. The people who deployed it initially did little to document it. This has had a negative, delayed impact on the overall project and solution. 

The good part is Quest One IDM allows for large customization.

• Separated modules and integration allow for more capabilities 
• Graphical and tabular interfaces
• VB and SQL front-end and back-end

A detailed solution document to registered aspirants and interested people would help them achieve what they require before its tested and pushed to production. Quest Software should provide notes and documents to customers before they buy the product and license.

Some valuable features are:

• Easy to configure, as it is mostly UI based
• Reporting
• Dashboard

It has improved the user life cycle operations and IT shop functionalities for our organization.

There is a need to improve the use case documentation and coding templates. This product has some limitations when it comes to use case documentation. Generally, when we have any different scenario, we need to post in the blog and only then we will get answers.

I have been using this product for the last two years. I have been using the Quest One Identity Manager (version 7.0, 7.1), Authentication Services (latest version), Password Manager (version 5.6.3), Privileged Access Management (latest version).

I have not encountered any stability issues.

I have not encountered any scalability issues.

Technical support replies within 1-2 business days. The Quest blog is very useful where the experts will answer the queries mostly on the same day.

Previously, we were using more complicated solutions.

The initial setup, installation and basic configuration are straightforward.

The pricing/licensing policy is less when compare to other leading other solutions.

We evaluated other options such as SailPoint, CA and Oracle.

This product is very effective and has more capabilities than any other.

• GUI
• Reporting capabilities

Allows the delegation of permissions related to identity management and also visual representation of the configuration as opposed to having to go through loads of scripts which was the case with our previous solution.

Job server engine -

• Performance
• Loadbalancing

One year.

Not yet.

Not yet.

More than one job server cannot be allocated per target/source system which can be a performance bottleneck,

Good.

Good.

Previous solution was an in house written application. We switched due to support reasons as well as outdated technology and a lack of functionality.

Configuration and implementation is a complex process as we had complex requirements, but could quite easily be done in a simple way.

We implemented via a combination of an in house team and a vendor partner. Their level of expertise was very good.

Yes we chose Dell One over Oracle IDM, IBM, NETIQ, and MS FIM.

Have a team of dedicated staff for the implementation who are given enough time to understand the many dimensions of the tool.