https://github.com/arxiv/arxiv-auth

Login page and core auth library
https://github.com/arxiv/arxiv-auth

authentication flask in-production jwt python

Last synced: about 2 months ago
JSON representation

Login page and core auth library

• Host: GitHub
• URL: https://github.com/arxiv/arxiv-auth
• Owner: arXiv
• License: mit
• Created: 2017-10-17T19:56:35.000Z (about 7 years ago)
• Default Branch: develop
• Last Pushed: 2024-10-24T16:06:32.000Z (2 months ago)
• Last Synced: 2024-10-25T22:21:51.197Z (2 months ago)
• Topics: authentication, flask, in-production, jwt, python
• Language: Python
• Homepage: https://arxiv.github.io/arxiv-auth/
• Size: 4.05 MB
• Stars: 18
• Watchers: 14
• Forks: 16
• Open Issues: 8
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# arXiv Auth

This repo provides applications and libraries to support authentication and

authorization, including /login, user sessions, account creation(TBD) and API

token management(TBD).

In this repository there are the following:

1. [``arxiv-auth/``](arxiv-auth/) contains the ``arxiv-auth`` package which

   provides a Flask add on and other code for working with arxiv authenticated

   users in arXiv services.  This provides core authentication and authorization

   functions and domain classes and provides integrations with the legacy

   database for users and sessions.

2. [``accounts/``](accounts/) contains web app for the login/logout pages,

   registration (TBD), profile management(TBD), etc.

3. [``cloud_auth/``](cloud_auth/) **Not in use** authentication for use as a

   FastAPI dependency that checks legacy cookies, NG JWTs and GCP OAuth2 tokens.

3. [``authenticator/``](authenticator/) **Not in use** contains the

   authenticator service. Handles authentication requests from NGINX

   in a cloud deployment scenario.

4. [``registry/``](registry/) **Not in use** contains the API client

   registry application. This implements OAuth2 workflows, client

   registration, and the root API landing page.

# How to get started

To get started look to the README.md for the directory of the component you are

looking to use.

# TODO

- Investigate the state of the registry service and clean up, test and document if useful.