dd1e705853
In a previous commit we made all calls to issue_v2_token use issue_v3_token instead. Any tokens that needed to be represented as a v2.0 token we translate using the V2TokenDataHelper class. At this point nothing really uses the issue_v2_token method and it can be safely removed. A subsequent patch will rename the issue_v3_token method to just issue_token since we no longer need to make a distinction between two different methods. Depends-On: Ia51f28a70ae099f1ec93851d271db8556aced836 Change-Id: I7d3b583cbec9a095ab8cc20c5d6c0a6127e37068
15 lines
612 B
YAML
15 lines
612 B
YAML
---
|
|
upgrade:
|
|
- The ``issue_v2_token()`` method has been removed
|
|
from the token provider interface. The token provider
|
|
API now uses a single create token method and translates
|
|
v3 token responses to v2 format when needed. Having
|
|
``issue_v2_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_v2_token()``
|
|
method.
|