Package: adsk-flaskoidc
FlaskOIDCThis package relies purely on theAuthlibpackage.AuthlibA wrapper of Flask with pre-configured OIDC support. Ideal for microservices architecture, each request will be authenticated using Flask'sbefore_requestmiddleware.
Necassary endpoints can be whitelisted using an environment variableFLASK_OIDC_WHITELISTED_ENDPOINTS.Installation:pip3installflaskoidcUsage:After simply installing the flaskoidc you can simply use it like below:fromflaskoidcimportFlaskOIDCapp=FlaskOIDC(__name__)Configurations:Please make sure to extend your configurations fromBaseConfig(only if you are sure what you are doing. Recommended way is to use the environment variables for the configuration.)fromflaskoidcimportFlaskOIDCfromflaskoidc.configimportBaseConfig# Custom configuration class, a subclass of BaseConfigCustomConfig(BaseConfig):DEBUG=Trueapp=FlaskOIDC(__name__)app.config.from_object(CustomConfig)FollowingENVIRONMENT VARIABLESMUST be set to get the OIDC working.FLASK_OIDC_PROVIDER_NAME(default: 'google')The name of the OIDC provider, likegoogle,okta,keycloaketc. I have verified this package only for
google, okta and keycloak. Please make sure to open a new issue if any of your OIDC provider is not working.FLASK_OIDC_SCOPES(default: 'openid email profile')Scopes required to make your client works with the OIDC provider, separated by a space.OKTA: make sure to addoffline_accessin your scopes in order to get the refresh_token.FLASK_OIDC_USER_ID_FIELD(default: 'email')Different OIDC providers have different id field for the users. Make sure to adjust this according to what
your provider returns in the user profile i.e.,id_token.FLASK_OIDC_CLIENT_ID(default: '')Client ID that you get once you create a new application on your OIDC provider.FLASK_OIDC_CLIENT_SECRET(default: '')Client Secret that you get once you create a new application on your OIDC provider.FLASK_OIDC_REDIRECT_URI(default: '/auth')This is the endpoint that your OIDC provider hits to authenticate against your request.
This is what you set as one of your REDIRECT URI in the OIDC provider client's settings.FLASK_OIDC_CONFIG_URL(default: '')To simplify OIDC implementations and increase flexibility, OpenID Connect allows the use of a "Discovery document," a JSON document found at a well-known location containing key-value pairs which provide details about the OpenID Connect provider's configuration, including the URIs of the authorization, token, revocation, userinfo, and public-keys endpoints.Discovery Documents may be retrieved from:Google:https://accounts.google.com/.well-known/openid-configurationOKTAhttps://[YOUR_OKTA_DOMAIN]/.well-known/openid-configurationhttps://[YOUR_OKTA_DOMAIN]/oauth2/[AUTH_SERVER_ID]/.well-known/openid-configurationAuth0: https://[YOUR_DOMAIN]/.well-known/openid-configuration`Keycloak: http://[KEYCLOAK_HOST]:[KEYCLOAK_PORT]/auth/realms/[REALM]/.well-known/openid-configurationA few other environment variables along with their default values are.# Flask `SECRET_KEY` config valueFLASK_OIDC_SECRET_KEY:'!-flask-oidc-secret-key'# Comma separated string of URLs which should be exposed without authentication, else all request will be authenticated.FLASK_OIDC_WHITELISTED_ENDPOINTS:"status,healthcheck,health"You can also set the config variables specific toFlask-SQLAlchemyusing the same key as the environment variables.# Details about this below in the "Session Management" section.SQLALCHEMY_DATABASE_URI:'sqlite:///sessions.db'Known Issues:Need to make sure it still works with the clients_secrets.json file or via env variables for each endpoint of a custom OIDC provider.refresh_tokenis not yet working. I am still trying to figure out how to do this using Authlib.You may enter problems when installing cryptography, check itsofficial document