i am using gcp service account but when calling dialogue flow api its giving error :












0















here is error:




Your application has authenticated using end user credentials from the
Google Cloud SDK or Google Cloud Shell which are not supported by the
dialogflow.googleapis.com. We recommend that most server applications
use service accounts instead. For more information about service
accounts and how to use them in your application, see
https://cloud.google.com/docs/authentication/.











share|improve this question

























  • I would double check that your application isn't running using the Application default credentials, and that your machine wasn't configured using 'gcloud auth login' or something similar.

    – FridayPush
    Nov 21 '18 at 7:10











  • thanks..!! now it start working i just activate my service account by using gcloud auth activate-service-account --key-file <path to file>.

    – BugResolver
    Nov 21 '18 at 7:55











  • @BugResolver Can you please add your solution as an answer in this post? so everyone could see it better. Thank you in advance.

    – Alex Riquelme
    Nov 21 '18 at 11:14
















0















here is error:




Your application has authenticated using end user credentials from the
Google Cloud SDK or Google Cloud Shell which are not supported by the
dialogflow.googleapis.com. We recommend that most server applications
use service accounts instead. For more information about service
accounts and how to use them in your application, see
https://cloud.google.com/docs/authentication/.











share|improve this question

























  • I would double check that your application isn't running using the Application default credentials, and that your machine wasn't configured using 'gcloud auth login' or something similar.

    – FridayPush
    Nov 21 '18 at 7:10











  • thanks..!! now it start working i just activate my service account by using gcloud auth activate-service-account --key-file <path to file>.

    – BugResolver
    Nov 21 '18 at 7:55











  • @BugResolver Can you please add your solution as an answer in this post? so everyone could see it better. Thank you in advance.

    – Alex Riquelme
    Nov 21 '18 at 11:14














0












0








0








here is error:




Your application has authenticated using end user credentials from the
Google Cloud SDK or Google Cloud Shell which are not supported by the
dialogflow.googleapis.com. We recommend that most server applications
use service accounts instead. For more information about service
accounts and how to use them in your application, see
https://cloud.google.com/docs/authentication/.











share|improve this question
















here is error:




Your application has authenticated using end user credentials from the
Google Cloud SDK or Google Cloud Shell which are not supported by the
dialogflow.googleapis.com. We recommend that most server applications
use service accounts instead. For more information about service
accounts and how to use them in your application, see
https://cloud.google.com/docs/authentication/.








google-cloud-platform dialogflow






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 21 '18 at 13:04









LundinCast

2,44341222




2,44341222










asked Nov 21 '18 at 6:52









BugResolverBugResolver

153




153













  • I would double check that your application isn't running using the Application default credentials, and that your machine wasn't configured using 'gcloud auth login' or something similar.

    – FridayPush
    Nov 21 '18 at 7:10











  • thanks..!! now it start working i just activate my service account by using gcloud auth activate-service-account --key-file <path to file>.

    – BugResolver
    Nov 21 '18 at 7:55











  • @BugResolver Can you please add your solution as an answer in this post? so everyone could see it better. Thank you in advance.

    – Alex Riquelme
    Nov 21 '18 at 11:14



















  • I would double check that your application isn't running using the Application default credentials, and that your machine wasn't configured using 'gcloud auth login' or something similar.

    – FridayPush
    Nov 21 '18 at 7:10











  • thanks..!! now it start working i just activate my service account by using gcloud auth activate-service-account --key-file <path to file>.

    – BugResolver
    Nov 21 '18 at 7:55











  • @BugResolver Can you please add your solution as an answer in this post? so everyone could see it better. Thank you in advance.

    – Alex Riquelme
    Nov 21 '18 at 11:14

















I would double check that your application isn't running using the Application default credentials, and that your machine wasn't configured using 'gcloud auth login' or something similar.

– FridayPush
Nov 21 '18 at 7:10





I would double check that your application isn't running using the Application default credentials, and that your machine wasn't configured using 'gcloud auth login' or something similar.

– FridayPush
Nov 21 '18 at 7:10













thanks..!! now it start working i just activate my service account by using gcloud auth activate-service-account --key-file <path to file>.

– BugResolver
Nov 21 '18 at 7:55





thanks..!! now it start working i just activate my service account by using gcloud auth activate-service-account --key-file <path to file>.

– BugResolver
Nov 21 '18 at 7:55













@BugResolver Can you please add your solution as an answer in this post? so everyone could see it better. Thank you in advance.

– Alex Riquelme
Nov 21 '18 at 11:14





@BugResolver Can you please add your solution as an answer in this post? so everyone could see it better. Thank you in advance.

– Alex Riquelme
Nov 21 '18 at 11:14












1 Answer
1






active

oldest

votes


















0














Many of the Client Libraries pull from the Application Default Credentials, a summary of how they're checked is provided on that link. Essentially it will check environmental variables for a path and pull credentials from that location. This error message means you're using a User account, and not a service account.



Most commonly you logged in once using gcloud auth login, and even though you provided your service account it's still pulling from the Application Default location.



