Omada Identity Reviews

Our clients use it to onboard apps for provisioning, not just collections. They use Omada for provisioning to business applications, such as SAP and PeopleSoft. They use ServiceNow as the front door to that but Omada is for their accounting and their HR business applications. It's mostly used for the governance piece, certification—GRC.

Compliance is often what the issue is for our customers. They want to hurry up and get these products onboarded and set them up for provisioning for their business application, so they can meet whatever regulatory compliance controls they're trying to meet.

We're an Omada partner/vendor. We implement both their on-prem and SaaS versions.

From a security perspective, we've got customers that are failing audits or that are in danger of failing audits, because they can't do certifications. While it's not necessarily an improvement to the way their business functions, Omada certainly helps customers remain compliant with those audits. It makes them more efficient, and it's easier for them to support the audit requirements they have to remain compliant.

The solution also helps reduce total cost of ownership. In cases where they're swapping out Oracle, or they're swapping out RSA's Aveksa or IGO product, it's certainly reducing total cost of ownership. And, when we're moving clients from an on-prem, legacy IGO or IGA solution to the cloud solution, they no longer have the infrastructure issues and it's a lot easier to maintain. It's not as complex as an Oracle. Certainly, when we're replacing some of those legacy systems—IBM, Oracle, CA—it definitely reduces total cost of ownership.

Another benefit is that it has helped to reduce the number of helpdesk tickets and requests, specifically when combined with ServiceNow, which we've done in a couple of instances. In that scenario it drastically reduces the helpdesk tickets. Omada has the workflow built into it that allows a lot of work that used to be done through the helpdesk to be automated. We try to build more automation into the system in an effort to reduce the amount of support that's required for it.

It has also absolutely reduced the number of audit fines that our customers receive. A few of our Omada customers have either had audit findings, or did a pre-audit and knew the findings were coming, or they were trying to clean up from an audit finding by using the solution to do so. We see a reduction in audit fines in at least half of the cases where we implement the product.

The most valuable feature in Omada is the governance. We work with other products and other product vendors, but the sweet spot in the market for Omada is where things are heavy on governance.

I would like to see them expand the functionality of the tool to continue to be competitive with the monsters out there. For example, they could add functionality on the authentication side, functionality that Octa and SailPoint have. But they should do that while maintaining the same simplicity that makes Omada a product of choice today.

We've been working with Omada for four or five years now.

We have a lot of choices out there in the market to spend our time on. We've chosen Omada as one of the products that we support. It has been very stable. We haven't seen any issues related to stability so far.

When it comes to scalability of Omada's cloud-native SaaS solution, we've used it with a Fortune 10 customer and a Fortune 100 customer. It's definitely scalable. The fact is, we're connecting it to SAP which is running the internal organizations of some of these companies. It's a new product, so it probably hasn't gone through enough Fortune 500 companies to say that it has been fully tested at that scale, but the customers that we work with are pretty significant customers.

In terms of our customers increasing usage of Omada, if they've gone through the process, they have a prioritization of the applications that need to be onboarded to an IGA tool. Once they get those high-priority applications onboarded, there's the never-ending list of additional applications to get onboarded. The priority for onboarding applications could be business-related, it could be audit-finding related, or it could be SOX-related. The client makes that determination. 

We've integrated the product with CyberArk and ServiceNow, to automate some of the helpdesk support that is typically required. Most of our customers are at the stage where they're saying, "Hey, let's get this Oracle HR product onboarded as our system of record, and work from there to onboard the other apps." Most customers, even the small customers, have an endless list of applications that need to be onboarded, once they have onboarded their highest priority applications.

We have relationships with Omada from the chief revenue officer, all the way down. When we really need to make something happen, we can put that call in and make it happen.

But from what I know from our customers that have used Omada's technical support, they seem to believe those guys to be as adequate as any of the competitors in the space.

