Amazon Cognito vs. One Identity Identity Manager

Well Suited

1. B2C mobile and web apps with a high number of users.
2. Cheaper and cost-effective.
3. If the other pieces of the infra are already using AWS services like Lambda, S3, Pinpoint, etc.

Not Suited For:

1. Advanced use-cases (Biometrics based authentication) Email, and other MFA channels.
2. For any use-cases needing SCIM.
3. Customized flows of SSO, and MFA will need a layer on Lambda and other AWS services.

Incentivized

Well-suited: Companies with .NET or windows technology as a core. Companies with AD as main Directory Services Less appropriate: Companies with lot UNIX boxes Companies looking to support applications with many different connectors.

Incentivized

• Strong integration with React.js and client-side applications
• Easy to bridge Cognito identities with the rest of the AWS ecosystem
• Easy to store user profile data directly in Cognito rather than having to build additional services/endpoints
• Easy integration with AWS Lambda to extend and add sophistication to the service

Incentivized

• Audit Trace History: Out of the box enables important field to trace and give you flexibility to expand them thru configuration settings.
• Provisioning to Active Directory: Synchronization Editor gives you flexibility to define what and when needs to be on sync.
• Web Portal: Latest version is more user friendly and support mobile devices.

Incentivized

• SCIM implementation is not present.
• B2B SaaS use-cases are very hard to configure. More suitable or B2C use-cases.
• Needs more recipes, plugins, SDK's.
• 2FA with Email as an OTP channel is not supported.
• 2 FA using biometrics is not available; can be customised using lambda.

Incentivized

• Web Designer: Hard to implement a new form from scratch.
• Rest API: Make more methods available.
• Connector: More connectors required like SNOW, Workday,etc.

Incentivized

All the features AWS Cognito offers gives the user the options they need without making it too complicated. Your customers will be happy. On the administration site usability is also great. After a small learning curve, you can setup Cognito for your usage

Incentivized

AWS Support overall is poor. Your main resources are trainings and the docs, and the docs can be very confusing. Using Cognito well involves having a developer learn it deeply and help support your team in understanding it. That said, Cognito's competitors also have dismal support and even worse documentation, so while this isn't a strength for Cognito it may still be the frontrunner here.

Incentivized

They are ideal tools to create a secure and unique login experience for our applications. Thanks to its API authorization, Amazon Cognito ensures connections to applications that are secure.It is easy to use and provides easy access to files and applications that you need to complete your goal.

Incentivized

Selected due windows base technology, easy to deploy and AD connector.

Incentivized

• Amazon Cognito has had a positive impact on our business by allowing us to develop services that require user sign-up and sign-in more rapidly. Not only do we not need to build or maintain these features, but Cognito's implementation is also better than what we would be justified in building ourselves.
• Amazon Cognito makes user management easy. This reduces the time we have to spend supporting users. Non-technical product managers can even use the AWS Console to manage users without requiring support from developers.
• Amazon Cognito is likely more secure than what would be built in-house; a portion of our attack surface is now managed by Amazon.

Incentivized

• Positive impact because we now disable users immediately from the authoritative source.
• Positive impact due our integration with EPIC.

Incentivized