As you did, the method to associate a specific service account is gcloud auth activate-service-account --key-file <path>



Alternatively to use the true application default you can use gcloud auth application-default login






share|improve this answer
























  • also i have change code :let config = { credentials: { private_key: privateKey, client_email: clientEmail } } const sessionClient = new dialogflow.SessionsClient(config); const sessionPath = sessionClient.sessionPath(projectId, sessionId); }

    – BugResolver
    Jan 3 at 7:56













  • now it's working fine

    – BugResolver
    Jan 3 at 7:57











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%2f53406673%2fi-am-using-gcp-service-account-but-when-calling-dialogue-flow-api-its-giving-err%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Many of the Client Libraries pull from the Application Default Credentials, a summary of how they're checked is provided on that link. Essentially it will check environmental variables for a path and pull credentials from that location. This error message means you're using a User account, and not a service account.



Most commonly you logged in once using gcloud auth login, and even though you provided your service account it's still pulling from the Application Default location.



As you did, the method to associate a specific service account is gcloud auth activate-service-account --key-file <path>



Alternatively to use the true application default you can use gcloud auth application-default login






share|improve this answer
























  • also i have change code :let config = { credentials: { private_key: privateKey, client_email: clientEmail } } const sessionClient = new dialogflow.SessionsClient(config); const sessionPath = sessionClient.sessionPath(projectId, sessionId); }

    – BugResolver
    Jan 3 at 7:56













  • now it's working fine

    – BugResolver
    Jan 3 at 7:57
















0














Many of the Client Libraries pull from the Application Default Credentials, a summary of how they're checked is provided on that link. Essentially it will check environmental variables for a path and pull credentials from that location. This error message means you're using a User account, and not a service account.



Most commonly you logged in once using gcloud auth login, and even though you provided your service account it's still pulling from the Application Default location.



As you did, the method to associate a specific service account is gcloud auth activate-service-account --key-file <path>



Alternatively to use the true application default you can use gcloud auth application-default login






share|improve this answer
























  • also i have change code :let config = { credentials: { private_key: privateKey, client_email: clientEmail } } const sessionClient = new dialogflow.SessionsClient(config); const sessionPath = sessionClient.sessionPath(projectId, sessionId); }

    – BugResolver
    Jan 3 at 7:56













  • now it's working fine

    – BugResolver
    Jan 3 at 7:57














0












0








0







Many of the Client Libraries pull from the Application Default Credentials, a summary of how they're checked is provided on that link. Essentially it will check environmental variables for a path and pull credentials from that location. This error message means you're using a User account, and not a service account.



Most commonly you logged in once using gcloud auth login, and even though you provided your service account it's still pulling from the Application Default location.



As you did, the method to associate a specific service account is gcloud auth activate-service-account --key-file <path>



Alternatively to use the true application default you can use gcloud auth application-default login






share|improve this answer













Many of the Client Libraries pull from the Application Default Credentials, a summary of how they're checked is provided on that link. Essentially it will check environmental variables for a path and pull credentials from that location. This error message means you're using a User account, and not a service account.



Most commonly you logged in once using gcloud auth login, and even though you provided your service account it's still pulling from the Application Default location.



As you did, the method to associate a specific service account is gcloud auth activate-service-account --key-file <path>



Alternatively to use the true application default you can use gcloud auth application-default login







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 21 '18 at 17:36









FridayPushFridayPush

61717




61717













  • also i have change code :let config = { credentials: { private_key: privateKey, client_email: clientEmail } } const sessionClient = new dialogflow.SessionsClient(config); const sessionPath = sessionClient.sessionPath(projectId, sessionId); }

    – BugResolver
    Jan 3 at 7:56













  • now it's working fine

    – BugResolver
    Jan 3 at 7:57



















  • also i have change code :let config = { credentials: { private_key: privateKey, client_email: clientEmail } } const sessionClient = new dialogflow.SessionsClient(config); const sessionPath = sessionClient.sessionPath(projectId, sessionId); }

    – BugResolver
    Jan 3 at 7:56













  • now it's working fine

    – BugResolver
    Jan 3 at 7:57

















also i have change code :let config = { credentials: { private_key: privateKey, client_email: clientEmail } } const sessionClient = new dialogflow.SessionsClient(config); const sessionPath = sessionClient.sessionPath(projectId, sessionId); }

– BugResolver
Jan 3 at 7:56







also i have change code :let config = { credentials: { private_key: privateKey, client_email: clientEmail } } const sessionClient = new dialogflow.SessionsClient(config); const sessionPath = sessionClient.sessionPath(projectId, sessionId); }

– BugResolver
Jan 3 at 7:56















now it's working fine

– BugResolver
Jan 3 at 7:57





now it's working fine

– BugResolver
Jan 3 at 7:57


















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%2f53406673%2fi-am-using-gcp-service-account-but-when-calling-dialogue-flow-api-its-giving-err%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







Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

RAC Tourist Trophy