keystone/api-ref/source/v3-ext
Colleen Murphy 22233747d2 Document token header in federation auth response
When reading the OS-FEDERATION API documentation, it is not clear how
to find the ID of the token when requesting either an unscoped or
scoped token. Token requests for the OS-FEDERATION API work the same
way as for the standard API, which is that the token ID is returned in
the X-Subject-Token header, so let's just mention that in the
OS-FEDERATION API documentation.

Change-Id: I6e9743d9001684f0d05ace119509f643c8b8e363
2016-11-28 09:06:25 -03:00
..
federation Document token header in federation auth response 2016-11-28 09:06:25 -03:00
samples Document OS-SIMPLE-CERT Routes 2016-11-01 08:26:00 -04:00
endpoint-policy.inc api-ref: Renaming parameters of V3-ext APIs 2016-08-11 13:36:30 +07:00
ep-filter.inc api-ref: Splitting status lines in API v3-ext. 2016-08-25 13:21:06 +07:00
federation.inc add a header for the federation APIs 2016-08-12 17:12:54 -04:00
index.rst Document OS-SIMPLE-CERT Routes 2016-11-01 08:26:00 -04:00
oauth.inc api-ref: Splitting status lines in API v3-ext. 2016-08-25 13:21:06 +07:00
parameters.yaml [api-ref] Correcting parameter's type 2016-09-06 04:17:38 +00:00
revoke.inc [api] add relationship links to v3-ext 2016-08-17 09:01:09 -05:00
simple-cert.inc Document OS-SIMPLE-CERT Routes 2016-11-01 08:26:00 -04:00
trust.inc Merge "api-ref: Splitting status lines in API v3-ext." 2016-08-29 15:40:56 +00:00