The complexity of the initial deployment of Omada depends on the customer. But one of the reasons we chose to become a product vendor for Omada is because of the simplicity. It's the perfect fit for a lot of customers that don't need the complexity of an Oracle, or of a CA, or even a SailPoint. That's one of the main factors that attracted us to the product.

The implementation strategy is going to depend on the customer and where they are in the process. The pre-implementation strategy is to find customers that meet what we've defined as the sweet spot of customers, where Omada is the best fit for them. They are customers that are looking for this, this, and this, they're this size, and they're at this stage in their maturity model. We like Omada for the SMB market because you can get your hands around an implementation. You can get them on the cloud version and get them up and running pretty quickly. 

If it's a customer that doesn't require a lot of complex workflows, it's a simple product to get installed and get up and running. However, it still does have the heft to be able to support some of the more complex custom configurations and workflows, if they need that in the future.

There is no such thing as an "average deployment," but 90 days would not be a stretch for getting some of our clients up and running and getting an app or two onboarded, with some pre-built-in workflows.

The number of staff required for deployment is also deployment-specific, but we'll typically have a team of between two to ten people, depending on the size of the deployment and what the customer wants to do.

Some of our legacy clients—and when I say legacy, I'm talking about two to three years ago—are using the on-prem version. Whether a client goes with the SaaS or the on-prem really depends on what the customer is looking for. A lot of customers are going for SaaS because of the "flash-to-bang." The pitch is that with one of the starter packs, you can get them up and running with a system of record in a shorter amount of time than with the on-prem version. That's typically the preference. Customers want to get up and running. They're running from an audit, they're running to meet compliance, they're running for a deadline. They typically want to go SaaS so they can get some quick wins under their belts. The on-prem takes a little bit more coordination with their onsite technical and security guys.

The ROI that we see is the "flash-to-bang." You can get in there and get the implementation up and running. 

There is definitely also ROI, that I can't quantify, in getting clients compliant with findings and in getting their highest priority applications up and onboarded.

Where we do see a lot of ROI is with the cloud version in particular. When we do these implementations, we require time from the customer's internal IT staff. With COVID, those guys have been busy making sure folks can work remotely and protecting themselves from all the different threat vectors that have presented themselves during COVID. The cloud version requires the least amount of time of the internal IT staff, so there is definitely ROI there.

Omada continues to be very competitive on pricing, especially on the Omada cloud product.

In terms of the solution's IGA features, I'm not going to say Omada's are pretty broad but there is enough breadth there to support some large customers that are using that product. It's definitely compatible, in terms of breadth, with other products out there in the market.

We support SailPoint. We've done a little work with Saviynt. We've worked with some of the legacy solutions, like Oracle OIG and RSA. We're familiar with other IGO and IGA solutions in the market.

Compared to some of the more complex tools, with Omada you can cut the implementation time in half, or even more than that. We look for the customers that fit that Omada mold. For the customers that don't have the complex workflows, and where you don't have to wade through 37,000 guys in their IT shop to make something happen, it's certainly a much easier product to get installed. That's why we like it.

But there is competition. All these vendors are now offering cloud solutions, like SailPoint's IdentityNow. Saviynt is a cloud-based solution. But when it comes to some of the legacy ones, you can certainly reduce your implementation time by 50 percent or more.

And on the pure governance part, Omada is definitely maintaining some of the same functionality as the other vendors out there in the market. It's not going to have all of the functionality of the SailPoint on-prem version. But it's more than adequate for the average customer.

The only advice I would give is the same advice I give anywhere: Know your requirements and then make sure that the Omada product is the product that best fits your requirements. If it does, you can get it in and up and running in a more reasonable amount of time than some of the competitors on the market.

