| Crates.io | affinidi-did-authentication |
| lib.rs | affinidi-did-authentication |
| version | 0.1.11 |
| created_at | 2025-03-20 10:35:49.669561+00 |
| updated_at | 2025-09-08 08:44:27.352995+00 |
| description | Using proof of DID ownership to authenticate to services |
| homepage | https://affinidi.com/ |
| repository | https://github.com/affinidi/affinidi-tdk-rs |
| max_upload_size | |
| id | 1599078 |
| size | 210,660 |
IMPORTANT:
affinidi-did-authentication crate is provided "as is" without any warranties or guarantees, and by using this framework, users agree to assume all risks associated with its deployment and use including implementing security, and privacy measures in their applications. Affinidi assumes no liability for any issues arising from the use or modification of the project.
Affinidi DID Authentication enables basic authentication using a DID and proof that you have access to the secrets to encrypt a server challenge. This can be used for services requiring some form of authentication/authorisation mechanism.
NOTE: There are two implementations of DID Authentication that differ. As a result this library will detect and handle the two implementations in the interim. Once alignment is complete and refactored into Affinidi Messaging and Meeting Place - then this library will be streamlined.
You can run Affinidi DID Authentication as a binary, this allows for simple testing and/or using the binary in other applications.
NOTE: The Binary for did_auth is located in the affinidi-tdk crate
There are two operating modes for the binary:
cargo run -- -a did:web:meetingplace.world environment -n Alice
NOTE: When manually entering a DID, you pass the secrets into STDIN
If you face any issues or have suggestions, please don't hesitate to contact us using this link.
If you have a technical issue with the Affinidi Messaging GitHub repo, you can also create an issue directly in GitHub.
If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.