Interface: LunaSecConfig

The configuration for the LunaSec Node Plugin

Properties

• tokenizerURL: string

The URL where the tokenizer backend can be queried

• auth: Object

The configuration for authentication

Name	Type	Description
`secrets`	`SecretConfig`	A configuration object that tells the LunaSec JWT generator where to find the signing key. LunaSec uses JWTs minted on your server in a few places. `example` `{ provider: 'environment' }` which will read the signing key from `process.env.LUNASEC_SIGNING_KEY` as base64 encoded Or for example to just pass it in directly `example` `{type:'manual', signingKey: createPrivateKey(signingKey) }` This needs to be a node KeyLike object
`sessionIdProvider`	`SessionIdProvider`	A callback used automatically by LunaSec when we have the req object and would like to know the sessionId. Used in automatic granting and also the Auth Plugin
`pluginBaseUrl?`	`string`	Optionally add a baseroute to the auth plugin's routes, useful if you need all of your application routes to be behind some route like `/api`
`publicTokenizerUrl?`	`string`	Optionally have the auth redirect URL use localhost as the domain name. This is used in the demo mode and local development.

• Optional secureResolverConfig: SecureResolverSdkConfig

Optionally configure the Secure Resolver functionality of the plugin, must be configured if you want to use Secure Resolvers