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
{{ message }}
This repository was archived by the owner on Feb 11, 2025. It is now read-only.
Support for signing and verification of bindles, both on the client and server side, will soon be fully implemented. So, client and server both must have their own secret keys as well as access to keyrings with accepted public keys for signing and verification actions.
I'm wondering if we also want to use these same assets for the purposes of authentication between client and server? (Currently, bindle supports basic auth and oidc in this realm.)
The main use case I'm envisioning is a server configured with a keyring of approved public keys and operators wish to only allow endpoint requests (regardless of type) from this same set of identities.
Would this be muddying the waters and/or overextending the key/identity logic in bindle?