What I've learned from using the solution is that Omada has a certain place in the market. When we find a customer that has the set of requirements that Omada is a really good fit for, we can get them up and running pretty quickly, without their having to spend a ton of money, and without their having to spend a ton of their internal IT resource time. Omada is probably marketing to everybody, but for us, there's a certain customer where we say, "Okay, they're heavy on this, they're light on this, they want this, they have this issue, that issue, and this requirement. Okay, perfect fit for Omada." When we find that, we end up with really happy customers because we can show them some progress in 30, 60, or 90 days, as opposed to a two-year deployment in other cases.

We are using Omada Identity Cloud, their SaaS version, as part of our identity and access management proposition towards our customers. We are an IT security company situated in the Netherlands. What we're trying to do: We give our customers guidance in their needs, aims, and goals regarding identity and access management. Therefore, we are the trusted partner for our customers in order to give them control over their identity and access management landscape, and we use Omada for this. We provide managed services for our clients.

It is all cloud native. What we do, we say, "Dear customer: We can help bring your landscape under control from an identity and access management perspective. For that, we use Omada as our platform."

Omada Identity Cloud is part of our proposition to help us manage environments. If we don't have a product underneath, then it is quite difficult. Therefore, we had to choose a product solution to make our proposition believable.

The governance part is the most valuable feature. The governance processes are defined, and it is quite easy to report upon the compliance. The compliance reporting is very good. 

From my perspective, the IGA features cover everything and are quite broad.

They need to improve the cost for small companies.

We have just started to use this solution.

The scalability of the product is good. There is a lot of functionality within it, without paying extra costs. It is quite complete on its own, and there are no hidden costs. 

It scales in terms of numbers and types of identities. It can govern the on-premise applications as well as the cloud applications. So, it can manage hybrid environments with all types of identities and various load amounts. 

They know what they are doing when setting up the business because this is their core business. There is no waiting time if you need to schedule a meeting with them. They provide a quick response time. Compared to other solutions, their response time is fast and done in a short amount of time.

We are starting the configuration stage right now. 

The initial setup has been straightforward. It is a quick setup, which is flexible and user-friendly.

They set up the environment, which makes it almost immediately available for us. Then, we can configure the solution for our customers' needs, as the customer wants, and as we think is best for our customers. That makes it flexible, so we do not have to make any big investments in terms of hardware.

We have a customer lead who is responsible for all contact with a given customer. We also have a project manager finishing the implementation process, then we have a couple of engineers and a solution architect. There are about five people who are involved.

With a SaaS solution, you don't have to buy something, install it, and activate it on your balance sheet. That is one of the clear benefits. 

They offer a complete solution. However, the pricing is too high for SMBs.

With the cloud solution, spinning up the system is quite easy. Afterwards, you configure and pay for all the use by customers, which is then paid by the customers.

We evaluated other vendors from the Gartner Magic Quadrant (the ones that were near Omada Identity Cloud) when looking for a solution. 

We are just starting with this product. We have a clear vision of what we want with our proposition, so we chose Omada Identity because it is a good product in regards to scalability and being a cloud-native solution.

We feel Omada has the same understanding of what is going on in the market as us. Our strategies are quite well-aligned. The decision to choose Omada Identity Cloud was not only about the product, but at least 50 percent about the company too.

It is very important that it is a cloud-native solution. The world is moving towards the cloud, which is a trend that you cannot change. Based on that, it is quite evident that you want a partner that has a product from a cloud-native perspective. Assets are less on-premise and more on the cloud now, so it's more about functionality and processing as well as taking it as a service. We want to move along with that trend.

I would rate this solution as an eight out of 10. There is always room for improvement.

I am the functional manager. I use the solution for user access management.

The product provides good security. Every access is secure. We saw the benefits of the solution right after the deployment.

The administrative features and SoD are valuable.

It would be nice if we could use queries. It is not possible to customize reports on Omada Identity. Everything is fixed. We can only use the standard options. It would be very nice if we could write queries using the SQL database.

I have been using the solution for 2.5 years.

The tool is stable.

The tool's scalability is fine.

My team contacts the support team. The support is slow.

