Solves the issue #1198: "Identity service not working with OS4j". #1199
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
Contributor
|
@jyothisaroja can you please resolve the conflicts? |
Contributor
Author
|
@vinodborole I have resolved the conflicts now. |
Contributor
Author
|
@vinodborole Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The code below fixes the github issue #1198: "Identity service not working with OS4j".
Keystone version v3 is missed in the keystone endpoint URL due to which the Identity service APIs fail with the error message "Resource could not be found (404)". The code appends version "/v3" to the keystone endpoint URL which fixes the issue.
Added a new class "BaseIdentityServices" to enforce keystone version to endpoint URL.