Our company has been using the solution to determine proof of concept for a project that is large-scale with over one million users. Through experimentation, we have found that some things work well and some things have issues.
We have 300 engineers using the solution but have determined our project cannot go to production because there are unresolved issues with B2C multifactor authentication.
The solution is proto-connective and integrates well with other AWS services.
The solution can be useful for small-scale, machine-machine projects. It can provide one kind of language that is the same for all connection partners.
The developer experience for mobile apps is terrible. Documentation is very poor and it is difficult to read the documents available to put things into practice. Our team has issues finding information related to using the solution.
SDK and libraries available for mobile apps are terrible. For example, if you use MFA to migrate one user from your database to the pool, you need to use Lambda functions or other methods in AWS to get the solution enabled.
It is extremely difficult to put a very, very scalable project into practice. Our team doesn't think you can use the solution for B2C on a large scale. We thought the solution would provide an agile experience but it does not.
The solution needs to keep a history of passwords. For example, you should be able to check if customers used the same password in the past when connecting to a company by username and password. This type of feature is a must for our project.
The MFA related to the solution's side is nonexistent. MFA should occur on the Facebook or Google side and also on the solution's side. This is a big problem because we have wallets, credit cards, and sensitive data stored for each customer. One layer of security is totally missing.
I have been using the solution for three months.
The solution does not seem stable because it performs and behaves differently for native and iOS apps. I cannot say the solution is stable for any one application.
Scalability is not so good so it is difficult to scale to future users. The solution works for some custom development but the backend needs to be more scalable. It does not seem that the solution is scalable in terms of features from both the backend and production sides.
Technical support is good so I rate it a five out of ten.
The setup is pretty easy but production is difficult.
Our team implemented the solution in-house. We have many teams so once we implement, other teams can do orchestration because we have a DDG domain-driven approach. You can see a vertical deployment in production even if teams are working independently.
Ongoing management is handled by five engineers.
The pricing is not so bad, so I rate it a two out of ten.
The solution works pretty well for some parts of our project but not well for parts related to our customer. For example, we need B2C to connect a mobile app experience but have a lot of problems with multifactor authentication so we cannot put the solution to production.
You can use the solution for proof of concept or starting projects that do not have a lot of users.
The solution will not work well for web apps or native applications that connect consumers in the end. It is not good for custom flows or the in-app experience. MFAs and social logins are not feasible with the solution.
I rate the solution a five out of ten.