Describe the bug
In case of a misconfigured login flow, token-based authentication may be necessary, which begins with generating a token. The process for this can be found on Authentik's official website under the Troubleshooting section titled "I can't log in to authentik": https://docs.goauthentik.io/docs/troubleshooting/login.
I chose to use the CLI method and successfully generated the token. However, there is no detailed documentation on how to use it. All I received was the following message:
"Store this link safely, as it will allow anyone to access authentik as #user.
/recovery/use-token/#verylongtoken"
To Reproduce
Steps to reproduce the behavior:
Log into the CLI: Access the Authentik server's command line interface.
Run the following command: ak create_recovery_key X #user (Replace X with the number of years the token should remain active, Replace #user with the username of the affected user for whom you want to generate the token.)
Describe the bug In case of a misconfigured login flow, token-based authentication may be necessary, which begins with generating a token. The process for this can be found on Authentik's official website under the Troubleshooting section titled "I can't log in to authentik": https://docs.goauthentik.io/docs/troubleshooting/login.
I chose to use the CLI method and successfully generated the token. However, there is no detailed documentation on how to use it. All I received was the following message:
"Store this link safely, as it will allow anyone to access authentik as #user. /recovery/use-token/#verylongtoken"
To Reproduce Steps to reproduce the behavior:
Log into the CLI: Access the Authentik server's command line interface.
Run the following command: ak create_recovery_key X #user (Replace X with the number of years the token should remain active, Replace #user with the username of the affected user for whom you want to generate the token.)
Use the generated link: Attempt to use the provided link to access the recovery process. For example, I tried: https://mydomain.tld/recovery/use-token/#verylongtoken This resulted in a "not found" error message.
Expected behavior Gain access to the Authentik admin interface by bypassing the faulty login flow using the recovery token.
Version and Deployment (please complete the following information):
Additional context Add any other context about the problem here.