Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Whitelist per TFA domain? #57

Closed
gvdhoven opened this issue Jul 9, 2019 · 5 comments
Closed

Whitelist per TFA domain? #57

gvdhoven opened this issue Jul 9, 2019 · 5 comments
Labels
enhancement New feature or request

Comments

@gvdhoven
Copy link

gvdhoven commented Jul 9, 2019

Precondition: I have one TFA instance deployed, with for example google auth configured.
i want to secure both domain1 & domain2; but domain1 i would only want to allow some@user.com and for domain2 i want to allow both users. Is this currently possible to use docker compose and inject separate whitelists per container?

@thomseddon
Copy link
Owner

No! But it's a good idea, this could be something that we integrate into the rules config.

@thomseddon thomseddon added the enhancement New feature or request label Jul 9, 2019
@gvdhoven
Copy link
Author

@thomseddon maybe it would be an idea to have more options configurable per domain (for example clientId/Secret to still allow different login flows but with only one TFA instance). P.s. is the lifetime cookie setting also thesame name in v1?

@thomseddon
Copy link
Owner

This has been proposed in #63

@cstack89
Copy link

This is similar to what I'm looking for, but a little different. I'd like to look at the scope of the token and have configurable rules for that. Like securing /admin to only allow users with an admin scope.

Also instead of having rules at this level, could they be passed in from traefik on the URL? Like /auth?scope=admin or /auth?username=joe

@thomseddon
Copy link
Owner

Planning to merge in #169

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants