OAuth Broker API integration provides a safe way to retrieve stored authorizations.
When you are building a component that communicates with a 3rd party API and that API authorizes using OAuth, Keboola Connection (KBC) stores the users’ credentials/access tokens in the OAuth Broker API. They are revealed and decrypted only for a target component and project. End-users can be assured that their authorized access will not leak.
Note: This feature must be enabled by our support.
Create a configuration for the given component and project in the OAuth Broker API.
OAUTH_API_ID is the id provided when storing authorization via the OAuth Broker API.
"version": 3 to use the latest OAuth Broker API. The old OAuth V2 API is deprecated but still usable.
Docker Runner then retrieves, decrypts and injects the credentials to the
configuration file in the
authorization.oauth_api.credentials.#data configuration node stores the response from
the authorized API as a raw string. Parse the string accordingly, as OAuth Broker API has intentionally
no knowledge about the authorized APIs.
Important: None of the sandbox API calls
If you want to bypass the OAuth Broker API integration, you can paste all required credential parameters in the configuration directly. Fields requiring encryption will be encrypted and decrypted as usual. That means that you can save the following configuration via the configuration API.
This comes in very handy for quick component iterations and for testing whether your component works before having the OAuth support enabled.