-
```
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…
-
```
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-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…
-
```
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…