unauthorized_scope_error in LinkedIn oAuth2 authentication
I am following the official Microsoft instructions in Sign in with Linkedin (there are also the Linkedin instructions here), which also link here for the authorization code flow. As instructed, I have set up a linkedin application and used the client id and secret to initiate an oAuth 2 flow, requesting the r_liteprofile and r_emailaddress scopes.
Instead of getting the login form, I am redirected to my callback url with the following params:
error: unauthorized_scope_error
error_description: Scope "r_liteprofile" is not authorized for your application
state: cfa970987c9a3c2178dddeda0d81dab3e00dce4c683098d6
This is the list of default scopes (which, as per the documentation, are the ones granted if you don't specify a list of scopes yourself), and the r_liteprofile is not in there.
Is the documentation out of date, or am I overlooking something?
oauth-2.0 linkedin
asked Nov 26 '18 at 10:27
Markos FragkakisMarkos Fragkakis
3,735155495
add a comment |
I am following the official Microsoft instructions in Sign in with Linkedin (there are also the Linkedin instructions here), which also link here for the authorization code flow. As instructed, I have set up a linkedin application and used the client id and secret to initiate an oAuth 2 flow, requesting the r_liteprofile and r_emailaddress scopes.
Instead of getting the login form, I am redirected to my callback url with the following params:
error: unauthorized_scope_error
error_description: Scope "r_liteprofile" is not authorized for your application
state: cfa970987c9a3c2178dddeda0d81dab3e00dce4c683098d6
This is the list of default scopes (which, as per the documentation, are the ones granted if you don't specify a list of scopes yourself), and the r_liteprofile is not in there.
Is the documentation out of date, or am I overlooking something?
oauth-2.0 linkedin
asked Nov 26 '18 at 10:27
Markos FragkakisMarkos Fragkakis
3,735155495
add a comment |
I am following the official Microsoft instructions in Sign in with Linkedin (there are also the Linkedin instructions here), which also link here for the authorization code flow. As instructed, I have set up a linkedin application and used the client id and secret to initiate an oAuth 2 flow, requesting the r_liteprofile and r_emailaddress scopes.
Instead of getting the login form, I am redirected to my callback url with the following params:
error: unauthorized_scope_error
error_description: Scope "r_liteprofile" is not authorized for your application
state: cfa970987c9a3c2178dddeda0d81dab3e00dce4c683098d6
This is the list of default scopes (which, as per the documentation, are the ones granted if you don't specify a list of scopes yourself), and the r_liteprofile is not in there.
Is the documentation out of date, or am I overlooking something?
oauth-2.0 linkedin
asked Nov 26 '18 at 10:27
Markos FragkakisMarkos Fragkakis
3,735155495
I am following the official Microsoft instructions in Sign in with Linkedin (there are also the Linkedin instructions here), which also link here for the authorization code flow. As instructed, I have set up a linkedin application and used the client id and secret to initiate an oAuth 2 flow, requesting the r_liteprofile and r_emailaddress scopes.
Instead of getting the login form, I am redirected to my callback url with the following params:
error: unauthorized_scope_error
error_description: Scope "r_liteprofile" is not authorized for your application
state: cfa970987c9a3c2178dddeda0d81dab3e00dce4c683098d6
This is the list of default scopes (which, as per the documentation, are the ones granted if you don't specify a list of scopes yourself), and the r_liteprofile is not in there.
Is the documentation out of date, or am I overlooking something?
oauth-2.0 linkedin
oauth-2.0 linkedin
asked Nov 26 '18 at 10:27
Markos FragkakisMarkos Fragkakis
3,735155495
asked Nov 26 '18 at 10:27
Markos FragkakisMarkos Fragkakis
3,735155495
edited Nov 27 '18 at 10:05
Markos Fragkakis
asked Nov 26 '18 at 10:27
Markos FragkakisMarkos Fragkakis
3,735155495
asked Nov 26 '18 at 10:27
Markos FragkakisMarkos Fragkakis
3,735155495
asked Nov 26 '18 at 10:27
Markos FragkakisMarkos Fragkakis
3,735155495
3,735155495
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
This happened to me the other day but somehow I was able to get around the issue. The new Microsoft API docs for LinkedIn are up to date. The docs on LinkedIn Developers portal will soon be outdated:
Important update: All developers need to migrate to Version 2.0 of our APIs and OAuth 2.0 by March 1, 2019.
A few things to try:
- Register a new LinkedIn OAuth 2.0 developer application - newly registered applications have access to the new V2 API
- Try removing the
r_liteprofilescope or revert back tor_basicprofile
answered Dec 18 '18 at 12:26
albogdanoalbogdano
1,06711731
add a comment |
The reason was that although the documentation was live, the actual implementation was not.
The documented scopes now work as described in the
answered Dec 19 '18 at 16:07
Markos FragkakisMarkos Fragkakis
3,735155495
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53479131%2funauthorized-scope-error-in-linkedin-oauth2-authentication%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
This happened to me the other day but somehow I was able to get around the issue. The new Microsoft API docs for LinkedIn are up to date. The docs on LinkedIn Developers portal will soon be outdated:
Important update: All developers need to migrate to Version 2.0 of our APIs and OAuth 2.0 by March 1, 2019.
A few things to try:
- Register a new LinkedIn OAuth 2.0 developer application - newly registered applications have access to the new V2 API
- Try removing the
r_liteprofilescope or revert back tor_basicprofile
answered Dec 18 '18 at 12:26
albogdanoalbogdano
1,06711731
add a comment |
This happened to me the other day but somehow I was able to get around the issue. The new Microsoft API docs for LinkedIn are up to date. The docs on LinkedIn Developers portal will soon be outdated:
Important update: All developers need to migrate to Version 2.0 of our APIs and OAuth 2.0 by March 1, 2019.
A few things to try:
- Register a new LinkedIn OAuth 2.0 developer application - newly registered applications have access to the new V2 API
- Try removing the
r_liteprofilescope or revert back tor_basicprofile
answered Dec 18 '18 at 12:26
albogdanoalbogdano
1,06711731
add a comment |
This happened to me the other day but somehow I was able to get around the issue. The new Microsoft API docs for LinkedIn are up to date. The docs on LinkedIn Developers portal will soon be outdated:
Important update: All developers need to migrate to Version 2.0 of our APIs and OAuth 2.0 by March 1, 2019.
A few things to try:
- Register a new LinkedIn OAuth 2.0 developer application - newly registered applications have access to the new V2 API
- Try removing the
r_liteprofilescope or revert back tor_basicprofile
answered Dec 18 '18 at 12:26
albogdanoalbogdano
1,06711731
This happened to me the other day but somehow I was able to get around the issue. The new Microsoft API docs for LinkedIn are up to date. The docs on LinkedIn Developers portal will soon be outdated:
Important update: All developers need to migrate to Version 2.0 of our APIs and OAuth 2.0 by March 1, 2019.
A few things to try:
- Register a new LinkedIn OAuth 2.0 developer application - newly registered applications have access to the new V2 API
- Try removing the
r_liteprofilescope or revert back tor_basicprofile
answered Dec 18 '18 at 12:26
albogdanoalbogdano
1,06711731
answered Dec 18 '18 at 12:26
albogdanoalbogdano
1,06711731
answered Dec 18 '18 at 12:26
albogdanoalbogdano
1,06711731
answered Dec 18 '18 at 12:26
albogdanoalbogdano
1,06711731
1,06711731
add a comment |
add a comment |
The reason was that although the documentation was live, the actual implementation was not.
The documented scopes now work as described in the
answered Dec 19 '18 at 16:07
Markos FragkakisMarkos Fragkakis
3,735155495
add a comment |
The reason was that although the documentation was live, the actual implementation was not.
The documented scopes now work as described in the
answered Dec 19 '18 at 16:07
Markos FragkakisMarkos Fragkakis
3,735155495
add a comment |
The reason was that although the documentation was live, the actual implementation was not.
The documented scopes now work as described in the
answered Dec 19 '18 at 16:07
Markos FragkakisMarkos Fragkakis
3,735155495
The reason was that although the documentation was live, the actual implementation was not.
The documented scopes now work as described in the
answered Dec 19 '18 at 16:07
Markos FragkakisMarkos Fragkakis
3,735155495
answered Dec 19 '18 at 16:07
Markos FragkakisMarkos Fragkakis
3,735155495
answered Dec 19 '18 at 16:07
Markos FragkakisMarkos Fragkakis
3,735155495
answered Dec 19 '18 at 16:07
Markos FragkakisMarkos Fragkakis
3,735155495
3,735155495
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53479131%2funauthorized-scope-error-in-linkedin-oauth2-authentication%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
