8144e28336
It was possible to create a credential without providing a project_id and later updating it to the ec2 type. This patch fixes the issue by adding a manual checking in the manager layer since it needs to check the old credential contents prior failing the request. Change-Id: I1eb28a46c89e17d9c990cc798867d1a59714fe5f Closes-Bug: #1613466
9 lines
436 B
YAML
9 lines
436 B
YAML
fixes:
|
|
- >
|
|
[`bug 1613466 <https://bugs.launchpad.net/keystone/+bug/1613466>`_]
|
|
Credentials update to ec2 type originally accepted credentials with no
|
|
project ID set, this would lead to an error when trying to use such credential.
|
|
This behavior has been blocked, so creating a non-ec2 credential with no
|
|
project ID and updating it to ec2 without providing a project ID will fail with
|
|
a `400 Bad Request` error.
|