You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already benefit from typed header parsing for the authorization header. We should author an extension to the typed headers that are offered by axum to include something to make parsing ucan headers more convenient and consistent.
The text was updated successfully, but these errors were encountered:
If anyone looks to pick this up, we have [almost] an implementation in fission-server that will be extracted to a generic axum extractor. Will update as we get closer. It probably makes sense to implement this as a separate crate from rs-ucan, but appreciate any thoughts on the matter!
After we integrate support for changes to
rs-ucan
landing in ucan-wg/rs-ucan#28, we will have to contend with a new world where HTTP request headers that use UCAN-based JWT for authorization may also include auxilliaryucan
headers (see: https://github.com/ucan-wg/ucan-as-bearer-token#2-request-headers).We already benefit from typed header parsing for the
authorization
header. We should author an extension to the typed headers that are offered byaxum
to include something to make parsingucan
headers more convenient and consistent.The text was updated successfully, but these errors were encountered: