2569205 - OAuth Token Server details

Are OAuth Token Server details stored in any database table which can be referenced?

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

SAP SuccessFactors Learning

SAP SuccessFactors HXM Suite

Client Secrets are not stored in the database.

As the description within the OAuth Token Server tab indicate, these details are not recorded anywhere. The secret key is not stored, so if you lose it, you need to generate another. The reason you will need to generate a new one is that we do not have a way to unencrypt the key once it is stored in the database.

When you navigate away from the OAuth Token Server page, the secret disappears from the page.

For Admin-based client secrets (used to request an Admin token):
The hashed value will be stored in PA_USER_PRFL in these 2 columns (in case you would need to track when it changed and by whom):

• OAUTH_USER_CLIENT_SECRET_HASH = This column stores Hash for OATH key
• PASS_RST_TOKEN_HASH = This column stores the hash of the password reset token

For Application-based client secrets (used to request Admin and User tokens):
The hashed value will be stored in PA_APP_ADMIN table in the DATA_FLD_1 column

• OAUTH_TOKEN_SERVER_CLIENT_SECRET_HASH = the APP_ADMIN_ID

SAP, SF, SuccessFactors, HCM, LMS, Learning, OAuth Token Server, database table, stored, recorded, client, secret, admin, odata , KBA , LOD-SF-LMS-ODA , Web Services OData , LOD-SF-LMS , Learning Management System , How To