From 2b260b19d23b517256e8c5245588b8f379a756cd Mon Sep 17 00:00:00 2001 From: Dave Syer Date: Wed, 14 Jan 2015 14:48:53 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- spring-cloud.html | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/spring-cloud.html b/spring-cloud.html index be13dab..8e1bf2f 100644 --- a/spring-cloud.html +++ b/spring-cloud.html @@ -2585,7 +2585,7 @@ running on port 8080.

To limit the scope that the client asks for when it obtains an access token -you can set oauth2.client.scope (comma separated or an array in YAML). By +you can set spring.oauth2.client.scope (comma separated or an array in YAML). By default the scope is empty and it is up to to Authorization Server to decide what the defaults should be, usually depending on the settings in the client registration that it holds.

@@ -2655,16 +2655,16 @@ following properties in the Environment:

  • -

    oauth2.client.* with * equal to clientId, clientSecret, +

    spring.oauth2.client.* with * equal to clientId, clientSecret, accessTokenUri, userAuthorizationUri and one of:

    • -

      oauth2.resource.userInfoUri to use the "/me" resource +

      spring.oauth2.resource.userInfoUri to use the "/me" resource (e.g. "https://uaa.run.pivotal.io/userinfo" on PWS), or

    • -

      oauth2.resource.tokenInfoUri to use the token decoding endpoint +

      spring.oauth2.resource.tokenInfoUri to use the token decoding endpoint (e.g. "https://uaa.run.pivotal.io/check_token" on PWS).

    @@ -2676,12 +2676,12 @@ you can set a flag to say that one is preferred over the other
  • -

    oauth2.resource.jwt.keyValue to +

    spring.oauth2.resource.jwt.keyValue to decode a JWT token locally, where the key is a verification key. The verification key value is either a symmetric secret or PEM-encoded RSA public key. If you don’t have the key and it’s public you can provide a URI where it can be downloaded (as a JSON object with a -"value" field) with oauth2.resource.jwt.keyUri. E.g. on PWS:

    +"value" field) with spring.oauth2.resource.jwt.keyUri. E.g. on PWS:

    $ curl https://uaa.run.pivotal.io/token_key
@@ -2698,7 +2698,7 @@ provide a URI where it can be downloaded (as a JSON object with a
 
    Warning
    
 
 
-If you use the oauth2.resource.jwt.keyUri the authorization
+If you use the spring.oauth2.resource.jwt.keyUri the authorization
 server needs to be running when your application starts up. It will
 log a warning if it can’t find the key, and tell you what to do to fix
 it.
@@ -2708,15 +2708,15 @@ it.

    You can set the preferred scope (as a comma-separated list or YAML -array) in oauth2.client.scope. It defaults to empty, in which case +array) in spring.oauth2.client.scope. It defaults to empty, in which case most Authorization Servers will ask the user for approval for the maximum allowed scope for the client.

    -

    There is also a setting for oauth2.client.clientAuthenticationScheme which +

    There is also a setting for spring.oauth2.client.clientAuthenticationScheme which defaults to "header" (but you might need to set it to "form" if, like Github for instance, your OAuth2 provider doesn’t like header -authentication). The oauth2.client.* properties are bound to an instance +authentication). The spring.oauth2.client.* properties are bound to an instance of AuthorizationCodeResourceDetails so all its properties can be specified.

    @@ -2767,7 +2767,7 @@ the matching patterns for the OAuth2 SSO, even if you have OAuth2SsoConfigurer beans as well. The default logout path is "/logout" and it gets similar treatment, as does the "home" page (which is the logout success page, defaults to "/"). Those paths can -be overriden by setting oauth2.sso.*' (`loginPath, logoutPath and +be overriden by setting spring.oauth2.sso.*' (`loginPath, logoutPath and home.path).

    @@ -3083,7 +3083,7 @@ service or the "resource" service if you have one).