Jump to content

Helmut Granda

Working for someone else - bad authorization header

Go to solution Solved by GreenSock,

Recommended Posts

If I am working with someone else and they have joined the Club but I am not part of the Club but I am going to assist with a project. Do I need to join the Club in order to use it myself or can I just use a token in order to do so?


Currently I do have a token but when I try to install GreenSock I get:


npm ERR! code E403
npm ERR! 403 403 Forbidden - GET https://npm.greensock.com/@gsap%2fshockingly - bad authorization header. Please login again
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.


Link to comment
Share on other sites

  • Solution

Thanks for asking, @Helmut Granda. You should not use someone else's token. If the person you're working with has a multi-developer license, they should just assign one of those developer slots to your account (they can do that from their account dashboard). That will give you a token of your own that you can get from your account dashboard. If they don't have a multi-developer license, they should get one :)


Let us know if you have any other questions. Enjoy the tools!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.