Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow GET to /token/ to create a new API token if none exists #4672

Merged
merged 1 commit into from
Oct 3, 2023

Commits on Oct 3, 2023

  1. Allow GET to /token/ to create a new API token

    …if none exists. The old behavior of POST is unchanged for the sake of
    API stability.
    
    Something in releases prior to 2.023.37 was creating these tokens
    implicitly. It's not happening anymore, meaning that new accounts are
    left without API tokens, and the front end has never had any facility to
    send anything other than a GET to the token endpoint. To avoid the
    hassle of backfilling tokens for accounts that have none, or of
    rewriting the front end to send POST whenever GET returns a 404, this
    change simply allows a GET request to create a token implicitly if none
    exists.
    jnm committed Oct 3, 2023
    Configuration menu
    Copy the full SHA
    c825783 View commit details
    Browse the repository at this point in the history