Connector Builder Guide – Authentication Type: Oauth 2.0
Open Connectors consists of over 170 connectors to 3rd Party Applications natively embedded in the SAP ecosystem. If the Connector you need does not exist in the catalog, you can build it quickly with Connector Builder. This instruction guide will walk you through using this tool, with concrete examples throughout. The beginning, Part 1, can be found here.
Selecting Oauth 2.0 will expose these fields in the Setup Screen. You will need (using the MailChimp API as an example):
- Oauth Authorization URL: https://login.mailchimp.com/oauth2/authorize
- Oauth API Key: In the page above for MailChimp, under Register Your Application, you will create an application that will provide a client_id and client_secret. This is standard practice when setting up an Oauth 2.0 flow. The client_id will be the Oauth API Key here.
- Oauth API Secret: This is the client_secret from the app above.
- Oauth Callback URL: Almost always, the app that you register will require a callback URL, or sometimes called a redirect URI. You would enter the callback that redirects back to Open Connectors, or https://auth.cloudelements.io/oauth
- Oauth Token URL: https://login.mailchimp.com/oauth2/token
- Oauth Scope: Some APIs require one – in this case MailChimp does not – so we have to remove the default “read” entry
- Oauth Refresh URL: Some APIs require one – in this case MailChimp does not. It will usually look like the authorize URL but instead end in /refresh, /token or something similar.
- Oauth Refresh Interval: Some APIs require one – in this case MailChimp does not. This is represented in seconds and is usually 3600 seconds.
- Oauth Token Revoke URL: Some APIs require one – in this case MailChimp does not.
After populating all the necessary fields for the specific API that you are working with, the Connector will redirect the user to the login page and will generate the access token (supplying the necessary grant-type behind the scenes) from the returned code. It will append an Authorization header in the format of `Bearer access_token` on all resource calls by default. The finished Connector will refresh the access token if the refresh token and interval is supplied.