This repository has been archived on 2020-03-24. You can view files and clone it, but cannot push or open issues or pull requests.

Joseph Schorr 8aac3fd86e Add support for an external JWT-based authentication system ... This authentication system hits two HTTP endpoints to check and verify the existence of users: Existance endpoint: GET http://endpoint/ with Authorization: Basic (username:) => Returns 200 if the username/email exists, 4** otherwise Verification endpoint: GET http://endpoint/ with Authorization: Basic (username:password) => Returns 200 and a signed JWT with the user's username and email address if the username+password validates, 4** otherwise with the body containing an optional error message The JWT produced by the endpoint must be issued with an issuer matching that configured in the config.yaml, and the audience must be "quay.io/jwtauthn". The JWT is signed using a private key and then validated on the Quay.io side with the associated public key, found as "jwt-authn.cert" in the conf/stack directory.		2015-06-05 13:20:10 -04:00
..
__init__.py	Get end-to-end configuration setup working, including verification (except for Github, which is in progress)	2015-01-07 16:20:51 -05:00
configutil.py	Move config handling into a provider class to make testing much easier	2015-01-09 16:23:31 -05:00
provider.py	Add proper error handling when the config volume is mounted in a read-only state.	2015-04-02 18:54:09 -04:00
superusermanager.py	Add an in-memory superusermanager, which stores the current list of superusers in a process-shared Value. We do this because in the ER, when we add a new superuser, we need to ensure that ALL workers have their lists updated (otherwise we get the behavior that some workers validate the new permission and others do not).	2015-01-20 12:43:11 -05:00
validator.py	Add support for an external JWT-based authentication system	2015-06-05 13:20:10 -04:00