Repository navigation
[FEATURE] Support implicit flow #704
Description
Is your feature request related to a problem? Please describe.
I tried to setup OIDC for guacamole, which failed as guacamole only support implicit flow
Describe the solution you'd like
Tiny Auth should support implicit flow, and the user should be able to select which flow to use per application (probably using an environment variable for each service like the rest of the conf)
Describe alternatives you've considered
No OIDC on guacamole (not the end of the world as there's the standard authentification available)
Activity
github-actions commentedon Apr 10, 2026
This issue has been inactive for 30 days and will be marked as stale.
github-actions commentedon May 11, 2026
This issue has been inactive for 30 days and will be marked as stale.
github-actions commentedon May 18, 2026
Closed for inactivity.
steveiliop56 commentedon May 18, 2026
Ah stupid bot.
Juff-Ma commentedon Jun 1, 2026
+1
Not because of actual application issues but rather because I think it makes more sense for tinyauth to use implicit flow. For tinyauth, an Admin always has to configure an app and thereby implicitely grants it trust. It feels weird to require each user's consent.
Tinauths scope (seem to be?)/are smaller deployments where any application associated with it automatically is trusted. Explicit flows only really come in handy when an App is inherently untrusted (i.e. user defined apps or SaaS providers).
Also, having to reconfirm every login is tedious. Even if explicit flow stays the default, is that really required? I think the user confirming the App once should be saved.
scratchmex commentedon Jul 18, 2026
remember to support the feature by upvoting the first message ^