Bixby Developer Center

Guides

authorization

optional

Top level authorization key that defines the OAuth 2.0 access scope a user can give a provider. This key must be in an authorization.bxb file, which must be in the root level directory of your capsule (the same level as the required capsule.bxb file).

authorization {
user {
oauth2-authorization-code (providerId) {
authorize-endpoint (...)
client-id (...)
client-secret-key (...)
scope (...) // optional
token-endpoint (...)
}
}
global {
oauth2-client-credentials (providerId) {
client-id (...)
client-secret-key (...)
scope (...) // optional
token-endpoint (...)
revoke-endpoint(...) // optional
login-button-label(...) // optional
}
}
}

The client-secret-key is a name entered in the Config & Secrets screen of the Bixby Developer Center for the capsule:

Config & Secrets View

To get the secret with the name sec1, your authorization block would contain client-secret-key (sec1).

Child Keys

global
optional
Defines the global OAuth 2.0 authorization access
user
optional
Defines the OAuth 2.0 authorization access for a user