LinkedIn Javascript SDK authorize stopped working










6















I have a LinkedIn integration using their SDK and use the method authorize to request permission from the user to post in her/his behalf. It was working fine but today I noticed that it stopped working. The issue is that the callbackFunction (see https://developer.linkedin.com/docs/getting-started-js-sdk) never gets called, so I don't know when the user grants permission or not.



I was checking and noticed that the file: https://platform.linkedin.com/in.js now redirects to https://platform.linkedin.com/xdoor/scripts/in.js. I took a look at https://web.archive.org/web/*/https://platform.linkedin.com/in.js and it seems that it changed around November the 13th.



Have you had any problems with the SDK recently?










share|improve this question






















  • Having the same issue. Did you found any status on this issue?

    – chamoda
    Nov 15 '18 at 5:42











  • Unfortunately no, I haven't been able to find anything. I found a workaround for it though. The isAuthorized does return true after the user has granted access so I could use an interval to check when that becomes true and manually invoke the callback.

    – David Montaño
    Nov 15 '18 at 14:04







  • 1





    have you reported it to linkedin?

    – Thayne
    Nov 15 '18 at 16:58






  • 2





    @Thayne I have a support case opened and am waiting to hear back. But their support cases are supposed to be for linkedin.com issues, not API questions. Their developer SDK documentation recommends asking questions on Stack Overflow.

    – a.stringham
    Nov 15 '18 at 17:23






  • 1





    Have in mind that LinkedIn posted recently SDKs: Our JavaScript and Mobile Software Development Kits (SDKs) will stop working. Developers will need to migrate to using OAuth 2.0 directly from their apps. (engineering.linkedin.com/blog/2018/12/developer-program-updates). I think that is a kind of abrupt change, but it seems that soon (probably in 2019-03-01 or before) LinkedIn will only accept Oauth2 authentication.

    – Lucas Basquerotto
    Jan 16 at 11:42















6















I have a LinkedIn integration using their SDK and use the method authorize to request permission from the user to post in her/his behalf. It was working fine but today I noticed that it stopped working. The issue is that the callbackFunction (see https://developer.linkedin.com/docs/getting-started-js-sdk) never gets called, so I don't know when the user grants permission or not.



I was checking and noticed that the file: https://platform.linkedin.com/in.js now redirects to https://platform.linkedin.com/xdoor/scripts/in.js. I took a look at https://web.archive.org/web/*/https://platform.linkedin.com/in.js and it seems that it changed around November the 13th.



Have you had any problems with the SDK recently?










share|improve this question






















  • Having the same issue. Did you found any status on this issue?

    – chamoda
    Nov 15 '18 at 5:42











  • Unfortunately no, I haven't been able to find anything. I found a workaround for it though. The isAuthorized does return true after the user has granted access so I could use an interval to check when that becomes true and manually invoke the callback.

    – David Montaño
    Nov 15 '18 at 14:04







  • 1





    have you reported it to linkedin?

    – Thayne
    Nov 15 '18 at 16:58






  • 2





    @Thayne I have a support case opened and am waiting to hear back. But their support cases are supposed to be for linkedin.com issues, not API questions. Their developer SDK documentation recommends asking questions on Stack Overflow.

    – a.stringham
    Nov 15 '18 at 17:23






  • 1





    Have in mind that LinkedIn posted recently SDKs: Our JavaScript and Mobile Software Development Kits (SDKs) will stop working. Developers will need to migrate to using OAuth 2.0 directly from their apps. (engineering.linkedin.com/blog/2018/12/developer-program-updates). I think that is a kind of abrupt change, but it seems that soon (probably in 2019-03-01 or before) LinkedIn will only accept Oauth2 authentication.

    – Lucas Basquerotto
    Jan 16 at 11:42













6












6








6


6






I have a LinkedIn integration using their SDK and use the method authorize to request permission from the user to post in her/his behalf. It was working fine but today I noticed that it stopped working. The issue is that the callbackFunction (see https://developer.linkedin.com/docs/getting-started-js-sdk) never gets called, so I don't know when the user grants permission or not.



I was checking and noticed that the file: https://platform.linkedin.com/in.js now redirects to https://platform.linkedin.com/xdoor/scripts/in.js. I took a look at https://web.archive.org/web/*/https://platform.linkedin.com/in.js and it seems that it changed around November the 13th.



Have you had any problems with the SDK recently?










share|improve this question














I have a LinkedIn integration using their SDK and use the method authorize to request permission from the user to post in her/his behalf. It was working fine but today I noticed that it stopped working. The issue is that the callbackFunction (see https://developer.linkedin.com/docs/getting-started-js-sdk) never gets called, so I don't know when the user grants permission or not.



I was checking and noticed that the file: https://platform.linkedin.com/in.js now redirects to https://platform.linkedin.com/xdoor/scripts/in.js. I took a look at https://web.archive.org/web/*/https://platform.linkedin.com/in.js and it seems that it changed around November the 13th.



Have you had any problems with the SDK recently?







linkedin linkedin-jsapi






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 14 '18 at 22:12









David MontañoDavid Montaño

466




466












  • Having the same issue. Did you found any status on this issue?

    – chamoda
    Nov 15 '18 at 5:42











  • Unfortunately no, I haven't been able to find anything. I found a workaround for it though. The isAuthorized does return true after the user has granted access so I could use an interval to check when that becomes true and manually invoke the callback.

    – David Montaño
    Nov 15 '18 at 14:04







  • 1





    have you reported it to linkedin?

    – Thayne
    Nov 15 '18 at 16:58






  • 2





    @Thayne I have a support case opened and am waiting to hear back. But their support cases are supposed to be for linkedin.com issues, not API questions. Their developer SDK documentation recommends asking questions on Stack Overflow.

    – a.stringham
    Nov 15 '18 at 17:23






  • 1





    Have in mind that LinkedIn posted recently SDKs: Our JavaScript and Mobile Software Development Kits (SDKs) will stop working. Developers will need to migrate to using OAuth 2.0 directly from their apps. (engineering.linkedin.com/blog/2018/12/developer-program-updates). I think that is a kind of abrupt change, but it seems that soon (probably in 2019-03-01 or before) LinkedIn will only accept Oauth2 authentication.

    – Lucas Basquerotto
    Jan 16 at 11:42

















  • Having the same issue. Did you found any status on this issue?

    – chamoda
    Nov 15 '18 at 5:42











  • Unfortunately no, I haven't been able to find anything. I found a workaround for it though. The isAuthorized does return true after the user has granted access so I could use an interval to check when that becomes true and manually invoke the callback.

    – David Montaño
    Nov 15 '18 at 14:04







  • 1





    have you reported it to linkedin?

    – Thayne
    Nov 15 '18 at 16:58






  • 2





    @Thayne I have a support case opened and am waiting to hear back. But their support cases are supposed to be for linkedin.com issues, not API questions. Their developer SDK documentation recommends asking questions on Stack Overflow.

    – a.stringham
    Nov 15 '18 at 17:23






  • 1





    Have in mind that LinkedIn posted recently SDKs: Our JavaScript and Mobile Software Development Kits (SDKs) will stop working. Developers will need to migrate to using OAuth 2.0 directly from their apps. (engineering.linkedin.com/blog/2018/12/developer-program-updates). I think that is a kind of abrupt change, but it seems that soon (probably in 2019-03-01 or before) LinkedIn will only accept Oauth2 authentication.

    – Lucas Basquerotto
    Jan 16 at 11:42
















Having the same issue. Did you found any status on this issue?

– chamoda
Nov 15 '18 at 5:42





Having the same issue. Did you found any status on this issue?

– chamoda
Nov 15 '18 at 5:42













Unfortunately no, I haven't been able to find anything. I found a workaround for it though. The isAuthorized does return true after the user has granted access so I could use an interval to check when that becomes true and manually invoke the callback.

– David Montaño
Nov 15 '18 at 14:04






Unfortunately no, I haven't been able to find anything. I found a workaround for it though. The isAuthorized does return true after the user has granted access so I could use an interval to check when that becomes true and manually invoke the callback.

– David Montaño
Nov 15 '18 at 14:04





1




1





have you reported it to linkedin?

– Thayne
Nov 15 '18 at 16:58





have you reported it to linkedin?

– Thayne
Nov 15 '18 at 16:58




2




2





@Thayne I have a support case opened and am waiting to hear back. But their support cases are supposed to be for linkedin.com issues, not API questions. Their developer SDK documentation recommends asking questions on Stack Overflow.

– a.stringham
Nov 15 '18 at 17:23





@Thayne I have a support case opened and am waiting to hear back. But their support cases are supposed to be for linkedin.com issues, not API questions. Their developer SDK documentation recommends asking questions on Stack Overflow.

– a.stringham
Nov 15 '18 at 17:23




1




1





Have in mind that LinkedIn posted recently SDKs: Our JavaScript and Mobile Software Development Kits (SDKs) will stop working. Developers will need to migrate to using OAuth 2.0 directly from their apps. (engineering.linkedin.com/blog/2018/12/developer-program-updates). I think that is a kind of abrupt change, but it seems that soon (probably in 2019-03-01 or before) LinkedIn will only accept Oauth2 authentication.

– Lucas Basquerotto
Jan 16 at 11:42





Have in mind that LinkedIn posted recently SDKs: Our JavaScript and Mobile Software Development Kits (SDKs) will stop working. Developers will need to migrate to using OAuth 2.0 directly from their apps. (engineering.linkedin.com/blog/2018/12/developer-program-updates). I think that is a kind of abrupt change, but it seems that soon (probably in 2019-03-01 or before) LinkedIn will only accept Oauth2 authentication.

– Lucas Basquerotto
Jan 16 at 11:42












0






active

oldest

votes











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
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53309517%2flinkedin-javascript-sdk-authorize-stopped-working%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53309517%2flinkedin-javascript-sdk-authorize-stopped-working%23new-answer', 'question_page');

);

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







這個網誌中的熱門文章

What does pagestruct do in Eviews?

Dutch intervention in Lombok and Karangasem

Channel Islands