getting an error code back from sonos auth pages
when I open a browser window to https://api.sonos.com/login/v3/oauth?client_id=myid&response_type=code&state=mystateinb64&scope=playback-control-all&redirect_uri=my redirect url
i get to the SONOS "starting" screen, then I press "continue"
I enter my sonos credentials , click connection
then I get to the consent screen showing my APP name, so I click "OK"
then I get a http 400 with body
error: "invalid_request"
and my authorization callback is never called
I checked the parameters, esp the client ID in the url , it is correct
any idea why would this be happenning ?
sonos
asked Nov 16 '18 at 7:31
amg0amg0
212
add a comment |
when I open a browser window to https://api.sonos.com/login/v3/oauth?client_id=myid&response_type=code&state=mystateinb64&scope=playback-control-all&redirect_uri=my redirect url
i get to the SONOS "starting" screen, then I press "continue"
I enter my sonos credentials , click connection
then I get to the consent screen showing my APP name, so I click "OK"
then I get a http 400 with body
error: "invalid_request"
and my authorization callback is never called
I checked the parameters, esp the client ID in the url , it is correct
any idea why would this be happenning ?
sonos
asked Nov 16 '18 at 7:31
amg0amg0
212
add a comment |
when I open a browser window to https://api.sonos.com/login/v3/oauth?client_id=myid&response_type=code&state=mystateinb64&scope=playback-control-all&redirect_uri=my redirect url
i get to the SONOS "starting" screen, then I press "continue"
I enter my sonos credentials , click connection
then I get to the consent screen showing my APP name, so I click "OK"
then I get a http 400 with body
error: "invalid_request"
and my authorization callback is never called
I checked the parameters, esp the client ID in the url , it is correct
any idea why would this be happenning ?
sonos
asked Nov 16 '18 at 7:31
amg0amg0
212
when I open a browser window to https://api.sonos.com/login/v3/oauth?client_id=myid&response_type=code&state=mystateinb64&scope=playback-control-all&redirect_uri=my redirect url
i get to the SONOS "starting" screen, then I press "continue"
I enter my sonos credentials , click connection
then I get to the consent screen showing my APP name, so I click "OK"
then I get a http 400 with body
error: "invalid_request"
and my authorization callback is never called
I checked the parameters, esp the client ID in the url , it is correct
any idea why would this be happenning ?
sonos
sonos
asked Nov 16 '18 at 7:31
amg0amg0
212
asked Nov 16 '18 at 7:31
amg0amg0
212
asked Nov 16 '18 at 7:31
amg0amg0
212
asked Nov 16 '18 at 7:31
amg0amg0
212
asked Nov 16 '18 at 7:31
amg0amg0
212
212
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Please confirm that the redirect uri you specified when you created your client I’d and secret is exactly the same as the one you pass when you request the auth code and when you request the access token.
answered Nov 16 '18 at 12:46
Matt WelchMatt Welch
6231512
I did have to change it compared to the one I used when I created the Client Credential, but as we speak I have it exactly correct in the sonos CLient Credential portal. I though about that and did create a brand new TEST client credential, this time properly filled in at creation time and it has exactly the same error behavior
– amg0
Nov 16 '18 at 18:11
add a comment |
it now worked, I had to delete the sonos credential completely ( not just the key ) and create a new one from scratch. very strange !
answered Nov 16 '18 at 21:21
amg0amg0
212
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%2f53333291%2fgetting-an-error-code-back-from-sonos-auth-pages%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
Please confirm that the redirect uri you specified when you created your client I’d and secret is exactly the same as the one you pass when you request the auth code and when you request the access token.
answered Nov 16 '18 at 12:46
Matt WelchMatt Welch
6231512
I did have to change it compared to the one I used when I created the Client Credential, but as we speak I have it exactly correct in the sonos CLient Credential portal. I though about that and did create a brand new TEST client credential, this time properly filled in at creation time and it has exactly the same error behavior
– amg0
Nov 16 '18 at 18:11
add a comment |
Please confirm that the redirect uri you specified when you created your client I’d and secret is exactly the same as the one you pass when you request the auth code and when you request the access token.
answered Nov 16 '18 at 12:46
Matt WelchMatt Welch
6231512
I did have to change it compared to the one I used when I created the Client Credential, but as we speak I have it exactly correct in the sonos CLient Credential portal. I though about that and did create a brand new TEST client credential, this time properly filled in at creation time and it has exactly the same error behavior
– amg0
Nov 16 '18 at 18:11
add a comment |
Please confirm that the redirect uri you specified when you created your client I’d and secret is exactly the same as the one you pass when you request the auth code and when you request the access token.
answered Nov 16 '18 at 12:46
Matt WelchMatt Welch
6231512
Please confirm that the redirect uri you specified when you created your client I’d and secret is exactly the same as the one you pass when you request the auth code and when you request the access token.
answered Nov 16 '18 at 12:46
Matt WelchMatt Welch
6231512
answered Nov 16 '18 at 12:46
Matt WelchMatt Welch
6231512
answered Nov 16 '18 at 12:46
Matt WelchMatt Welch
6231512
answered Nov 16 '18 at 12:46
Matt WelchMatt Welch
6231512
6231512
I did have to change it compared to the one I used when I created the Client Credential, but as we speak I have it exactly correct in the sonos CLient Credential portal. I though about that and did create a brand new TEST client credential, this time properly filled in at creation time and it has exactly the same error behavior
– amg0
Nov 16 '18 at 18:11
add a comment |
I did have to change it compared to the one I used when I created the Client Credential, but as we speak I have it exactly correct in the sonos CLient Credential portal. I though about that and did create a brand new TEST client credential, this time properly filled in at creation time and it has exactly the same error behavior
– amg0
Nov 16 '18 at 18:11
I did have to change it compared to the one I used when I created the Client Credential, but as we speak I have it exactly correct in the sonos CLient Credential portal. I though about that and did create a brand new TEST client credential, this time properly filled in at creation time and it has exactly the same error behavior
– amg0
Nov 16 '18 at 18:11
I did have to change it compared to the one I used when I created the Client Credential, but as we speak I have it exactly correct in the sonos CLient Credential portal. I though about that and did create a brand new TEST client credential, this time properly filled in at creation time and it has exactly the same error behavior
– amg0
Nov 16 '18 at 18:11
add a comment |
it now worked, I had to delete the sonos credential completely ( not just the key ) and create a new one from scratch. very strange !
answered Nov 16 '18 at 21:21
amg0amg0
212
add a comment |
it now worked, I had to delete the sonos credential completely ( not just the key ) and create a new one from scratch. very strange !
answered Nov 16 '18 at 21:21
amg0amg0
212
add a comment |
it now worked, I had to delete the sonos credential completely ( not just the key ) and create a new one from scratch. very strange !
answered Nov 16 '18 at 21:21
amg0amg0
212
it now worked, I had to delete the sonos credential completely ( not just the key ) and create a new one from scratch. very strange !
answered Nov 16 '18 at 21:21
amg0amg0
212
answered Nov 16 '18 at 21:21
amg0amg0
212
answered Nov 16 '18 at 21:21
amg0amg0
212
answered Nov 16 '18 at 21:21
amg0amg0
212
212
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%2f53333291%2fgetting-an-error-code-back-from-sonos-auth-pages%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
