Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to Access the Clinet Secret Id in Node JS application #514

Closed
kiranbalivada opened this issue Mar 1, 2017 · 3 comments
Closed

Comments

@kiranbalivada
Copy link

kiranbalivada commented Mar 1, 2017

Node.js Version : 5.0.0
OS: Windows 10
Scope :Token Generation Using Google 0auth 2

Hi All,

In my Node JS application, we are using Client Secret ID for Google 0Auth 2. When I directly assign the static Client Secret ID to the google authentication key it is working fine. But when I read the value of Client Secret ID from a text box in the UI by code and assigned to google authentication key, on submit it is displaying an error message "the key is probably invalid".

Can you please advice.

Following is sample code:

function Verify(){
var options={
email: Client Secret mail
key: Client Secret ID,
scopes: ['https://www.googleapis.com/auth/content']
}
googleAuth.authenticate(options)

Thanks ,
Kiran Kumar.

@Knighton910
Copy link
Contributor

Knighton910 commented Mar 1, 2017

theoephraim/node-google-spreadsheet#38

see if this helps you:

screen shot 2017-02-28 at 11 45 51 pm


if it doesn't help, we will keep trying to solve this with you.

@kiranbalivada
Copy link
Author

kiranbalivada commented Mar 1, 2017

In My requirement keeping the P12 file in the solution folder would require a code checkin every time each different client. that's why I want to avoid using P12. Is there any other way please let me know

Thank you

@Knighton910
Copy link
Contributor

This doesn't look like a node-js problem specifically, and I don't have knowledge of this tech. It would probably be better posted on stackoverflow. How ever if you post a terminal photo or a package.json pic, of the package. And as well, your full error log, then maybe i can help point you in the right direction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants