Expand description
LexeConnect: one-tap sharing of a Lexe client credential with an app or service. Implements the protocol parts of the LexeConnect spec; UI and credential creation are left to the WALLET.
- The REQUESTER builds a
PendingRequestand shows its connection string as a link or QR code. - The WALLET parses it, shows the user a
RequesterDisplay, and responds with aDeliveryAction. - The REQUESTER accepts the delivered bytes, which yields the verified
CredentialResponse.
- Comments cite the spec by section heading, e.g.
// Spec: Encryption. - Everything is I/O-free except the
httpmodule. - The REQUESTER side and
respondneed thecryptofeature; without it the crate is types only, e.g. for parsing connection strings.
Modules§
- http
- HTTP delivery and a mailbox client. HTTP delivery for the WALLET and a mailbox client for the REQUESTER.
- mailbox
- The mailbox address and an in-memory mailbox store. The mailbox address and an in-memory mailbox store.
- request
- The credential request and its connection string. The credential request and its connection string.
- requester
- The REQUESTER side: build requests, accept and verify responses. The REQUESTER side: build requests, accept and verify responses.
- response
- The credential response and its JSON form. The credential response and its JSON form.
- seal
- HPKE sealing of responses. HPKE sealing of responses.
- wallet
- The WALLET side: approval screen model and response delivery. The WALLET side: approval screen model and response delivery.
Constants§
- LEXE_
MAILBOX_ URL - Lexe’s public mailbox.