Skip to content
This repository was archived by the owner on Feb 2, 2025. It is now read-only.

"Public key not found at" xxx #3

Open
UnifyBadPirate opened this issue Oct 14, 2019 · 4 comments
Open

"Public key not found at" xxx #3

UnifyBadPirate opened this issue Oct 14, 2019 · 4 comments

Comments

@UnifyBadPirate
Copy link

UnifyBadPirate commented Oct 14, 2019

When attempting verify I get the error:

Error: Public key not found at https://cognito-idp.us-west-2.amazonaws.com/us-west-2_zXjcft1AV/.well-known/jwks.json

However, if I access that url directly there appears to be valid key JSON:

{
   "keys":[
      {
         "alg":"RS256",
         "e":"AQAB",
         "kid":"qWCZy9S8+ZUdx1ULRcU2NyC3ovIp19EzIfWDtrVcWhs=",
         "kty":"RSA",
         "n":"i4uoosLV8Fw5X2vzy_BWgzyOxFr5rDvcKWWs0pmjWnV7ynRtNZea6mc9HBbp6kYt9gfP9VnW3qC-tA1RDchwDD6Qfsq1xi1S7A_b6vjeFGdQHMSK-r9iZfWcVoiw8pIDJ3NII5Y2ew_KT4j0tDq5Gk93D0fxAa-XCZSfdX7sTExvIGhqQF1R3PIpjqrLrRBhZ717Ab1h_mUw913UXYPtYu3ykydorEFmH_Ln1w851l0VyyJnErMobR3vNrYlRbQUmNTxjO7ruhK62hMO1HZnJ8J1E81Bks9X5_I2qlIaI0EEPSH29T91PIuK8HNm5jkJnoW1xB_mrc_y5BcOdXNsNQ",
         "use":"sig"
      },
      {
         "alg":"RS256",
         "e":"AQAB",
         "kid":"kTOAgwxCbXrExZ8aFsqSVkAp1z+iIcA2ujiCkTn2/EI=",
         "kty":"RSA",
         "n":"gXQ8_VYMXg1SZaSWijNocIp5SX54-8IOmAukZa36oIHiRfUNwZBH_7jqSXFIXMMZ55ju0qTR8G1NL1hb5E5mN_33CgKst-4mr3iBt7xjTKnKLG2LTjrqVJaLGujlJgVOMFEvuFwDKeR5RGntN9dleC1Sn5veGoS3qP-_aiHGyo1i0XFrYWpjlZlDp41xBpk-MfTc6g91EvzWfUecVf5ZDiRZGTtZDHBOGPL06KRqbvwp-SgEraR-O2rEclfXFWYRJA-JSB3JjAg9jrWwUmNwvVO2ojEXGhsBvz6FJObCVqp0vtg3MyVzjXZTpZXFMiRHUzLSgrU6PznE1VhTtjk8xw",
         "use":"sig"
      }
   ]
}
@phong-innomizetech
Copy link

@UnifyBadPirate Did you resolve this issue?

@UnifyBadPirate
Copy link
Author

No I was not able to. Are you having the same trouble? @phong-innomizetech

@phong-innomizetech
Copy link

Yes we had the same issue and I have to implement it instead of using this lib.

@ilikepi63
Copy link

I just had to replace this in our production environment because a previous dev decided to use this package. Rather just go directly to the jwt/jwk route, this package is not stable.

The invocations would work temperamentally at best.

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

No branches or pull requests

3 participants