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
I recall @csuwildcat mentioning this as either being impossible or very difficult, so feel free to let me know if this is a waste of time; however, regardless, I'd like to personally explore this feature as I think it could be beneficial for others long term.
Summary
It would be nice to be able to somehow send authenticated requests to the DWN HTTP API layer. Specifically, I'd like to use this feature in my project @bnonni/drpm.tools to enable my ability to construct DRLs for record creates. DRPM creates 2 DWN records: package and package/release. The current DRPM implementation toggles between DRLs for reads with an SDK fallback and SDK only for creates. Unifying and aligning install and publish such that both use DRLs as default and SDK as fallback would be nice.
Side Note
A side effect of this feature request presents the possibility for a specialized dwn-server implementation: a DRPM-registry-specific HTTP API layer. This specialized implementation of the dwn-server would be separate and called something like dwn-registry instead of dwn-server. Because of that, it is out of scope for this issue; however, its something that I plan to explore on my own, and impacts this project in a downstream way, so I at least wanted to mention it here.
Feel free to assign this to me if you think its worth exploring as I'd be happy to take this on. Thanks!
The text was updated successfully, but these errors were encountered:
I recall @csuwildcat mentioning this as either being impossible or very difficult, so feel free to let me know if this is a waste of time; however, regardless, I'd like to personally explore this feature as I think it could be beneficial for others long term.
Summary
It would be nice to be able to somehow send authenticated requests to the DWN HTTP API layer. Specifically, I'd like to use this feature in my project @bnonni/drpm.tools to enable my ability to construct DRLs for record creates. DRPM creates 2 DWN records:
package
andpackage/release
. The current DRPM implementation toggles between DRLs for reads with an SDK fallback and SDK only for creates. Unifying and aligninginstall
andpublish
such that both use DRLs as default and SDK as fallback would be nice.Side Note
A side effect of this feature request presents the possibility for a specialized dwn-server implementation: a DRPM-registry-specific HTTP API layer. This specialized implementation of the dwn-server would be separate and called something like
dwn-registry
instead ofdwn-server
. Because of that, it is out of scope for this issue; however, its something that I plan to explore on my own, and impacts this project in a downstream way, so I at least wanted to mention it here.Feel free to assign this to me if you think its worth exploring as I'd be happy to take this on. Thanks!
The text was updated successfully, but these errors were encountered: