Symptom
When planning to enable OAuth 2.0 token caching for multiple REST receiver channels in SAP PO, the channel will generate the token during first call and will store the token in the database for reuse in subsequent requests but it is unclear whether all channels will share a common cached token or whether each channel will maintain its own cached token. Seeking clarification on the criteria used by SAP PI/PO to determine OAuth token sharing across multiple channels.
Read more...
Environment
- Process Integration/Process Orchestration 7.5 SP 12 or higher
Product
Keywords
SAP PI, PO. Process Integration, Process Orchestration, REST receiver, Receiver channel, Rest Polling, OAuth, OAuth 2.0, token, Cache, caching, XI_AF_OAUTH_CACHE, multiple channels, token sharing, reuse, Access Token Reuse, Client ID, OAuth Scope, Authorization Server URL, OAuth Authentication, Token Cache Entry , KBA , BC-XI-CON-RST , Rest Adapter , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview