Repository navigation
[FEATURE] Support sourcing User-Email from a LDAP user attribute #699
Description
Is your feature request related to a problem? Please describe.
Now with added LDAP groups support I am considering adding Tinyauth to my auth stack as a auth_request handler. I'd like to use the Headers feature with my existing LDAP instance, as I asked in #692.
Describe the solution you'd like
Add support for sourcing the header data from LDAP. Maybe even add LDAP support to custom headers?
Describe alternatives you've considered
Not using Tinyauth/not using headers? idk
Additional context
I may give adding the feature in myself a try during the coming weeks if i have the time. Great project btw keep up the good work!
Activity
Track3 commentedon Apr 4, 2026
+1 for this. The same issue occurs when using Tinyauth as an OIDC server — both local and LDAP users always have their email set to
username@domain. in order to set proper user email, it seems the only way is to rely on an external OIDC service. Since Tinyauth can act as an OIDC server now, it makes sense to support sourcing user email directly from LDAP user attribute.github-actions commentedon May 5, 2026
This issue has been inactive for 30 days and will be marked as stale.
yodatak commentedon May 5, 2026
I would love to have this feature to its realy difficult to use it for now with ldap backend without take the email from the user
steveiliop56 commentedon May 11, 2026
Added in #834.