To use DIDAuth for private key proof, your could use #affinidi #sdk https://github.com/affinidi/affinidi-core-sdk/tree/master/common-libs/did-auth-lib. It covers a lot of cases when the resource is connected to did. What to do if you need to share claims together with DID? The answer is quite simple all you need is a slightly modified exchange protocol for Verifier. So we ask the verifier to send us a challenge and issue a VP. All protocols have a common issue - the adoption curve. It is much easier to get adoption when you build on top of standards that are already in use. I am happy to see the recent OpenID for Verifiable Presentations spec https://openid.net/specs/openid-4-verifiable-presentations-1_0.html that is based on another fantastic spec: Self-Issued OpenID Provider v2 https://openid.net/specs/openid-connect-self-issued-v2-1_0.html. It lifts #SSI concepts with #openId ecosystem and allows us to use a VP for advanced DID Auth