Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

publicKey without discovery #133

Open
4 tasks done
cerpins opened this issue Jan 26, 2024 · 2 comments
Open
4 tasks done

publicKey without discovery #133

cerpins opened this issue Jan 26, 2024 · 2 comments

Comments

@cerpins
Copy link

cerpins commented Jan 26, 2024

Checklist

  • I have looked into the Readme and Examples, and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved

It seems possible to avoid discovery altogether by specifying issuer instead of issuerBaseURL, and this is perfectly fine with symmetrical algorithms. However, it seems impossible to provide an asymmetrical algorithm and not specify issuerBaseURL.

Describe the ideal solution

I would like to pass the public key explicitly without doing discovery. So something like defining issuer, audience, and then public key in secret. The library jose seems to allow passing the public key already, but we never get here because node-oauth2-jwt-bearer will throw before that during validation.

Alternatives and current workarounds

Currently not possible.

Additional context

No response

@gaving
Copy link

gaving commented May 2, 2024

I've came across this issue trying to migrate from express-jwt and having the same problem.

Is there any suggested workaround? Hoping to not have to introduce JWKS for this asymmetrical setup where I have the public key available to me which I hoped to pass into secret.

Otherwise faced with jose or a jsonwebtoken approach but not sure where to turn.

@ehaynes99
Copy link

ehaynes99 commented Aug 7, 2024

There's no way to do it currently. You can pass a custom issuer and jwksUri param, but you would still have to host the JWKS yourself. The secret parameter can only be used with symmetric algorithms. As it's published by Auth0, I expect they're largely focused on their workflow where you would have the jwks hosted by them.

It's pretty straightforward with jsonwebtoken, though:

import fs from 'node:fs/promises'
import jsonWebToken from 'jsonwebtoken'

const TEN_HOURS = 10 * 60 * 60
const AUDIENCE = 'https://example.com/api'

const payload = {
  iss: 'https://example.com',
  sub: '0123456789abcdef',
  aud: [AUDIENCE],
  iat: Math.floor(Date.now() / 1000),
  exp: Math.floor(Date.now() / 1000) + TEN_HOURS,
  scope: 'openid profile email offline_access',
  azp: '0123456789abcdef',
}

const privateKey = await fs.readFile('/path/to/private.pem', 'utf8')
const publicKey = await fs.readFile('/path/to/public.pem', 'utf8')

const token = jsonWebToken.sign(payload, privateKey, { algorithm: 'RS256' })

try {
  const payload = jsonWebToken.verify(token, publicKey, {
    algorithms: ['RS256'],
    audience: AUDIENCE,
  }) as jsonWebToken.JwtPayload

  // or if you need `{ header, payload, signature }` for some reason:
  // const { header, payload, signature } = jsonWebToken.verify(token, publicKey, {
  //   algorithms: ['RS256'],
  //   audience: AUDIENCE,
  //   complete: true,
  // }) as jsonWebToken.Jwt
  console.log('payload:', payload)
} catch (error) {
  // throws if expired, invalid signature, incorrect audience, etc.
  console.error(error)
}

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

No branches or pull requests

3 participants