Is the /v2/keys endpoint compatible with libraries...
# ask-a-descopera
acceptable-airport-27193
07/06/2023, 9:12 PMIs the /v2/keys endpoint compatible with libraries expecting JKS key endpoints?
s
square-vr-55083
07/06/2023, 9:14 PMdo you mean JWKS ?
a
acceptable-airport-27193
07/06/2023, 9:18 PMyes
s
square-vr-55083
07/06/2023, 9:19 PMI think this is what you are looking for https://docs.descope.com/customize/auth/oidc/#example-well-known-oidc-configuration
a
acceptable-airport-27193
07/06/2023, 9:21 PMI have descope working with my UI to complete the login. My current task is token verification on the server (in a language without the descope SDK). So I am trying to use a JWT library that can get key data from JWKS, or to configure this library to use the key data returned from descope.
acceptable-airport-27193
07/06/2023, 9:22 PMI will see if the doc has anything about JWT key verification.
acceptable-airport-27193
07/06/2023, 9:27 PMThe URL configured in that for "well known" JWKS URI returns the same result as the /v2/keys URL so it looks like it is JWKS compatible.
s
square-vr-55083
07/06/2023, 9:32 PMyes,
Copy code
<https://api.descope.com/{project> id}/.well-known/jwks.jsonsquare-vr-55083
07/06/2023, 9:33 PMLooping in @salmon-night-88354 in case you need more help on this
👍 1
a
acceptable-airport-27193
07/06/2023, 9:44 PMIf that is valid, then my problem is probably configuring the library. It reports "No strategy provided" which is probably something I need to do, unless this sounds like a JWKS thing.
s
salmon-night-88354
07/06/2023, 10:02 PM@acceptable-airport-27193 you updated it with your project ID? It loads successfully when you go to it within a web browser?
Which library are you using? I can test as well.