-
Notifications
You must be signed in to change notification settings - Fork 26
Oauth not working #30
Comments
Hi @collinwong53, npm install suiteplus/nscabinet I don't have access to publish the updated versions to NPM and the author is non-responsive. I only have access to the GitHub repositories. |
@mattgaspar Thanks for the quick response. I gave it another shot, it fixed the tokens getting removed from params but I am still getting invalid login. I do notice that the nscabinet folder gets installed into node modules, and then that folder has its own node modules. Is that correct, or should it be in the root directory? |
@collinwong53 Are you sure that the role that the token was generated for has the necessary permissions? On the role, under the Setup tab make sure you have Full access for: And under Lists you might need "Documents and Files" Also, I'm not sure if you just used the wrong term but this authentication is using Token Based Authentication NOT OAuth. The node modules folder is probably not an issue but if the above doesn't help, you could delete the root node_modules folder and do an |
Hey @mattgaspar, Thanks so much for your response. It turns out all I had to do was capitalize sb_1 on the account param =(. Sorry for raising a dumb issue. I really appreciate your response though. |
Hi, I am trying to use OAuth but it seems like my credentials get deleted by checkParams function. I tried adding it back in as soon as it's deleted in the nsconfig function in the nsconfig.js but it still does not work. Am I missing something or is this a known issue?
The text was updated successfully, but these errors were encountered: