Sign in with AliasCloak
Let people sign in to your site with an AliasCloak mailbox without learning their private key, messages, files, or a universal cross-site identifier.
Provider metadata
Issuer
https://aliascloak.comDiscovery document
https://aliascloak.com/.well-known/openid-configurationPrivacy model
The required openid scope returns a stable pairwise sub: the same AliasCloak mailbox gets a different identifier at unrelated relying-party sectors. Your application should use sub as the account key.
The optional alias scope asks the person to disclose their current AliasCloak alias. It is shown as an explicit consent checkbox and is not selected by default. AliasCloak exposes no sign-in scope for reading messages, sending mail, reading chats, files, contacts, private keys, or recovery data.
Authorization request
Generate a fresh state, nonce, and PKCE verifier for every sign-in. Derive an S256 code challenge and redirect the browser to the authorization endpoint.
https://aliascloak.com/oidc/auth?
client_id=YOUR_CLIENT_ID&
response_type=code&
scope=openid&
redirect_uri=https%3A%2F%2Fexample.com%2Fauth%2Faliascloak%2Fcallback&
state=RANDOM_STATE&
nonce=RANDOM_NONCE&
code_challenge=BASE64URL_SHA256_VERIFIER&
code_challenge_method=S256Exchange the code
POST the returned code and the original PKCE verifier to the discovered token endpoint. Public clients authenticate with token_endpoint_auth_method=none; there is no shared client secret to leak.
POST https://aliascloak.com/oidc/token
Content-Type: application/x-www-form-urlencoded
grant_type=authorization_code&
client_id=YOUR_CLIENT_ID&
code=RETURNED_CODE&
redirect_uri=https%3A%2F%2Fexample.com%2Fauth%2Faliascloak%2Fcallback&
code_verifier=ORIGINAL_PKCE_VERIFIERValidate the ID token
Use a maintained OpenID Connect client library for your framework. Validate the signature against the provider JWKS as well as iss, aud, expiry, and the nonce you sent. Do not use the optional alias as the database primary key; aliases can change.