From 153ea49c9974fb92e732234dd44001bcfdb31f5e Mon Sep 17 00:00:00 2001 From: Dolph Mathews Date: Fri, 27 Jun 2014 10:54:24 -0500 Subject: [PATCH] Remove duplicate section title Two sections were entitled 'Validate token', whereas the second should have distinguished itself from the first. Also added a line break after "New in version..." to show that the entire section is new, not just the one paragraph. Change-Id: If6dd9c099950d24f65e861b28f7fc80810c78225 --- v3/src/markdown/identity-api-v3.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/v3/src/markdown/identity-api-v3.md b/v3/src/markdown/identity-api-v3.md index 92a046ed..ea1f1246 100644 --- a/v3/src/markdown/identity-api-v3.md +++ b/v3/src/markdown/identity-api-v3.md @@ -1236,7 +1236,7 @@ Use cases: #### Authenticate: `POST /auth/tokens` -Each request to create a token contains an attribute with `identiy` +Each request to create a token contains an attribute with `identity` information and, optionally, a `scope` describing the authorization scope being requested. Example request structure: @@ -1765,11 +1765,12 @@ For example: } } -#### Validate token: `GET /auth/tokens` +#### Validate token and get service catalog: `GET /auth/tokens` To validate a token using the Identity API, pass your own token in the `X-Auth-Token` header, and the token to be validated in the `X-Subject-Token` -header. Example request: +header. The Identity service returns a service catalog in the response. +Example request: Headers: X-Auth-Token: 1dd7e3 @@ -1782,9 +1783,10 @@ token was issued by `POST /auth/tokens`. #### Validate token: `GET /auth/tokens?nocatalog` -*New in version 3.2* To validate a token using the Identity API without -receiving a catalog in the response. The request has the same format as -`GET /auth/tokens`. +*New in version 3.2* + +To validate a token using the Identity API without returning a service catalog in the +response. The request has the same format as `GET /auth/tokens`. The Identity service will return the exact same response as when the subject token was issued by `POST /auth/tokens?nocatalog`. @@ -3443,7 +3445,7 @@ Response: } The entity `links` section of a response using the `effective` query parameter also contains, -for entities that are included by virtue of group memebership, a url that can be used to +for entities that are included by virtue of group membership, a url that can be used to access the membership of the group. ### Policies