Stats

Basic Doorkeeper repo stats
1
4,797
6.9
13 days ago

doorkeeper-gem/doorkeeper is an open source project licensed under MIT License which is an OSI approved license.

Doorkeeper Alternatives

Similar projects and alternatives to Doorkeeper based on common topics and language

  • GitHub repo Keycloak

    Open Source Identity and Access Management For Modern Applications and Services

  • GitHub repo authelia

    The Single Sign-On Multi-Factor portal for web apps

  • GitHub repo KrakenD

    Ultra performant API Gateway with middlewares

  • GitHub repo oauth2-proxy

    A reverse proxy that provides authentication with Google, Github or other providers.

  • GitHub repo glewlwyd

    Single Sign On server, OAuth2, Openid Connect, multiple factor authentication with, HOTP/TOTP, FIDO2, TLS Certificates, etc. extensible via plugins

  • GitHub repo fusionauth-issues

    FusionAuth issue submission project

  • GitHub repo hydra

    OpenID Certified™ OpenID Connect and OAuth Provider written in Go - cloud native, security-first, open source API security for your infrastructure. SDKs for any language. Compatible with MITREid.

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better Doorkeeper alternative or higher similarity.

Posts

Posts where Doorkeeper has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-03-10.
  • Authelia is an open-source authentication/authorization server with 2FA/SSO
    news.ycombinator.com | 2021-03-10
    One thing that is missing from this list is open source language specific libraries. Projects such as https://oauthlib.readthedocs.io/en/latest/oauth2/server.html and https://github.com/doorkeeper-gem/doorkeeper

    Depending on your use case, for example if you only have one application, you might be better off running something embedded in your app, or independent but using the same runtime/deployment environment. Then, when you are ready to add another app or integration, you should be able to introduce a standalone auth system more easily if appropriate (because all your auth interactions should be relatively standardized). I'm a big fan of standalone auth systems as a way to simplify access control and give a single view of a user/customer, but you can also succeed using open source embedded libraries.

    When the moment comes to introduce a standalone system, you should consider a few dimensions (this list pulled from a previous comment of mine: https://news.ycombinator.com/item?id=26360048 ):

       * open source or not