c0c23fd9df
Since we don't have a reason to hold on to a version specific token method name, we can rename it to be just issue_token. Now the token provider interface has two intergral methods, validate_token and issue_token. From a third-party perspective, this makes it easier to maintain a proprietary token provider since it eliminates a lot of version specific things from the provider implementation. From a keystone perspective, we are isolating the numerous token validation and issuance paths to a since route. This will make understanding the code easier for other developers and eventually easier to optimize. Change-Id: I71a04b42e931338b8bd59e479636b6199c7c2d76
16 lines
633 B
YAML
16 lines
633 B
YAML
---
|
|
upgrade:
|
|
- The ``issue_v3_token()`` method has been removed
|
|
from the token provider interface. The token provider
|
|
API now uses a single create token method, ``issue_token``
|
|
and translates v3 token responses to v2 format when
|
|
needed. Having ``issue_v3_token()`` defined with the
|
|
Ocata codebase will fail since the interface no longer
|
|
includes that method. Please take this into consideration
|
|
and plan accordingly if you're maintaining a custom token
|
|
provider.
|
|
critical:
|
|
- If writing a custom token provider, see the upgrade
|
|
section about the removal of the ``issue_v3_token()``
|
|
method.
|