Alternatives to Azure Active Directory logo

Alternatives to Azure Active Directory

AWS IAM, Okta, Auth0, Amazon Cognito, and Keycloak are the most popular alternatives and competitors to Azure Active Directory.
189
209
+ 1
3

What is Azure Active Directory and what are its top alternatives?

It is a comprehensive identity and access management solution that gives you a robust set of capabilities to manage users and groups. You can get the reliability and scalability you need with identity services that work with your on-premises, cloud, or hybrid environment.
Azure Active Directory is a tool in the Password Management category of a tech stack.

Top Alternatives to Azure Active Directory

  • AWS IAM

    AWS IAM

    It enables you to manage access to AWS services and resources securely. Using IAM, you can create and manage AWS users and groups, and use permissions to allow and deny their access to AWS resources. ...

  • Okta

    Okta

    Connect all your apps in days, not months, with instant access to thousands of pre-built integrations - even add apps to the network yourself. Integrations are easy to set up, constantly monitored, proactively repaired and handle authentication and provisioning. ...

  • Auth0

    Auth0

    A set of unified APIs and tools that instantly enables Single Sign On and user management to all your applications. ...

  • Amazon Cognito

    Amazon Cognito

    You can create unique identities for your users through a number of public login providers (Amazon, Facebook, and Google) and also support unauthenticated guests. You can save app data locally on users’ devices allowing your applications to work even when the devices are offline. ...

  • Keycloak

    Keycloak

    It is an Open Source Identity and Access Management For Modern Applications and Services. It adds authentication to applications and secure services with minimum fuss. No need to deal with storing users or authenticating users. It's all available out of the box. ...

  • OAuth2

    OAuth2

    It is an authorization framework that enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. ...

  • Spring Security

    Spring Security

    It is a framework that focuses on providing both authentication and authorization to Java applications. The real power of Spring Security is found in how easily it can be extended to meet custom requirements. ...

  • Firebase Authentication

    Firebase Authentication

    It provides backend services, easy-to-use SDKs, and ready-made UI libraries to authenticate users to your app. It supports authentication using passwords, phone numbers, popular federated identity providers like Google, ...

Azure Active Directory alternatives & related posts

AWS IAM logo

AWS IAM

1.1K
734
26
Securely control access to AWS services and resources for your users
1.1K
734
+ 1
26
PROS OF AWS IAM
  • 23
    Centralized powerful permissions based access
  • 3
    Straightforward SSO integration
CONS OF AWS IAM
  • 1
    Cloud auth limited to resources, no apps or services
  • 1
    No equivalent for on-premise networks, must adapt to AD

related AWS IAM posts

Okta logo

Okta

310
662
59
Enterprise-grade identity management for all your apps, users & devices
310
662
+ 1
59
PROS OF OKTA
  • 12
    REST API
  • 9
    SAML
  • 5
    OIDC OpenID Connect
  • 5
    User Provisioning
  • 5
    Easy LDAP integration
  • 4
    API Access Management - oAuth2 as a service
  • 4
    Universal Directory
  • 4
    Protect B2E, B2B, B2C apps
  • 3
    SSO, MFA for cloud, on-prem, custom apps
  • 3
    Easy Active Directory integration
  • 3
    Tons of Identity Management features
  • 1
    SWA applications Integration
  • 1
    SOC2
CONS OF OKTA
  • 2
    Pricing is too high
  • 1
    Okta verify (Multi-factor Authentication)

related Okta posts

Hey all, We're currently weighing up the pros & cons of using Firebase Authentication vs something more OTB like Auth0 or Okta to manage end-user access management for a consumer digital content product. From what I understand so far, Something like Firebase Auth would require more dev effort but is likely to cost less overall, whereas OTB, you have a UI-based console which makes config by non-technical business users easier to manage. Does anyone else have any intuitions or experiences they could share on this, please? Thank you!

See more
Auth0 logo

Auth0

1.1K
1.7K
208
Token-based Single Sign On for your Apps and APIs with social, databases and enterprise identities
1.1K
1.7K
+ 1
208
PROS OF AUTH0
  • 63
    JSON web token
  • 31
    Integration with 20+ Social Providers
  • 20
    It's a universal solution
  • 20
    SDKs
  • 14
    Amazing Documentation
  • 11
    Heroku Add-on
  • 8
    Enterprise support
  • 7
    Extend platform with "rules"
  • 7
    Great Sample Repos
  • 4
    Azure Add-on
  • 3
    Passwordless
  • 3
    Easy integration, non-intrusive identity provider
  • 2
    It can integrate seamlessly with firebase
  • 2
    Ruby
  • 2
    Great documentation, samples, UX and Angular support
  • 2
    Polished
  • 2
    On-premise deployment
  • 1
    Will sign BAA for HIPAA-compliance
  • 1
    SAML Support
  • 1
    Active Directory support
  • 1
    Springboot
  • 1
    SOC2
  • 1
    Great support
  • 1
    OpenID Connect (OIDC) Support
  • 0
    A';P[];Æ`/
CONS OF AUTH0
  • 12
    Pricing too high (Developer Pro)
  • 7
    Poor support
  • 4
    Status page not reflect actual status
  • 3
    Rapidly changing API

related Auth0 posts

Stephen Gheysens
Senior Solutions Engineer at Twilio · | 14 upvotes · 425.6K views

Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

See more

Hey all, We're currently weighing up the pros & cons of using Firebase Authentication vs something more OTB like Auth0 or Okta to manage end-user access management for a consumer digital content product. From what I understand so far, Something like Firebase Auth would require more dev effort but is likely to cost less overall, whereas OTB, you have a UI-based console which makes config by non-technical business users easier to manage. Does anyone else have any intuitions or experiences they could share on this, please? Thank you!

