Replies: 5 comments 5 replies
-
|
On GitHub, you can create two different types of apps: GitHub apps and OAuth apps. |
Beta Was this translation helpful? Give feedback.
-
|
After several attempts, I finally successfully redirected to GitHub to complete the authorization, but when calling the interface, an error occurred: {
code: 'verification_record.permission_denied',
message: 'Permission denied, please re-authenticate.'
}The same error also occurred on Discord bug-reports channel, but it has not been resolved. const bindResponse = await fetch(`${logtoConfig.endpoint}api/my-account/identities`, {
method: 'POST',
headers: {
Authorization: `Bearer ${accessToken}`,
'logto-verification-id': verificationRecordId,
'Content-Type': 'application/json',
},
body: JSON.stringify({
connectorId,
newIdentifierVerificationRecordId: verificationRecordId,
}),
}); |
Beta Was this translation helpful? Give feedback.
-
|
It seems that you encountered an authentication failure when requesting the |
Beta Was this translation helpful? Give feedback.
-
Is it still that I'm using the wrong method? |
Beta Was this translation helpful? Give feedback.
-
|
I create issue: #8172 |
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
-
Refer to this document:
https://docs.logto.io/zh-CN/end-user-flows/account-settings/by-account-api#link-a-new-social-connection
I performed the following steps:
Another scenario:
I received the following response:
{verificationRecordId: 'n800rh4r3tz4bnomlllp0', authorizationUri: 'https://github.com/login/oauth/authorize?client_id=*******&scope=read%3Auser+user%3Aemail', expiresAt: '2026-01-05T19:40:28.257Z'}Then it normally redirects to authorizationUri, and at this point, Github shows a warning:
At this point, the complete request link:
https://github.com/login/oauth/authorize?client_id=*********&redirect_uri=http%3A%2F%2Flocalhost%3A3000%2Fapi%2Flogto%2Fverifications%2Fsocial%2Fcallback&state=x7a8M8lhXk9KAgPk_mBA9nblG1QsRStB&scope=read%3Auser+user%3Aemail
A problem arises here because Github only allows setting one Authorization callback URL, and this URL has already been preset in Logto.
Therefore, when my application is from a different domain, it is blocked by Github's authentication process.
Has anyone actually successfully completed this social account binding? I looked through the issues and didn't find any similar discussions.
By the way, I can't imagine at all how much room for imagination all these "...." in the documentation can bring me.

Beta Was this translation helpful? Give feedback.
All reactions