Drizzt Posted February 14 Share Posted February 14 Hi there, Just bought premium license. Followed the installation instructions, created a .npmrc file in the root dir, copied pasted the contents into .npmrc etc. But npm install gsap@npm:@gsap/shockingly fails with 403 Forbidden - GET https://npm.greensock.com/@gsap%2fshockingly - bad authorization header. Please login again Any suggestions? Thanks! Link to comment Share on other sites More sharing options...
Drizzt Posted February 14 Author Share Posted February 14 I am running on NPM v10.2.4 and Node v21.6.1 Link to comment Share on other sites More sharing options...
Drizzt Posted February 14 Author Share Posted February 14 It seems the token generated in my account dashboard is working. But the token which can be generated on the installation page is not! https://gsap.com/docs/v3/Installation Is this a bug? Link to comment Share on other sites More sharing options...
Rodrigo Posted February 14 Share Posted February 14 Hi @Drizzt and welcome to the GSAP Forums! Thanks for being a Club GSAP member and supporting GSAP! I'm not seeing any difference between the token in my account's dashboard and the one in the installation page 🤷♂️ Maybe you copied an extra space or line break? Are you seeing two completely different tokens in those pages? Happy Tweening! Link to comment Share on other sites More sharing options...
Drizzt Posted February 14 Author Share Posted February 14 Hi Rodrigo, Thanks for you answer (pretty sure it was not a extra space line-break). But here are some more clues: When I just re-logged in to the gsap platform the tokens on both pages were the same. When I regenerate on the installation page, that code does not work. When I then go the dashboard, the code there differs from the code that was just regenerated on the installation page. When I regenerate on the dashboard page that code works. Link to comment Share on other sites More sharing options...
Cassie Posted February 14 Share Posted February 14 Heya! I'm looking into this - thanks so much for flagging it. Did you manage to access the repo with the token from the dashboard page? 1 Link to comment Share on other sites More sharing options...
Drizzt Posted February 15 Author Share Posted February 15 Thanks, token on dashboard has always been working. The newly generated token on installation page is causing the problem (as far as i can see) Link to comment Share on other sites More sharing options...
GreenSock Posted February 15 Share Posted February 15 Howdy, @Drizzt. Are you saying that you do have it working with a particular token? Or are you saying that no matter what token you use, you constantly get a "403 Forbidden - GET https://npm.greensock.com/@gsap%2fshockingly - bad authorization header" error? Link to comment Share on other sites More sharing options...
Drizzt Posted February 16 Author Share Posted February 16 Yes, token generated on dashboard is working. Token generated on installation instruction page is not. Link to comment Share on other sites More sharing options...
GreenSock Posted February 16 Share Posted February 16 I see. Yeah, those should match now. Thanks for pointing out the problem. Sorry about the confusion. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now