Disable current recovery service #750
Closed
Conversation
This file contains 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
This was referenced Aug 28, 2023
Rashmini
force-pushed
the
recovery-api-v1-disable
branch
from
c7c68a7 to
ae50301
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes in this pull request
Due to the encountered issues with the current V1 API, a new V2 API is provided. Hence, current recovery service will be disabled. There will be a config to enable/disable the service.
When the V1 API is invoked while it's disabled, the response will be as follows.
Status code: 404 Not Found
Response body:
Related issue: wso2/product-is#16536
When should this PR be merged
This should be merged after wso2/carbon-identity-framework#4878