Change Default Certificate Hashing Algorithm to SHA-256 #12365
Merged
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.
Purpose
This PR changes the default certificate hashing algorithm to SHA-256 instead of SHA-1.
The following flows are affected due to this change.
The certificate hashing algorithm used in generating API keys will now use SHA-256 as the hashing algorithm
The certificate hashing algorithm used in generating backend JWTs for JWT and Opaque token SPs will now use SHA-256 as the default hashing algorithm. A config is provided to use SHA-1 as follows.
api-manager.xml.j2
To use SHA-1 instead of SHA-256, the following has to be added to the deployment.toml.
deployment.toml
[1] wso2/product-apim#13455