ForgeRock Reviews

We use it to define the users in all of our systems like VMS and Samba. We don't use Windows, we use Samba. We create and define the permissions and configurations for the users. 

We were using Solaris IDM system, Solaris sells an IDM system and there was a big migration telling us where to go. They told us to rewrite the IDM solution and we saw which other solutions there were out there. We found this solution and we found someone who could create a proof of concept and we decided to change from Solaris IDM to this. It has the same functionality.

In the beginning, it was open-source as opposed to other solutions like IBM. We used Solaris IDM and we had to merge with another product and we chose this because, in our company, open-source software is the main solution. 

It's hard to speak with ForgeRock. It's very expensive. I find that it's quite expensive for just an open-source system. Support is quite expensive. We are only 300 users. It would make sense for a big company but for a little company, it's quite expensive. 

I have been using ForgeRock for around six to seven years. 

The stability is quite good. As an IDM system, it's not so stressed. We create five or six users per month. 

I heard that it's good for big companies, with thousands of users use it but our company only has a few hundred users. We use little bits of the database. Scalability isn't a problem for us. 

I have contacted their support. It's quite good. Out of ten, I would rate it a seven. 

I would rate it a seven out of ten. 

I would recommend trying it. Do a proof of concept. Every company is different. Management is different, you have to find a local company that can support you.

The interface is quite lively but I don't think that it's possible to have UI that's compatible with the rest of the company's. We only use the core of OpenIDM. 

We use the solution for the authorization and authentication of various applications.

The solution has the ability to handle a lot of users.

In an upcoming release, the solution could improve by limiting the need to do customizations.

I have been using the solution for more than three years. 

I find the solution to be stable, it has been working well. However, we have encountered some stability issues when we tried to upgrade. Normally we would have to reboot the server and occasionally have performance and tunning issues. The solution's stability during the upgrade should be improved.

The solution is very scalable. We have a lot of users that have been increasing over the years that we have been using it. We have approximately 20,000 users.

Whenever we experience an incident, we call everyone in the breach and the system owner expert will call the support of the solution. The support could improve because we sometimes have to repeat ourselves since the support is across different time zones.

The initial setup of the solution was quite complex because we tried to use it as a Single Sign-On with multiple applications or customers. 

The solution requires a vendor consultant for the implementation to make the right choices. 

The pricing of the solution is fair but I do not have the full details.

My advice to other users is to be careful about customizing the solution. If you customize the solution you will need good documentation and information that will have to be retained otherwise, there will be a knowledge gap. Especially if you use it for Single Sign-On or federated authentication and authorization. The more you customize it the more it will cause some issues when you are trying to upgrade. We have found in this particular instance if you do the customization you should have certain consistent standards. If you have this solution across multiple teams, there is no single party that has an overview of the code, and what ends up happening is there is too much customization making the upgrades difficult. However, this all depends on the business.

If we are using the solution in a certain way, especially the authorization with customization can cause problems. Every application might have a different way to authorize its functions in the area. However, the authentication is very straightforward. You have to be careful about customizing the solution, and how to sustain it across your teams. Every three to five years you will need to do an upgrade. Otherwise, you will not be supported. Most of us just treat it as a project, then we move on, and we do not use it until a few years later and then we run into large issues.

I rate ForgeRock a six out of ten. 

We are using off protocol to protect the application for multiple redirects and single redirects. We have multiple flows and from there an authentication perspective. We do have IDM in place to manage roles and also provisioning activities.

I like the way it is handling authentication and authorization.

I think the upgrade process is sometimes a little complicated and there are failures that occur.

I have been using ForgeRock for the past four years.

I have found ForgeRock to be stable.

The scalability of ForgeRock is not a problem. 

I have used technical support and they have a great team.

Positive

The support team is better than the other product we were using. If the support team is not good you have many issues.

The initial setup is not always straightforward. If we are looking to automate the process, that is not ready currently.  The time it takes to deploy is not a problem and is pretty easy.

I have also worked on Okta and PingFederate. I am comparing based on my experience with other products.

I would rate ForgeRock a nine out of ten.

My clients use the solution primarily for customer identity management, access management, customer onboarding, data management, and authentication.

The solution integrates well and it is important for them to keep up with the current trends in the market quickly enough, and they have been doing a good job at it.

