The product needs to be available in marketplaces for subscription. They should offer competitive pricing models. There could be a better service line compared to Kong. It will help us further adapt and promote it easily.

This solution does not have BPM workflows already integrated, we had to integrate the BPM module externally. They do not provide full-featured auditing and certification modules out of the box.

In an upcoming release, they could improve the user interface by making it more user-friendly. Additionally, they have most of the connectors for the cloud version of the solution, but not on the on-premise or hybrid versions. We are left to come up with our own API-based connectors.

The code could be improved. I've had some difficulties working with the source code at times, but this could be due to inexperience.

Sometimes working with the code is difficult because I search for documentation about the code and how to work with the code, which is where I believe they should improve, by providing some documentation on how to work with the code.

I found that the product was too large, and therefore difficult for people such as myself who only wanted to make use of a single function. I was interested in the identity server, alone.

I would like to see a simpler and faster installation and configuration process for making use of individual components.

I have two suggestions for improving the product. First, improvements have to been made in the high availability architecture. This has to do with the master-slave replication, and how the load balancing is handled between the identity servers. The way in which it is handled has to be improved.

My second suggestion has to do with LDAP synchronization.  Ideally, the agents should be simplified beyond what they are now.

The solution could improve its development from a user perspective.

In a development environment, from a developer's perspective, there are a few ways they could simplify things. To understand scenarios and develop solutions can take some time.

The product could use more documentation, especially around the setup.

If you take one microservice, and one microservice wants to interact with another microservice, there are communication glitches that are happening at this moment. Those kinds of things have to be resolved. 

The need to ensure they are keeping up with the latest advancements, and especially be cognizant of security.

There may be memory issues if you haven't properly configured the policies.

This solution requires extensive knowledge to be used effectively as certain areas of its use are not user friendly.