investigate NPE in test jwt-spec:arbitrary-token-with-separators #2
Labels
question
Further information is requested
Comments
line-o
added a commit
that referenced
this issue
Jun 4, 2021
refs #2 The implementation of `jwt:encode` with arrow expressions failed with an NPE. It does so only when called in a test case as part of an XQSuite. Since this module is considered security relevant code the functon was refactored to be extra sure this will work under all circumstances. If the underlying NPE of the XQuery runtime is fixed the implementation can use arrow expressions again.
line-o
added a commit
that referenced
this issue
Jun 30, 2021
refs #2 The implementation of `jwt:encode` with arrow expressions failed with an NPE. It does so only when called in a test case as part of an XQSuite. Since this module is considered security relevant code the functon was refactored to be extra sure this will work under all circumstances. If the underlying NPE of the XQuery runtime is fixed the implementation can use arrow expressions again.
github-actions bot
pushed a commit
that referenced
this issue
Jun 30, 2021
# [2.0.0](v1.1.2...v2.0.0) (2021-06-30) ### Bug Fixes * **deps:** declare stable versions as minimum ([610e1c8](610e1c8)) * **jwt:** possible NPE in jwt:encode ([1a5e483](1a5e483)), closes [#2](#2) ### feature * release for exist 5.3.0 ([902a24b](902a24b)) ### BREAKING CHANGES * depends on processor version 5.3.0 and crypto lib version 6.0.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: