Omada Identity Reviews

Our general use cases include: 

• User onboarding
• User out-boarding
• Role-based access control, e.g., whenever a person's role is changed from one to another, then all the related roles need to be changed.
• Role management 
• Asset management 
• Re-certification, audits that happen every quarter. Every quarter a manager has to certify all his subordinates' access, whether that expertise should be gained or not, or whether they'll be skipped.

The most valuable aspect of the product is that it is Microsoft-based and it supports all Microsoft technology. It is ingrained with Microsoft and we implemented it ourselves for our clients wherein we can request software to install from Omada. That is something they have implemented and they are getting a lot of value out of. 

In terms of improvement, there are not so many out of the box connectors available in the current version. So what they have improved in the latest version is more out of the box connectors for integration, that is one improvement. 

Then there is the recertification process. When the recertification process is launched that makes Omada very slow. There are performance issues in the current version.

We have been working with Omada Identity Suite for around one year. 

There have been some performance issues during the re-certification process, so it works well whenever the re-certifications or audits are not launched but the re-certification makes it very slow. 

We haven't tried doing scaling it yet, so I don't know about that.

I personally have not contacted their support because I don't support our Omada current clientele but our clients have contacted Omada quite often when they required line support. They said the support was fine. 

Omada people came in on-premises and they helped with the installation, so it was a joint effort from the client and Omada. Our client takes care of the maintenance. They are enterprise size and use Omada on a daily basis. 

Licenses are only for installations and support problems. They are definitely additional costs.

I would recommend this solution if you are more Microsoft based technology. If not then I wouldn't recommend Omada, because it mainly works on Windows. It has been a market leader and Omada is growing, but it's not quite there with the current version. I would definitely recommend version 12.0 Omada.

In the next release, I would like to see more governance.

I would rate Omada a seven out of ten. The reason for that being is that it's good but it has got some limitations. Some performance improvements can be done.

I have this solution at two different sites and they are completely different setups.

The most valuable feature is the automatic provisioning and reconciliation of things like the Active Directory groups and memberships.

You can set up automated processes so that you don't need to have an AD administrator doing it all. You can automate processes and control who is allowed to do what. All of these features are quite good.

The way they do the connection to external systems for the provisioning and for the reconciliation is also very good.

The user interface should have a more flexible design, where you can change it to your requirement. It is not an agile design, so it doesn't reformat itself for small devices like tablets or mobile phones (i.e. fluid design). 

One year.

In a stable environment, it's reasonably stable.

You can kind of provoke it into being less stable. There is a thing called ROPE (Reconciliation and Policy Engine) that can sometimes be a bit tricky. Otherwise, it is mostly stable.

On my side, I consider it relatively easy to scale. I have been involved with customers that have worldwide organizations running with it. There are guidelines for scaling to that kind of size. Generally, scalability is ok.

Frankly, everybody in the company uses it because it is used to apply for permissions. Our internal administration team is between ten and twelve people, whereas there are a couple of thousand end-users.

I have had no problem with technical support. I have enrolled two similar people, with access to their partner website as well. In the partner's site, there is help available outside of the Omada family of products. 

I find the initial setup quite straightforward, however, I can imagine it being complex for some people. It can become very complex with the connections to external systems. I know of one customer here who has had very great problems with it, but another one found it a bit easier.

The main problem is going to be the amount of shoe-horning your own systems into it. That's the big problem; modeling so that everything fits.

We had an integrator working with our in-house team. You can't do it all on your own. You need an integrator, but there are good integrators and poor integrators.

I recommend using this solution and I would rate it a seven and a half out of ten.

Omada Identity Suite is an extremely flexible solution providing easy customisation of anything from process flows to role assignment rules and compliance reports. It’s handled almost exclusively through configuration, not development. Reacting on new requirements can be handled swiftly.

The whole IT side of offboarding/onboarding of employees/external consultants is centred on OIS. A tight integration between the HR system, OIS and AD ensures a high level of compliance while reducing manpower to a minimum.

The suite’s flexibility within the area of continuous violation detection and handling could be improved. I have not used the latest version, but I have been told that some work has been put into this area recently by Omada.

Eight years.

Generally, a very robust system running on Windows/MS SQL.

I have experience with rather large companies that have OIS handling thousands of identities and without worrying much about load balancing, server clusters, etc.

Above average.

I have worked with Sailpoint’s IIQ and I believe that on quite a high number of features (functional and nonfunctional), OIS is superior. I can only think of one area in which Sailpoint could claim to have reached a higher level of maturity: continuous recertification of accesses.

Considering the scope of the project, the setup was quite straightforward.

No knowledge of the pricing model.

No.

Despite the high level of flexibility in the SW, I recommend implementing the standard IAM processes/functionality that OIS offers and expand scope/customise from there.

Strict governance, ability to scrutinize, and make a granular view.

Governance around user access provisioning and user profiling.

UI and user-friendly adaptivity.

Less than one year.

Slow performance on reports.

OK, with complex questions from us.

Was complex, a lot of org implementation questions, master data issues, process workflows, too much compared to what we needed.

Choose wisely based on needs.

Work hard with your requirements and scope.