Extend the Remote User Auth backend with REMOTE_GROUPS ability#311
Extend the Remote User Auth backend with REMOTE_GROUPS ability#311
Conversation
f274c48 to
e4a5a85
Compare
There was a problem hiding this comment.
In general I'm nervous about code cleanups like this because it's extra surface area for conflicts when integrating with upstream
There was a problem hiding this comment.
is wildcard support something we need currently?
There was a problem hiding this comment.
I don't know how the actual group notation for us is (@robotblake?) but nested groups is certainly a thing in LDAP which would make setting this stuff up simpler.
There was a problem hiding this comment.
It's somewhat arbitrary, it doesn't hurt to have this though and I'm guessing while we probably won't use it right now I could see it being useful going forward.
There was a problem hiding this comment.
I changed my mind, this is a risk to land this upstream, backed it out again.
e4a5a85 to
02fcf1c
Compare
|
Looks good overall. |
cca066d to
bde4ca3
Compare
2618326 to
bf7370c
Compare
bde4ca3 to
c5f3043
Compare
|
@robotblake I've rebased the branch with current master, could you push your branch? You can also just push the old state and I do the rebasing ;) |
ecaaeda to
ea9c225
Compare
4ae2fe6 to
80d9ab6
Compare
c5f3043 to
3c5f58b
Compare
…ser groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
3c5f58b to
a84ec1e
Compare
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
Extend the Remote User Auth backend with the ability to pass remote user groups via a configurable request header similar to the REMOTE_USER header. Refs #37. If enabled the feature allows checks the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.
If enabled the feature allows checking the header value against a configured list of group names, including the ability to use UNIX shell-style wildcards.