Skip to content

Commit e62f555

Browse files
Merge pull request #203 from dastrobu/fix-README.md
fix json examples for --openshift-delegate-urls
2 parents aad1b28 + 51ac102 commit e62f555

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -116,14 +116,14 @@ Cons:
116116
Example:
117117

118118
# Allows access if the provided bearer token has view permission on a custom resource
119-
--openshift-delegate-urls='{"/":{"group":"custom.group","resource":"myproxy""verb":"get"}}'
119+
--openshift-delegate-urls='{"/":{"group":"custom.group","resource":"myproxy","verb":"get"}}'
120120

121121
# Grant access only to paths under /api
122-
--openshift-delegate-urls='{"/api":{"group":"custom.group","resource":"myproxy""verb":"get"}}'
122+
--openshift-delegate-urls='{"/api":{"group":"custom.group","resource":"myproxy","verb":"get"}}'
123123

124124
WARNING: Because users are sending their own credentials to the proxy, it's important to use this
125125
setting only when the proxy is under control of the cluster administrators. Otherwise, end users
126-
may be unwittingly provide their credentials to untrusted components that can then act as them.
126+
may unwittingly provide their credentials to untrusted components that can then act as them.
127127

128128
When configured for delegation, Oauth Proxy will not set the `X-Forwarded-Access-Token` header on
129129
the upstream request. If you wish to forward the bearer token received from the client, you will

0 commit comments

Comments
 (0)