-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add spontaneous scopes support to gluu-oauth-pep #414
Milestone
Comments
We should use the same path captures as in #415 to match path and scopes but on GG side. So we would be able not only check that scope match some regexp, but also match the path. IMO we should use the same {}, {1},... {n} notation to include the captured from the path. |
altexy
added a commit
that referenced
this issue
Apr 14, 2020
altexy
added a commit
that referenced
this issue
Apr 14, 2020
altexy
added a commit
that referenced
this issue
Apr 14, 2020
altexy
added a commit
that referenced
this issue
Apr 14, 2020
altexy
added a commit
that referenced
this issue
Apr 14, 2020
altexy
added a commit
that referenced
this issue
Apr 15, 2020
altexy
added a commit
that referenced
this issue
Apr 15, 2020
altexy
added a commit
that referenced
this issue
Apr 15, 2020
altexy
added a commit
that referenced
this issue
Apr 22, 2020
- remove default mapping - fix mapping without named group
altexy
added a commit
that referenced
this issue
Apr 22, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Root ticket #410
Here we should be able to specify a spontaneous scope(s) within our scope expressions.
We should match the particular scope of a token against regexp.
IMO, we may use
^
char at the beginning of scope as regexp mark.The text was updated successfully, but these errors were encountered: