Docusign - sandbox - Redirect URI - not working
I am trying out Docusign sandbox environment in which I have created an integrator key with appropriate redirect uri
When I request the api:
https://admindemo.docusign.com/oauth/auth?response_type=id_token&scope=open_id&client_id=<integrator-key>&state=custom&redirect_uri=https://webhook.site/1b7aba4c-f96f-41e1-922d-2d8d38392208&admin_consent_scope=impersonation
Docusign does not redirect to the redirect-url, but opens the Docusign admin page.
If I request the URL:
https://account-d.docusign.com/oauth/auth?response_type=id_token&scope=open_id&client_id=<integrator-key>&state=custom&redirect_uri=https://webhook.site/1b7aba4c-f96f-41e1-922d-2d8d38392208&admin_consent_scope=impersonation
Then I get the error:
You are not an organization admin. Please contact your DocuSign Administrator
docusignapi docusign
asked Nov 14 '18 at 5:01
NgmNgm
5,041114779
add a comment |
I am trying out Docusign sandbox environment in which I have created an integrator key with appropriate redirect uri
When I request the api:
https://admindemo.docusign.com/oauth/auth?response_type=id_token&scope=open_id&client_id=<integrator-key>&state=custom&redirect_uri=https://webhook.site/1b7aba4c-f96f-41e1-922d-2d8d38392208&admin_consent_scope=impersonation
Docusign does not redirect to the redirect-url, but opens the Docusign admin page.
If I request the URL:
https://account-d.docusign.com/oauth/auth?response_type=id_token&scope=open_id&client_id=<integrator-key>&state=custom&redirect_uri=https://webhook.site/1b7aba4c-f96f-41e1-922d-2d8d38392208&admin_consent_scope=impersonation
Then I get the error:
You are not an organization admin. Please contact your DocuSign Administrator
docusignapi docusign
asked Nov 14 '18 at 5:01
NgmNgm
5,041114779
add a comment |
I am trying out Docusign sandbox environment in which I have created an integrator key with appropriate redirect uri
When I request the api:
https://admindemo.docusign.com/oauth/auth?response_type=id_token&scope=open_id&client_id=<integrator-key>&state=custom&redirect_uri=https://webhook.site/1b7aba4c-f96f-41e1-922d-2d8d38392208&admin_consent_scope=impersonation
Docusign does not redirect to the redirect-url, but opens the Docusign admin page.
If I request the URL:
https://account-d.docusign.com/oauth/auth?response_type=id_token&scope=open_id&client_id=<integrator-key>&state=custom&redirect_uri=https://webhook.site/1b7aba4c-f96f-41e1-922d-2d8d38392208&admin_consent_scope=impersonation
Then I get the error:
You are not an organization admin. Please contact your DocuSign Administrator
docusignapi docusign
asked Nov 14 '18 at 5:01
NgmNgm
5,041114779
I am trying out Docusign sandbox environment in which I have created an integrator key with appropriate redirect uri
When I request the api:
https://admindemo.docusign.com/oauth/auth?response_type=id_token&scope=open_id&client_id=<integrator-key>&state=custom&redirect_uri=https://webhook.site/1b7aba4c-f96f-41e1-922d-2d8d38392208&admin_consent_scope=impersonation
Docusign does not redirect to the redirect-url, but opens the Docusign admin page.
If I request the URL:
https://account-d.docusign.com/oauth/auth?response_type=id_token&scope=open_id&client_id=<integrator-key>&state=custom&redirect_uri=https://webhook.site/1b7aba4c-f96f-41e1-922d-2d8d38392208&admin_consent_scope=impersonation
Then I get the error:
You are not an organization admin. Please contact your DocuSign Administrator
docusignapi docusign
docusignapi docusign
asked Nov 14 '18 at 5:01
NgmNgm
5,041114779
asked Nov 14 '18 at 5:01
NgmNgm
5,041114779
asked Nov 14 '18 at 5:01
NgmNgm
5,041114779
asked Nov 14 '18 at 5:01
NgmNgm
5,041114779
asked Nov 14 '18 at 5:01
NgmNgm
5,041114779
5,041114779
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
response_type=id_token is invalid. The response type should be code. Unfortunately, the 'Obtaining Consent' documentation still references this incorrect value.
scope=open_id can only be used if your account is associated with an Organization, and if you are an Organization Administrator. If your account is not under an Organization, you'll need to use the individual consent workflow, which means scope should be signature impersonation and the admin_consent_scope parameter should be removed.
If you would like to create an Organization in the sandbox environment, you will need to open a case with DocuSign Support requesting that functionality be added to your Demo account. To have that enabled in Production, you'll need to contact your Account Manager or the Sales team.
answered Nov 14 '18 at 18:24
DrewDrew
1,027126
Hi it would be very helpful if you could add these details to the documentation, otherwise it takes a lot of time for someone to figure this out
– Ngm
Nov 14 '18 at 23:10
add a comment |
Your question is not so clear -- please update your question if this answer is in the wrong direction.
I think you are trying to implement the oauth authorization code grant flow and are having a problem.
The starting url for DocuSign for the oauth auth code grant flow:
- For the developer sandbox environment: https://account-d.docusign.com/oauth/auth
- For the production platforms: https://account.docusign.com/oauth/auth
Also, why are you including the admin_consent_scope query parameter?
Hopefully this answer regarding the correct url will help. If so, then ask a NEW question if you run into any future issues.
Developer documentation
answered Nov 14 '18 at 7:59
Larry KLarry K
33.7k1073103
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%2f53293460%2fdocusign-sandbox-redirect-uri-not-working%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
response_type=id_token is invalid. The response type should be code. Unfortunately, the 'Obtaining Consent' documentation still references this incorrect value.
scope=open_id can only be used if your account is associated with an Organization, and if you are an Organization Administrator. If your account is not under an Organization, you'll need to use the individual consent workflow, which means scope should be signature impersonation and the admin_consent_scope parameter should be removed.
If you would like to create an Organization in the sandbox environment, you will need to open a case with DocuSign Support requesting that functionality be added to your Demo account. To have that enabled in Production, you'll need to contact your Account Manager or the Sales team.
answered Nov 14 '18 at 18:24
DrewDrew
1,027126
Hi it would be very helpful if you could add these details to the documentation, otherwise it takes a lot of time for someone to figure this out
– Ngm
Nov 14 '18 at 23:10
add a comment |
response_type=id_token is invalid. The response type should be code. Unfortunately, the 'Obtaining Consent' documentation still references this incorrect value.
scope=open_id can only be used if your account is associated with an Organization, and if you are an Organization Administrator. If your account is not under an Organization, you'll need to use the individual consent workflow, which means scope should be signature impersonation and the admin_consent_scope parameter should be removed.
If you would like to create an Organization in the sandbox environment, you will need to open a case with DocuSign Support requesting that functionality be added to your Demo account. To have that enabled in Production, you'll need to contact your Account Manager or the Sales team.
answered Nov 14 '18 at 18:24
DrewDrew
1,027126
Hi it would be very helpful if you could add these details to the documentation, otherwise it takes a lot of time for someone to figure this out
– Ngm
Nov 14 '18 at 23:10
add a comment |
response_type=id_token is invalid. The response type should be code. Unfortunately, the 'Obtaining Consent' documentation still references this incorrect value.
scope=open_id can only be used if your account is associated with an Organization, and if you are an Organization Administrator. If your account is not under an Organization, you'll need to use the individual consent workflow, which means scope should be signature impersonation and the admin_consent_scope parameter should be removed.
If you would like to create an Organization in the sandbox environment, you will need to open a case with DocuSign Support requesting that functionality be added to your Demo account. To have that enabled in Production, you'll need to contact your Account Manager or the Sales team.
answered Nov 14 '18 at 18:24
DrewDrew
1,027126
response_type=id_token is invalid. The response type should be code. Unfortunately, the 'Obtaining Consent' documentation still references this incorrect value.
scope=open_id can only be used if your account is associated with an Organization, and if you are an Organization Administrator. If your account is not under an Organization, you'll need to use the individual consent workflow, which means scope should be signature impersonation and the admin_consent_scope parameter should be removed.
If you would like to create an Organization in the sandbox environment, you will need to open a case with DocuSign Support requesting that functionality be added to your Demo account. To have that enabled in Production, you'll need to contact your Account Manager or the Sales team.
answered Nov 14 '18 at 18:24
DrewDrew
1,027126
answered Nov 14 '18 at 18:24
DrewDrew
1,027126
answered Nov 14 '18 at 18:24
DrewDrew
1,027126
answered Nov 14 '18 at 18:24
DrewDrew
1,027126
1,027126
Hi it would be very helpful if you could add these details to the documentation, otherwise it takes a lot of time for someone to figure this out
– Ngm
Nov 14 '18 at 23:10
add a comment |
Hi it would be very helpful if you could add these details to the documentation, otherwise it takes a lot of time for someone to figure this out
– Ngm
Nov 14 '18 at 23:10
Hi it would be very helpful if you could add these details to the documentation, otherwise it takes a lot of time for someone to figure this out
– Ngm
Nov 14 '18 at 23:10
Hi it would be very helpful if you could add these details to the documentation, otherwise it takes a lot of time for someone to figure this out
– Ngm
Nov 14 '18 at 23:10
add a comment |
Your question is not so clear -- please update your question if this answer is in the wrong direction.
I think you are trying to implement the oauth authorization code grant flow and are having a problem.
The starting url for DocuSign for the oauth auth code grant flow:
- For the developer sandbox environment: https://account-d.docusign.com/oauth/auth
- For the production platforms: https://account.docusign.com/oauth/auth
Also, why are you including the admin_consent_scope query parameter?
Hopefully this answer regarding the correct url will help. If so, then ask a NEW question if you run into any future issues.
Developer documentation
answered Nov 14 '18 at 7:59
Larry KLarry K
33.7k1073103
add a comment |
Your question is not so clear -- please update your question if this answer is in the wrong direction.
I think you are trying to implement the oauth authorization code grant flow and are having a problem.
The starting url for DocuSign for the oauth auth code grant flow:
- For the developer sandbox environment: https://account-d.docusign.com/oauth/auth
- For the production platforms: https://account.docusign.com/oauth/auth
Also, why are you including the admin_consent_scope query parameter?
Hopefully this answer regarding the correct url will help. If so, then ask a NEW question if you run into any future issues.
Developer documentation
answered Nov 14 '18 at 7:59
Larry KLarry K
33.7k1073103
add a comment |
Your question is not so clear -- please update your question if this answer is in the wrong direction.
I think you are trying to implement the oauth authorization code grant flow and are having a problem.
The starting url for DocuSign for the oauth auth code grant flow:
- For the developer sandbox environment: https://account-d.docusign.com/oauth/auth
- For the production platforms: https://account.docusign.com/oauth/auth
Also, why are you including the admin_consent_scope query parameter?
Hopefully this answer regarding the correct url will help. If so, then ask a NEW question if you run into any future issues.
Developer documentation
answered Nov 14 '18 at 7:59
Larry KLarry K
33.7k1073103
Your question is not so clear -- please update your question if this answer is in the wrong direction.
I think you are trying to implement the oauth authorization code grant flow and are having a problem.
The starting url for DocuSign for the oauth auth code grant flow:
- For the developer sandbox environment: https://account-d.docusign.com/oauth/auth
- For the production platforms: https://account.docusign.com/oauth/auth
Also, why are you including the admin_consent_scope query parameter?
Hopefully this answer regarding the correct url will help. If so, then ask a NEW question if you run into any future issues.
Developer documentation
answered Nov 14 '18 at 7:59
Larry KLarry K
33.7k1073103
answered Nov 14 '18 at 7:59
Larry KLarry K
33.7k1073103
answered Nov 14 '18 at 7:59
Larry KLarry K
33.7k1073103
answered Nov 14 '18 at 7:59
Larry KLarry K
33.7k1073103
33.7k1073103
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%2f53293460%2fdocusign-sandbox-redirect-uri-not-working%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
