Skip to content

[BUG] when changing GENERIC_NAME to other then the default value (generic) is being ignored for services that uses traefik middlewares #353

Closed

Description

@falkheiland

Describe the bug
traefik setup.

services:
  tinyauth:
    image: ghcr.io/steveiliop56/tinyauth:v3
    environment:
      - APP_URL=https://auth0.example.com
      - GENERIC_NAME=MyGenericName #default:. generic
    deploy:
      labels:
        # defining the labels for other services:
        - "traefik.http.middlewares.tinyauth-auth0-secure.forwardauth.address=http://tinyauth:3000/api/auth/traefik"
        - "traefik.http.middlewares.tinyauth-auth0-secure.forwardauth.authResponseHeaders=remote-user, authorization"
        - "traefik.http.middlewares.tinyauth-auth0-secure.forwardauth.trustForwardHeader=true"

i can call the tinyauth just fine and authenticate with my OIDC endpoint (OpenText Advanced Authetication).

now i add the middleware to another service

services:
  homer:
    deploy:
      labels:
        - "tinyauth.domain=swarm0.example.com"

if i call now swarm0.example.com i get presented with the tinyauth webui -> press the now called "MyGenericName" button and a redirect is shown in the url bar which has a callback to auth0.example.com... callback...generic in it that is not working (should be MyGenericName)

the redirect to MyGenericName works with the tinyauth WebUI but not with the other service that uses a middleware via label.

if i comment GENERIC_NAME (and adapt the OIDC provider setting to generic) then both work

Activity

  1. changed the title [-][BUG] when changing GENERIC_NAME to other then the deafult value is being ignored for services that uses traefik middlewares[/-] [+][BUG] when changing GENERIC_NAME to other then the default value (generic) is being ignored for services that uses traefik middlewares[/+] on Sep 12, 2025
  2. steveiliop56 commented on Sep 12, 2025

    @steveiliop56
    Member

    Hello,

    The config option GENERIC_NAME is just an option to customize the name of the OAuth button in the login screen, nothing more. It isn't being used anywhere in the OAuth logic. This will be changed with #355 that will completely overhaul the OAuth logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions