Skip to content
New issue

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

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

Already on GitHub? # to your account

XQuery error in handling invalid-signature #11

Closed
ahenket opened this issue Jun 24, 2021 · 1 comment · Fixed by #12
Closed

XQuery error in handling invalid-signature #11

ahenket opened this issue Jun 24, 2021 · 1 comment · Fixed by #12
Labels

Comments

@ahenket
Copy link

ahenket commented Jun 24, 2021

I was testing what happens you use a token from a different server. The result was not invalid-signature as I had expected, but:

err:XPTY0004 It is a type error if, during the static analysis phase, an expression is found to have a static type that is not appropriate for the context in which the expression occurs, or during the dynamic evaluation phase, the dynamic type of a value does not match a required type as specified by the matching rules in 2.5.4 SequenceType Matching. xs:string(invalid-signature) is not a sub-type of xs:QName

I believe that is due to line 83 in jwt-xqm where it says:

else (error("invalid-signature"))

The fix would be:

else (error(xs:QName("invalid-signature")))
line-o added a commit that referenced this issue Jun 25, 2021
fixes #11

The error thrown when a token has an invalid signature is
now given xs:QName.
github-actions bot pushed a commit that referenced this issue Jun 25, 2021
## [1.1.2](v1.1.1...v1.1.2) (2021-06-25)

### Bug Fixes

* **jwt:** error expects xs:QName ([0047857](0047857)), closes [#11](#11)
@github-actions
Copy link

🎉 This issue has been resolved in version 1.1.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging a pull request may close this issue.

1 participant