OAuth 2.0 - Secure Store Example and which encryption is suggested? — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

OAuth 2.0 - Secure Store Example and which encryption is suggested?

edited Jul 30, 2025 6:32PM in EPM Platform and Freeform 2 comments

Summary:

What is indicated by Secure Store here and which is the suggested/preferrable encryption? This is for OAuth 2.0 Device code grant type, and this is as per admin guide

to ensure security of Cloud EPM, it is important to securely encrypt and store the client_id and any tokens. The REST client must securely store the refresh token and client_id

curl --location --request POST 'https://tenant-base-url/oauth2/v1/token' --header 'Content-Type: application/x-www-form-urlencoded' --data-urlencode 'grant_type=refresh_token' --data-urlencode 'client_id=<DECRYPTED CLIENT ID OF OAUTH2 APPLICATION FROM SECURE STORE>' --data-urlencode 'refresh_token=<DECRYPTED REFRESH TOKEN FROM SECURE STORE>'

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!