mikaki Docs provides public FAQs and integration guides without sign-in. Its login state example connects a dedicated RP to auth.mikaki.org and shows session rechecking and RP-local logout after passkey sign-in. You need a passkey already registered with mikaki. For a new account, see Getting started.
Docs does not require sign-in. The login example requests only openid, without your name, email or Vault contents. It has no ticket or note submission. The application-specific identifier and session information needed for login are temporarily stored in a dedicated database separate from the IdP.
On this page
Sign in to Docs#
- Select “Sign in with mikaki” at
https://docs.mikaki.org/session?lang=en. - Check that authentication is on
auth.mikaki.organd the destination isdocs.mikaki.org. - Confirm the initial application connection and verify your registered passkey.
- On returning to Docs, check that “Login state” shows “Signed in”.
Registration and login are separate operations. For a new account, obtain an invitation and follow Getting started first. Read Passkeys for device and browser considerations.
Check the session again#
“Check session again” asks the public IdP about the current session from the RP server. A successful check returns to the login state page. A confirmed revocation or expiry deletes the RP session, even if an earlier confirmation period had time remaining.
Ordinary rendering uses a previous check within its validity period. A network failure does not extend that period. Reaching authentication or seeing a button alone does not prove successful code exchange or session verification.
The demo’s RP session lasts at most one hour and cannot exceed an earlier IdP expiry. Times are shown in UTC.
Sign out of Docs#
“Sign out of Docs” deletes its RP session and cookie. It leaves mikaki SSO active, so another login in the same browser may need fewer steps.
“Open mikaki’s sign-out confirmation” is a separate action that ends IdP SSO. Read the confirmation and consider the effect on other connected applications.
Implementation and verification scope#
Docs uses a dedicated RP Worker, HTTPS origin, D1 database and RP-specific ES256 key with an exact registered callback. Its private key stays in a Worker secret. Reading the FAQs does not depend on an RP session.
| Check | Scope |
|---|---|
| PKCE, state, nonce, ID Token signature, issuer / audience | Existing RP implementation and local integration tests |
| Passkey login, session checks, RP logout and rejection after revocation | Docs RP browser test, using a disposable local OP and virtual authenticator |
| Public IdP client registration | Dedicated public key, callback and Back-Channel receiver registered by an operator |
| Public passkey round trip and actual notification delivery | Require participant actions; registration or local success alone does not establish these |
This example does not indicate OpenID Foundation certification or an independent audit. See the separate conformance results. For your own RP, read the local example.
Read next#
- Application integration: Registration and connection qualification.
- API reference: Public OP request/response and session check contracts.