SAP Identity Management Reviews

We are a big SAP shop, so SAP IDM is the main identity provider for accessing all of the applications. This is not just for SSO but also for the provisioning and related tasks.

Rather than implement a basic SSO, this solution assisted us with setting up two-factor authentication.

The most valuable feature is that it is able to integrate with many modules and other applications. 

It needs to have the SSO for the HANA modules that SAP is releasing.

This solution is stable. We don't have any issues once it is moved to production, but it has challenges for new stuff that SAP is releasing because they don't have that kind of integration.

We do not have any issues with scalability.

The SAP technical support is pretty good.

The initial setup is pretty straightforward but it had to be catered to our needs. We did a lot of customization.

We did have a consultant but most of the implementation was done in-house.

There is definitely ROI because we use this as our enterprise-wide SSO solution.

My advice for others implementing this solution is to identify all of the systems that you need to connect to using SSO. Make sure that you have a unique identifier for each user, whether it be an employee ID or a username. Just make sure that it is available for IDM to provision it and do the sample authentications.

I would rate this solution an eight out of ten.

I like the core functionality of what IBM provides, like provisioning the triggers. Also, how you can maintain not only SAP back end systems, but non-SAP. The functionality that IBM provides if you're able to implement a certain logic, and if you can code, you can do a really good connector or UI. Basically the two allow you to be able to do whatever you want, not only as a UI, but as a connector but as internal logic for each customer.

For example, we have developed a lot of custom logic built within the standard functionality, i.e., the standard workflow. So, IBM is really powerful in this way, and it is nice tool, if you know how to build the things you want.

In my company, we don't use IBM. I'm just implementing IBM in other companies.

The current functionality allows you only to change one user at a time. There is no option to maintain the business roles from the UI using like standard validation, imports, or whatever you have to build your business roles one by one. Logging into the UI searching for the access you want, and for a lot of our customers in one business role, they have around thousands of roles, so it's a really hard process to do by hand.

So, maintaining the business roles is another topic that the functionality is missing, the notifications, because in 7.2 of IBM 8, it tried to improve the implementation of the notification functionality. But again, it is not so user-friendly. You have to be really IBM knowledgeable to maintain the notification process.

With the SAP 10, there is a menu from the web interface, and there you can monitor the work for the system. But there is no option to monitor or to start or restart the discussions. There is nothing to check the tasks, the jobs, what is the status, and if there is a job in another state, then you should use the console itself.

But for most of our customers, they are not so familiar with the IBM console. So, they want a nicer way to check if there is a problem with some of the jobs and tasks, and patches with the queue. Because, at the moment, it's really difficult for a person that is not so familiar with the tool itself to monitor.

I have been implementing it for five and a half years.

7.2 SP 6 was a really nice version. Now, SP-8 was pretty unstable. SP 10 is in process, like we have some problems with this SP level. And IBM 8, SP 4 is better.

No.

Basically, the developers that are building the tool are responsible for maintaining the tickets on second level. They are very knowledgeable. They are friendly and I am really satisfied from their behavior. A nine out of 10.

No. I started with the SAP version. I'm only familiar with this tool. But I switched between the different SP levels, and this version. So now we have clients on IBM 8 SP 4. We had them on SP 1 and 2 as well. I started with 7.2 SP 4 and SP 6. We also get some clients with SP-8, and now SP 10.

Basically, if you don't have any knowledge with SAP, and IBM is a different product, it is not like standard SAP, especially when we started. Because I know that this is not how is was originally, it was like bought from new region guys. So when I started, it was really strange for me as well. The IBM as a tool is a little bit complicated, the logic triggers everything and maintains the workflow. You have to think a little bit.

So, it was very challenging.

Maybe if you start using the solution with some courses or training, it would be easier. But the tool is not so easy to get to know.

When I started, there were no standard SAP trainings. When I started with this tool, there were no trainings going on around this tool, so I started learning on the fly. I read the documentation, the online help, and everything that was available. It was really helpful. Google it, you always get some discussion on it.

I thought the documentation is really nice, the online help is really nice. If you know where to look, and if you have colleagues like I had, that are pointing you in the right direction, it's not so hard.

Also, I know right now there are some really nice trainings.

Our customers use SAP IBM, and they chose this option because basically they have SAP already in their environment. They were using SAP, so it's the easiest option for them. I don't know what the other like processes in mind were about choosing this option for them.

Basically, all of them already had SAP. The SAP systems, HR, QA, etc. These also provided the option to connect, not only the SAP systems, they had in their environment, but to activate to pretty well-known non-SAP applications, like Magic, Google, and Exchange.

Overall, IBM really gives you the functionality. The power to implement a lot of functionality outside the current implementation.

If you know how to do it, how to build the functionality you want, you have that option to do it yourself.

The main idea is to review the SAP Analytics Cloud.

For our dealers, we send a monthly report about the sale and strength of floatation devices.

The most valuable feature is the user experience for managing information.

Research and marketing need to be improved.

I don't have any problems with the stability of this solution.

The scalability has not been a problem.

Our experience with technical support has been good.

We found the initial setup to be complex. It is not a technical team; rather, it is made up of users. The technical support was helpful.

We handled the implementation in-house.

I would rate this solution a nine out of ten.

I find it an excellent tool for data synchronization and cleansing. I also like how easy it is to extend the product.

As a consultant, I have found SAP IDM to bring increased efficiency and consolidation of tools needed for managing Identity and Access management in large corporations. It also helps with the centralization of audit and security based tasks.

The product needs better UI customization and the administration console is outdated in this version.

I've used it for 11 years. For SAP centric organizations, I would rate it 9.5/10.

Not in this release.

None.

None.

Mid-range, it is not uncommon to file a technical support request and then have days pass before getting results. It’s better to go to the product forum for support sometimes.

Identity management is never easy to setup. One cannot begin to implement this solution without extensive requirements and discovery analysis throughout the entire organization.

Before doing any configuration, gather requirements for use, and document use cases. Even if you are having a consultant come in to do the setup and initial configuration, have one or more people attend training. Document everything.

NW IDM is extremely flexible. With a small amount of effort you can integrate the basic provisioning for most of the commonly used modern systems.

Faster identity management integrated in user-friendly UI interfaces.

• DB Logic implementation
• Performance

Three years.

Yes, usually environments are complex and different - the OS varies from Windows to IBM AIX and Oracle Solaris, thus there might be different issues regarding deployment - however most of them are due to customer specifics not the actual product.

Yes up to SP07 there were some issues with the dispatcher stability. There are also some issues with the UI, the ACLs and performance - depending on the configuration and Identity DB size.

No, everything depends on the way the DB is maintained. When you have a well maintained DB then scalability is not an issue.

Very good expertise.

Very good expertise.

Not a product similar to NW IM in regards to its functionality and ways under which it could be operated.

Initial setup up for setting a plain Identity Center is straightforward and simple.

Implementation is done by me.

I do not know as I am on the other end - I am setting up, configuring and developing customizations for IDM.

No other options evaluated.

Provisioning framework, if not configured correctly could result in huge issues. Before even starting, you need to get a full picture from the customer on the Identity life-cycle process with all the smallest details. Missing anything here makes things very complicated with the project development.