Preparing OAuth SHA1

Normally, the application-based OAuth requires a consumer key and secret to be stored in the back-end system for each external application ID. The external application ID is the technical representation of the SAP Jam’s OAuth client in the back end.

The ABAP Social Media Integration, however, uses a variant that replaces the secret with a SAML assertion, similar to the SAML 2.0 authentication scenario. For this approach, only one entry is necessary in Secure Store and Forward (SSF), and no secrets need to be stored here. The consumer key for each application still needs to be maintained, as described in Defining Application Settings.

A client based on OAuth (2-legged or 3-legged) is required by some administrative APIs that are run in an application. By default, RSA-SHA1 is used for encryption.

As part of the standard delivery, the SSF application exists in the system with the name CLBOAU (= CoLlaBoration OAUth) and the parameters mentioned in Creating an SSFA Instance.

• If it is missing for any reason, follow the procedure in Creating an SSFA Instance, before you complete section Issuing Certificates for SSF CLBOAU.
• If you see the SSF Collaboration Integration in the Dialog Structure on the Trust Manager screen, skip section Creating an SSFA Instance, and continue with section Issuing Certificates for SSF CLBOAU.