-
```
OAUTH2_CLIENT_ID_REGEXP seems to be too restrictive (e.g. it won't accept
simple numeric client ids from 0 to 99), and cannot be changed without patching
OAuth2.inc.
Could this be a configurati…
-
```
OAUTH2_CLIENT_ID_REGEXP seems to be too restrictive (e.g. it won't accept
simple numeric client ids from 0 to 99), and cannot be changed without patching
OAuth2.inc.
Could this be a configurati…
-
```
OAUTH2_CLIENT_ID_REGEXP seems to be too restrictive (e.g. it won't accept
simple numeric client ids from 0 to 99), and cannot be changed without patching
OAuth2.inc.
Could this be a configurati…
-
```
OAUTH2_CLIENT_ID_REGEXP seems to be too restrictive (e.g. it won't accept
simple numeric client ids from 0 to 99), and cannot be changed without patching
OAuth2.inc.
Could this be a configurati…
-
```
OAUTH2_CLIENT_ID_REGEXP seems to be too restrictive (e.g. it won't accept
simple numeric client ids from 0 to 99), and cannot be changed without patching
OAuth2.inc.
Could this be a configurati…
-
### Steps To Reproduce
1. Go to 'https://bitwarden.mycompany.com/api/docs'
2. Click on 'Authorize'
3. Fill OAuth2 credentials (client_id, client_secret)
4. Select the single available scope "api…
-
hi. I followed the steps from README
`1. Get /oauth2/authorize?client_id=SampleClientId&response_type=code&redirect_uri=http://client.sso.com/login/oauth2/code/sso-loginscope=openid profile`
but the…
-
### OAuth2-Proxy Version
oauth2 v2.0
### Provider
github
### Current Behaviour of your Problem
In the oauth2-proxry configuration, we are configuring --skip-auth-route=["GET=/*"] which is skippin…
-
The docs show that the current client has options to set the user and password for basic authentication.
Was wondering if oauth2 could also be an option.
If not, would adding an oauth2 token to t…
-
I have my resource server where I want to configure the _security.oauth2.client_ properties:
```
security:
oauth2:
client:
clientId: my-service-id
clientSecret: my-service-id…