You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
From the details page of an application, updating the slug of an application from the "Edit" tab does not redirect the user to the updated url leading to a bad UX and 404s. The only way to be able to interact with that application would be to go back to the main applications page and click on the updated application
To Reproduce
Steps to reproduce the behavior:
In the admin interface of the authentik dashboard, navigate to Applications > Applications and create an application named 'a'
Click on the newly created application and click edit and choose a new slug, 'b' for example.
Once confirmed, you will no longer be able to interact with the application and refreshing would lead to a loading page.
Expected behavior
The user should be redirected to the new application detail page. Just a UX thing.
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
Output of docker-compose logs or kubectl logs respectively
Version and Deployment (please complete the following information):
authentik version: 2024.10.1
Deployment: docker compose
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
From the details page of an application, updating the slug of an application from the "Edit" tab does not redirect the user to the updated url leading to a bad UX and 404s. The only way to be able to interact with that application would be to go back to the main applications page and click on the updated application
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The user should be redirected to the new application detail page. Just a UX thing.
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
Output of docker-compose logs or kubectl logs respectively
Version and Deployment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: