Encrypting OAuth Keys
- Former user (Deleted)
- Former user (Deleted)
- Former user (Deleted)
WSO2 API Manager allows you to encrypt any sensitive OAuth2.0 keys that are created. The API Manager encrypts access tokens, client secrets and authorization codes (this can be extended to any other OAuth2.0 keys if needed) using the primary keystore. The result is encoded in Base64 and stored in the database. The RSA algorithm is used by default and the key strength (1024, 2048, etc) is based on the private key strength of the primary keystore. If SymmetricEncryption is enabled, the API Manager uses the AES algorithm by default, or the algorithm specified for the SymmetricEncryption.Algorithm in the carbon.xml file.
It is recommended to switch this configuration on/off before any keys have been generated in your system. Once token encryption is switched on, the system encrypts all sensitive OAuth2.0 data such as Access Tokens, Consumer Secrets, etc. When reading that information, the system assumes that they are in the encrypted format and attempts to decrypt them. Therefore, switching this configuration on after any keys are created would break the system, unless the data is converted back into plain text.
In order to encrypt the OAuth keys, change the following configurations.
- In the
<APIM_HOME>/repository/conf/api-manager.xmlfile, set theÂ<EncryptPersistedTokens>property totrue. - In the
<APIM_HOME>/repository/conf/identity/identity.xmlfile, change the<TokenPersistenceProcessor>property toorg.wso2.carbon.identity.oauth.tokenprocessor.EncryptionDecryptionPersistenceProcessor. - Restart the server(s) after the above configuration changes are performed.
Tip
- If you use a distributed API Manager setup, the changes must be made on both the API Store and Key Manager nodes.
- If you use WSO2 Identity Server (WSO2 IS) as the Key Manager setup, you need to make changes in both WSO2 IS and WSO2 API Manager.