There are multiple reasons that can result in oAuth verification failing. Let's enumerate some of the common causes:
- The actual value is defined in the client-secret-key in the authorization.bxb file instead of the name of the key. The screenshot below shows the Dev Center configuration that should accompany the following code:
authorization {
user {
oauth2-authorization-code (providerId) {
authorize-endpoint (...)
client-id (...)
client-secret-key (KeyName)
scope (...) // optional
token-endpoint (...)
}
}
global {
oauth2-client-credentials (providerId) {
client-id (...)
client-secret-key (KeyName)
scope (...) // optional
token-endpoint (...)
revoke-endpoint(...) // optional
login-button-label(...) // optional
}
}
} - The secret being used does not correspond to the method the capsule is being tested. Please keep in mind that testing via Bixby Developer Studio's Simulator uses the secret(s) defined in the Dev section of Config & Secrets while on-device testing with public AND private revisions uses the the secret(s) defined in the Prod section of Config & Secrets.
- The defined secret may have expired. Confirm with the content provider that the secret being used is still valid.
- The content provider's API may have changed. This happens rarely but abruptly cuts off previously functional flows until changes are made to how requests are built by the capsule.
Comments
0 comments
Please sign in to leave a comment.