You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Currently, BouncyCastle ("BC") crypto provider is hardcoded in org.wso2.carbon.core.util.CryptoUtil (E.g. Refer [1]), which is used for conducting internal encryption tasks such as OAuth2 token encryption. We should check the feasibility of making this configurable in order to allow use of FIPS 140-2 compliant crypto providers (E.g. "BCFIPS").
Description:
Currently, BouncyCastle ("BC") crypto provider is hardcoded in org.wso2.carbon.core.util.CryptoUtil (E.g. Refer [1]), which is used for conducting internal encryption tasks such as OAuth2 token encryption. We should check the feasibility of making this configurable in order to allow use of FIPS 140-2 compliant crypto providers (E.g. "BCFIPS").
[1]
carbon-kernel/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/util/CryptoUtil.java
Line 153 in 9e8dab2
The text was updated successfully, but these errors were encountered: