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
When two or more application icons have the same name and the storage backend is set to s3, a random suffix is added to the file. When the application icon is changed or removed, the duplicate icon is not removed. No errors are shown to the user or are present in console to indicate a configuration error.
To Reproduce
Steps to reproduce the behavior:
Set the storage backend to s3 and configure it in your env file
Create 2 applications and assign them the same icon
Update the icon of one of the applications
Check the S3 bucket and notice the duplicate icon still present
Expected behavior
The second icon is removed
Screenshots
2 applications with same icon:
Ok, it works as expected:
The application icon is changed:
The old application icon is not removed:
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
Bucket is tied to a read-write user with the default policy of
Describe the bug
When two or more application icons have the same name and the storage backend is set to s3, a random suffix is added to the file. When the application icon is changed or removed, the duplicate icon is not removed. No errors are shown to the user or are present in console to indicate a configuration error.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The second icon is removed
Screenshots
2 applications with same icon:
Ok, it works as expected:
The application icon is changed:
The old application icon is not removed:
Logs
Output of docker-compose logs or kubectl logs respectively
Version and Deployment (please complete the following information):
Additional context
Bucket is tied to a read-write user with the default policy of
The text was updated successfully, but these errors were encountered: