fix: handling of user-defined jwt claims #1517
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #1515
config.oauth.claims.privileges
to conform to MySQL JSON path syntax by double-quoting all object properties.config.oauth.claims.privileges
to surround the path statement with single-quotes in order to support the double-quoted path componentsformatChain()
toformatJsChain()
for clarityconfig.oauth.claims
for clarity:privileges
=>privilegesChain
privilegesPath
=>privileges
oauth.claims
fromEnv.js
served to the web app since it is no longer used by any web app codeconst
declaration inUser.js
$.name
with$.${config.oauth.claims.name}
inCollectionService.js
STIGMAN_JWT_*_CLAIM
environment variables to describe which variables MUST NOT be nested and MUST be valid ECMAScript identifiers, or MAY be nested and SHOULD be valid ECMAScript identifiers.STIGMAN_JWT_PRIVILEGES_CLAIM
is the only variable documented as allowing nesting.