7 Commits

Author	SHA1	Message	Date
Lisa Cawley	828ff01515	[DOCS] Update snippets in security APIs (#46191) (#46401)	2019-09-05 11:12:39 -07:00
Lisa Cawley	00235bbecd	[DOCS] Reformats the security APIs (#45124)	2019-08-02 11:32:47 -07:00
Lisa Cawley	efd7003ea9	[DOCS] Corrected API path for invalidate token and SSL certificate examples (#39530)	2019-03-12 13:28:37 -07:00
lcawl	32bed098bb	[DOCS] Synchs titles of X-Pack APIs	2018-12-20 10:27:24 -08:00
Ioannis Kakavas	7b9ca62174	Enhance Invalidate Token API (#35388) ... This change: - Adds functionality to invalidate all (refresh+access) tokens for all users of a realm - Adds functionality to invalidate all (refresh+access)tokens for a user in all realms - Adds functionality to invalidate all (refresh+access) tokens for a user in a specific realm - Changes the response format for the invalidate token API to contain information about the number of the invalidated tokens and possible errors that were encountered. - Updates the API Documentation After back-porting to 6.x, the `created` field will be removed from master as a field in the response Resolves: #35115 Relates: #34556	2018-12-18 10:05:50 +02:00
Ioannis Kakavas	d7c5d8049a	Deprecate /_xpack/security/* in favor of /_security/* (#36293) ... * This commit is part of our plan to deprecate and ultimately remove the use of _xpack in the REST APIs. - REST API docs - HLRC docs and doc tests - Handle REST actions with deprecation warnings - Changed endpoints in rest-api-spec and relevant file names	2018-12-11 11:13:10 +02:00
Ioannis Kakavas	e8ec4fad7b	[DOCS] Adjust Invalidate Token REST API docs (#35622) ... - Renames API to Invalidate Token - Explicitly calls out the possibility to invalidate refresh tokens via this API	2018-11-21 09:32:56 +02:00