See more
Amazon Cognito logo

Amazon Cognito

477
735
33
Securely manage and synchronize app data for your users across their mobile devices
477
735
+ 1
33
PROS OF AMAZON COGNITO
  • 14
    Backed by Amazon
  • 7
    Manage Unique Identities
  • 3
    Work Offline
  • 3
    MFA
  • 2
    Store and Sync
  • 1
    It works
  • 1
    Integrate with Google, Amazon, Twitter, Facebook, SAML
  • 1
    SDKs and code samples
  • 1
    Free for first 50000 users
CONS OF AMAZON COGNITO
  • 3
    Massive Pain to get working
  • 2
    Login-UI sparsely customizable (e.g. no translation)
  • 2
    Documentation often out of date
  • 1
    MFA: there is no "forget device" function
  • 1
    Hard to find expiration times for tokens/codes
  • 1
    Lacks many basic features
  • 1
    There is no "Logout" method in the API
  • 1
    No recovery codes for MFA
  • 1
    Difficult to customize (basic-pack is more than humble)
  • 1
    Only paid support
  • 1
    Docs are vast but mostly useless

related Amazon Cognito posts

I'm starting a new React Native project and trying to decide on an auth provider. Currently looking at Auth0 and Amazon Cognito. It will need to play nice with a Django Rest Framework backend.

See more
Keycloak logo

Keycloak

450
859
65
An open source identity and access management solution
450
859
+ 1
65
PROS OF KEYCLOAK
  • 25
    It's a open source solution
  • 18
    Supports multiple identity provider
  • 11
    OpenID and SAML support
  • 6
    Easy customisation
  • 5
    JSON web token
CONS OF KEYCLOAK
  • 2
    Okta
  • 2
    Poor client side documentation
  • 2
    Lack of Code examples for client side

related Keycloak posts

Joshua Dean Küpper
CEO at Scrayos UG (haftungsbeschränkt) · | 7 upvotes · 343.1K views

As the access to our global REST-API "Charon" is bound to OAuth2, we use Keycloak inside Quarkus to authenticate and authorize users of our API. It is not possible to perform any un-authenticated requests against this API, so we wanted to make really sure that the authentication/authorization component is absolutely reliable and tested. We found those attributes within Keycloak, so we used it.

See more
Shared insights
on
OktaOktaKeycloakKeycloak

I want some good advice on which one I should prefer. (Keycloak or Okta) Since Keycloak is open source, it will be our first preference, but do we face some limitations with this approach? And since our product is SAAS based and we support the following authentications at present. 1. AT DB level 2. 3rd part IDP providers 3. LDAP/AD...

See more
OAuth2 logo

OAuth2

436
439
0
An open standard for access delegation
436
439
+ 1
0
PROS OF OAUTH2
    Be the first to leave a pro
    CONS OF OAUTH2
      Be the first to leave a con

      related OAuth2 posts

      Joshua Dean Küpper
      CEO at Scrayos UG (haftungsbeschränkt) · | 7 upvotes · 343.1K views

      As the access to our global REST-API "Charon" is bound to OAuth2, we use Keycloak inside Quarkus to authenticate and authorize users of our API. It is not possible to perform any un-authenticated requests against this API, so we wanted to make really sure that the authentication/authorization component is absolutely reliable and tested. We found those attributes within Keycloak, so we used it.

      See more
      Isaac Ogunleye
      Backend Developer at Coast research Institute · | 5 upvotes · 66.2K views
      Shared insights
      on
      PassportPassportOAuth2OAuth2

      My teammates and I are arguing on which library to use for our local and social authentication in our express app between OAuth2 and Passport. I went for Passport cause I personally like it, and it seems easier to implement with good docs, but some of my teammates think it's less secure than OAuth2. So any advice please would be appreciated. Thanks 🙏🏻

      See more
      Spring Security logo

      Spring Security

      416
      422
      4
      A powerful and highly customizable authentication and access-control framework
      416
      422
      + 1
      4
      PROS OF SPRING SECURITY
      • 2
        Easy to use
      • 2
        Java integration
      CONS OF SPRING SECURITY
        Be the first to leave a con

        related Spring Security posts

        Firebase Authentication logo

        Firebase Authentication

        370
        470
        52
        An App Authentication System In A Few Lines Of Code
        370
        470
        + 1
        52
        PROS OF FIREBASE AUTHENTICATION
        • 11
          Completely Free
        • 8
          Native App + Web integrations
        • 8
          Email/Password
        • 6
          Passwordless
        • 6
          Works seemlessly with other Firebase Services
        • 5
          Integration with OAuth Providers
        • 4
          Easy to Integrate and Manage
        • 4
          Anonymous Users
        CONS OF FIREBASE AUTHENTICATION
        • 3
          Heavy webpack

        related Firebase Authentication posts

        Stephen Gheysens
        Senior Solutions Engineer at Twilio · | 14 upvotes · 425.6K views

        Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

        My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

        See more

        Hey all, We're currently weighing up the pros & cons of using Firebase Authentication vs something more OTB like Auth0 or Okta to manage end-user access management for a consumer digital content product. From what I understand so far, Something like Firebase Auth would require more dev effort but is likely to cost less overall, whereas OTB, you have a UI-based console which makes config by non-technical business users easier to manage. Does anyone else have any intuitions or experiences they could share on this, please? Thank you!

        See more