ABAP Social Media Integration (ABAP SMI) does not store any application data, but only transfers data to and from the external service provider.
An application table exists for storing OAuth tokens; however, the tokens are not relevant for secure storage, as they are not usable without a corresponding secret. ABAP SMI does not use secrets, instead it uses the SAML 2.0 assertions.
For performance reasons, ABAP SMI buffers sessions (SAP Jam session IDs) for each user in the secure storage. The sessions are valid for a limited time, but are automatically renewed when they expire.
If there is an error, you can use report RCLB2_SESSION_DELETE to delete created sessions.
You can use transaction SECSTORE to access and maintain SAP Jam sessions. To find the SAP Jam sessions, on the Administration Program for Secure Storage screen, do the following:
For more information about the SECSTORE transaction, go to SAP Library for User Interface Add-On for SAP NetWeaver at http://help.sap.com/nw-uiaddon, and search for Secure Storage (ABAP).
ABAP Social Media Integration (ABAP SMI) enables the integration of SAP on-premise systems with external service providers located outside of the firewall. This channel allows sharing of information on business objects and documents that may contain sensitive information with external users that do not have access to the back-end system of the company or organization.
SAP does not assume any warranty or liability for information that is shared and cannot issue a guarantee that neither data privacy regulations nor legal requirements have been violated. The company or organization should consider the additional information channel in their guidelines on security and data privacy.