Neutral

I worked with One Identity before. We could customize reporting using One Identity. Omada Identity and One Identity have their positives and negatives. Omada is a better tool. However, some features are not very good. The reporting takes more work on Omada.

The deployment is not easy. It takes too long. My colleagues always have issues after deployment.

My colleagues deployed the product in my organization.

The reporting is very poor. It is impossible to see which people are under what rules. Omada is set up to remove employees' access as soon as they leave our organization. It works very well.

I use Omada for role-based access control. We can create roles for the team or members of the organization. When they leave the organization, the role is removed automatically. It is beneficial to us.

Even though I use Omada, I still need the other systems we use. Omada helps automate reviews of access requests and reroutes them to the appropriate people. I use Omada Connectivity Community, but not much.

Overall, I rate the product a 7 out of 10.

My primary use cases of this solution are to manage the life cycle of identities, manage authorizations for applications, and the re-certification of authorizations.

The most valuable feature of this product is that it gives you a dashboard on which applications the user has access. It's also a user-friendly solution. 

I would like to see some additional functionality and improvements in usability.

I have been using this solution for one and a half years.

This solution's stability is fine, with no issues. Maintenance requires three to four people.

We had good support from the supplier for this product.

Before you start implementation, you should think about the impact the solution will have on the company. Also, if you have very old or obsolete data, you should remove it prior to implementation. I would rate this solution as eight out of ten.

Our primary use cases are around employee life cycle processes. Employees join us, extend their contracts, move around, and leave us. Omada is connected to our HR system as well as SAP, Microsoft Exchange, and Active Directory.

We also use it for updating our employee master data and use the request management, covering about 900 employees.

We are an Omada partner and reseller.

The best feature in Omada Identity is that it enables us to implement standardized employee life cycle processes so that we don't have to create them ourselves. We can then use the standard workflows.

The breadth and scope of the solution’s IGA features also fulfill our requirements. 

We are trying to use Omada's standards and to adapt our processes. But we have had some trouble with the bad documentation. This is something that they could improve on. It has not been possible for us to analyze some of the problems so far, based on the documentation. We always need consultants. The documentation should include some implementation hints and some guidelines for implementing the processes. It's an area that could definitely be improved.

We have been using Omada Identity for about a year.

We have not had any major issues with the system so far.

We are planning to implement more and more of these standard processes and to connect more target systems to it.

We haven't submitted any support tickets to Omada so far because we have been solving our issues with consultants.

Our previous solution was developed in-house by my colleagues. We switched to Omada because the old solution did not have any standards. In addition, the components it used were end-of-life and we decided to use software that offers more standards out-of-the-box.

The initial setup was complex. We have so many different stakeholders in our company and they all have their specific requirements, but we were trying to standardize things. We have struggled with all the requirements and have tried to reduce the special implementations to a standard.

Our implementation of Omada took about half a year.

In terms of maintaining the solution, we have four people involved. Two are technical application managers who are in charge of the operation of the system. And we have two guys who are mainly dealing with the implementation of the employee processes, connecting to the target systems, as well as some scripting.

We used consultants from Omada. Our experience with them was okay.

So far, we have not saved money compared to our previous solution because we are struggling with some internal issues. We have had some trouble with our HR data, but we expect that we will save money, using Omada, by the end of this year.

Because we are a partner and an IT service provider, we have a special licensing agreement because we are planning to offer Omada Identity to our customers. Our licensing and pricing model differs from the standard.

Because we operate this on-premises and just connect it to internal systems, we have had no security issues so far.

Be sure to use Omada's standards and try to reduce special implementations. You may have to adapt your processes to reduce all the specific requirements from the stakeholders. But my advice is to reduce the special requirements to a minimum.

Also, because you're connecting the HR system to the employee master data and organizational data, all this data has to be clean. Otherwise, you will have a lot of trouble with Omada. Make sure your master data is in good shape.

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.