The solution requires more simplified customization. However, part of the problem is my clients determining their own preferences. Technology can help and do many things, but you have to define your own policies to ensure that the solution or service works within those parameters. Helping customers understand their business and different processes is another issue not relating to the functionality of this solution.

The reports could be more customizable in an upcoming release, and the overall customization could be simplified by making drag-and-drop functionality.

I have been using this solution within 12 months.

I have found the solution stable.

There is a lot of options for scalability in this solution.

ForgeRock was born out of the open souced technology and users can use the community support without a license. Users with a commercial license can talk directly with the support agents that can immediately assist them with their problems.

The installation is very simple.

The license is purchased annually per user. However, you can negotiate if you are signing for a longer period of time. When comparing this solution to others on the market it is priced fair, it is not at the top of the price range or at the bottom end.

My advice to those wanting to implement ForgeRock is if they are looking for a strong customizable identity management solution that strikes the balance between convenience and security then this is probably a good choice for you.

I rate ForgeRock an eight out of ten.

Customization can be a difficult job.

I have been using ForgeRock for last three to four months. 

It is a customizable solution so if the customization is on track then it is stable. 

The technical support team is very good. 

Positive

I used Seapoint previously. 

As it is a new product I would rate it five out of ten. 

• Flexibility in the customisation.
• Out-of-the-box support for almost all authentication mechanisms/products.
• Hassle-free support to federation protocols (SAML can be enabled and configured in a few mouse clicks).

This is not directly applicable to me, as I work in the consulting service industry. However, I have seen how it's brought about improvements at our client locations. One of our clients wanted to have a solution with complicated authentication requirements (authenticate users from multiple sources and even from non-standard sources), and they approached several product vendors. ForgeRock was the only solution they found which fit their budget and time frame.

It has a promising roadmap and strategy. However, the product still needs to refactor and get rid of the dirty coding from its predecessor. I hope it will improve over time.

More than 10 years. I worked on its predecessor, Sun Java System Access Manager, as well.

Not with the version I’m reviewing. There were issues in previous versions but they were fixed over time.

I have never had any issues with scalability. It depends upon how we spec the environment as well.

It's awesome. Instant responses on support calls.

I used Oracle AM a little bit. Its configuration is a bit confusing and takes a long time.

As I said before, you can install and configure the product in a matter of a few minutes; it’s that easy.

I know it’s cheap compared to other leading AM products. You can even go for the Open Source version of the product if you are building it by yourself and don’t need the support and regular patches.

As I said, I work in the consulting/service industry, hence this is not directly applicable to me.

Just try it and get a feel for the product.

Integration with Identity repository and managing SAML2.0 SSO & Federation; provides a simple upgrade from Sun OpenSSO to OpenAM and ForgeRock OpenIDM; runs seamlessly with the Sun Identity Connector Framework; Unified Platform; lightweight Infrastructure; Connected Security; Developer-friendly AM solution.

The product was used mainly to migrate from Sun IAM suite. The integration has been smooth and the costs have been significantly reduced.

Reporting and Analysis capabilities seem to be less mature. 

Business strategic partnership model with multiple parties across marketing and sales needs improvement. 

Implementation, integration capabilities and support model are still evolving and posing a risk of poor quality.

3 years

Nothing significant.

I did, but I would rather blame my LDAP infrastructure. No significant issues with the product had been encountered that are worth mentioning.

No significant issues.

3; on a scale from 1-5 (1=worst, 5=best).

The key driver had been the migration from Sun IAM.

Migration involved analysis and solution design. The setup was of medium complexity.

The solution was implemented by a vendor. Level of required expertise was 3 on a scale from 1-5 (1=worst, 5=best).

Cost, increased time to market.

I evaluated Oracle Identity suite, TIM/TAM.

It may not have a complete suite of best-in-class IAM capabilities compared to some of the market leaders; however, they are maturing steadily and rapidly expanding the portfolio with OpenDJ and OpenIDM. It’s easy to configure and yes, it’s open source!

REST interface

Better Access Management

Less Oracle Java oriented.

Three years.

Not more then average.

Not more then average.

Not more then average.

Average.

Average.

Sun Access Manager, and we switched because SUN does not exist anymore.

Complex because of the customizations needed.

In house implementation.

We also looked at Oracle.

Start off with a pilot.