From 00c444892a22f38939c7a091004cf470c5868cd9 Mon Sep 17 00:00:00 2001 From: zlyqqq Date: Mon, 17 Jul 2017 10:52:05 +0800 Subject: [PATCH] Assert default project id is not domain If using default project id when creating user, make sure the project is not a domain. This patch add the note to the description of default_project_id in api ref. Change-Id: Iedda6df116f237cb68a882efff6f3e19c6ee8e72 --- api-ref/source/v3/parameters.yaml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/api-ref/source/v3/parameters.yaml b/api-ref/source/v3/parameters.yaml index 77aa617dec..a7d518dd22 100644 --- a/api-ref/source/v3/parameters.yaml +++ b/api-ref/source/v3/parameters.yaml @@ -534,14 +534,14 @@ credentials_links: default_project_id_request_body: description: | The ID of the default project for the user. - Setting this attribute does not grant any actual authorization on - the project, and is merely provided for convenience. Therefore, - the referenced project does not need to exist within the user - domain. (Since v3.1) If the user does not have authorization to - their default project, the default project is ignored at token - creation. (Since v3.1) Additionally, if your default project is - not valid, a token is issued without an explicit scope of - authorization. + A user's default project must not be a domain. Setting this + attribute does not grant any actual authorization on the project, + and is merely provided for convenience. Therefore, the referenced + project does not need to exist within the user domain. (Since v3.1) + If the user does not have authorization to their default project, + the default project is ignored at token creation. (Since v3.1) + Additionally, if your default project is not valid, a token is + issued without an explicit scope of authorization. in: body required: false type: string