Repository navigation
[FEATURE] Allow different container names versus subdomain name for access controls #196
Description
I am hosting Tinyauth and my apps using Coolify with Traefik.
Coolify adds automatically an uuid to container names and propose by default the same name for the app URL.
So an app hello would be by default available at https://hello-uuid.example.com with a container name hello-uuid.
The subdomain can be changed so it is quite customary to get rid of the uuid and make the app available at https://hello.example.com
This breaks the access control functionality as described in the documentation https://tinyauth.app/docs/guides/access-controls.html
Could there be a workaround?
For example in the app traefik labels something like this that you can catch in the code to find out the container name.
labels:
- tinyauth.oauth.groups=admin
- tinyauth.comment=container_name:hello-uuid
Activity
steveiliop56 commentedon Jun 14, 2025
Hello!
Yeah this issue indeed exists. Adding a
tinyauth.app.domainlabel should be easy to include in the next release. You could dotinyauth.app.domain: whatever.example.comand tinyauth then looks it up when a requested.steveiliop56 commentedon Jun 15, 2025
Added in #198. You will be able to do
tinyauth.domain: app.mydomain.comand when you make a request tinyauth will get the domain fromX-Forwarded-Host, remove the port and search all containers for either the subdomain name or the label that contains this domain.