From 98b6fafe92c78f91dbb0ce2b7b51ded909c2ebfb Mon Sep 17 00:00:00 2001 From: Phillip Webb Date: Fri, 5 Jun 2015 16:31:41 -0700 Subject: [PATCH] Fix broken docbook --- .../src/main/asciidoc/spring-boot-features.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc b/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc index 6ee4a400924..85678ab0b50 100644 --- a/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc +++ b/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc @@ -1504,11 +1504,11 @@ access tokens. If your appplication is also an Authorization Server it already k to decode tokens, so there is nothing else to do. If your app is a standalone service then you need to give it some more configuration, one of the following options: -* `spring.oauth2.resource.user-info-uri` to use the "/me" resource (e.g. -"`https://uaa.run.pivotal.io/userinfo`" on PWS) +* `spring.oauth2.resource.user-info-uri` to use the `/me` resource (e.g. +`https://uaa.run.pivotal.io/userinfo` on PWS) * `spring.oauth2.resource.token-info-uri` to use the token decoding endpoint (e.g. -"`https://uaa.run.pivotal.io/check_token`" on PWS). +`https://uaa.run.pivotal.io/check_token` on PWS). If you specify both the `user-info-uri` and the `token-info-uri` then you can set a flag to say that one is preferred over the other (`prefer-token-info=true` is the default).