Skip to content

Commit

Permalink
Fix disable-oauth-proxy example (#107)
Browse files Browse the repository at this point in the history
* Fix disable-oauth-proxy example

Signed-off-by: Juraci Paixão Kröhling <[email protected]>
  • Loading branch information
jpkrohling authored and objectiser committed Nov 9, 2018
1 parent 3ddcd1f commit 45d9731
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions README.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -179,7 +179,7 @@ oc get routes

NOTE: make sure to use `https` with the hostname/port you get from the command above, otherwise you'll see a message like: "Application is not available".

By default, the Jaeger UI is protected with OpenShift's OAuth service and any valid user is able to login. For development purposes, the user/password combination `developer/developer` can be used. To disable this feature and leave the Jaeger UI unsecured, set the Ingress property `oauth-proxy` to `false`:
By default, the Jaeger UI is protected with OpenShift's OAuth service and any valid user is able to login. For development purposes, the user/password combination `developer/developer` can be used. To disable this feature and leave the Jaeger UI unsecured, set the Ingress property `security` to `none`:

[source,yaml]
----
Expand All @@ -189,7 +189,7 @@ metadata:
name: disable-oauth-proxy
spec:
ingress:
oauth-proxy: false
security: none
----

== Auto injection of Jaeger Agent sidecars
Expand Down
2 changes: 1 addition & 1 deletion deploy/examples/openshift/disable-oauth-proxy.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,4 @@ metadata:
name: disable-oauth-proxy
spec:
ingress:
security: oauth-proxy
security: none

0 comments on commit 45d9731

Please sign in to comment.