Uses of Package
co.ankatech.keymanagement.client.auth.model
Packages that use co.ankatech.keymanagement.client.auth.model
Package
Description
-
Classes in co.ankatech.keymanagement.client.auth.model used by co.ankatech.keymanagement.client.auth.apiClassDescriptionOAuth 2.0 authorization server metadata (RFC 8414 §2).OAuth 2.0 token response (RFC 6749 §5.1) for every grant.
-
Classes in co.ankatech.keymanagement.client.auth.model used by co.ankatech.keymanagement.client.auth.modelClassDescriptionA passkey registration made with the options of createPasskeyRegistrationOptionsA stored passkey, with the first recovery codes when it is your first strong factorCapability properties of an authenticator; a property is true only when it is establishedA new recovery code set, shown once; every earlier code is refused from now onOne of the person's authenticators.The authenticator kindThe signed-in person's authenticatorsA started TOTP enrolment, shown onceThe first code of your authenticator app, which completes the TOTP enrolmentWhether the TOTP enrolment was completed, with the first recovery codes when issuedThe new name of one of your passkeysThe tenants the signed-in person may switch to with a refresh_token grant carrying tenant_idWebAuthn RegistrationResponseJSON membersAn alternative that would admitThe kind of the path. passkey-enrolment is taken with passkey-registration-options and passkey-registration; totp-enrolment with totp-enrolment and totp-enrolment-verification, after a password the person proved or chose; federated with the action federated and this path's idp_id, in the browser.An answer of the authorization challenge endpoint: the authorization code (200), the next step of the sign-in (403 insufficient_authorization), or the move of the sign-in to the browser for a federated path (403 redirect_to_web).403 only. insufficient_authorization: the sign-in continues with another step. redirect_to_web: the sign-in continues in the browser, through the identity provider of the federated path taken; navigate the browser (top level) to GET /api/v3/auth/idp/initiate?403 only.A tenant the person may enterAn authenticator app being enrolledOAuth 2.0 authorization server metadata (RFC 8414 §2).Gets or Sets dpopSigningAlgValuesSupportedResponse containing blacklisted token JTIsRequest to change the password of the account named by the access token.Request for a password-reset link.Acknowledgement of a password-reset request.One live sign-in session of a person.The kind of the identity provider that authenticated the person.A list of live sign-in sessionsOAuth 2.0 token introspection response (RFC 7662)OAuth 2.0 error response per RFC 6749 Section 5.2 with additional RFC 7807 fieldsOAuth 2.0 error code per RFC 6749 Section 5.2.ProblemDetailStandard RFC 7807 problem envelope.WebAuthn AuthenticatorSelectionCriteriaWebAuthn PublicKeyCredentialDescriptorJSONWebAuthn PublicKeyCredentialParametersThe client extensions requestedWebAuthn PublicKeyCredentialCreationOptionsJSONThe attestation conveyance preferenceWebAuthn PublicKeyCredentialRpEntityWebAuthn PublicKeyCredentialUserEntityJSONWebAuthn PublicKeyCredentialRequestOptionsJSONThe user verification requirementRequest to reset password using tokenResponse for successful password resetOne membership the authenticated identity may sign intoPLATFORM_ADMIN for the membership of the platform tenant, TENANT_ADMIN for any other tenantOAuth 2.0 token response (RFC 6749 §5.1) for every grant.Token type (RFC 6749 §7.1): 'Bearer' on every grant, except 'DPoP' (RFC 9449 §5) for an administrative workload's client_credentials grant sent with a DPoP proof, whose token is bound to the proof key