33 docs tagged with "passwordless"

What is Account Linking?

cidaas Multifactor or Two-factor Authentication offers an additional layer of security for end-users. It provides the user with the means of verifying their identity through a second channel to eliminate any doubt about the legitimacy of an access request. MFA is available for password-based (email/username/mobile number and password) and passwordless authentication flows.

The AMR value is used in authentication protocols. It refers to a value that indicates the methods or mechanisms used to authenticate a user during an authentication process.

The Authorization Code Flow is one of the OAuth2 flows that was designed to securely authenticate a user and issue an access token. The basic concept behind the authorization code flow is that a code is issued after identification and this must be exchanged for an access token.

Authenticate with a backup code in cidaas — a set of ten single-use 8-digit codes for signing in when no other method is available.

cidaas can act as an OpenID Connect (OIDC) Identity Provider (IdP) for external applications.

Communication providers in cidaas — send notifications for user creation, password reset or MFA using built-in or custom providers.

This flow can be reimplemented and integrated into their own pages and platform directly using the cidaas APIs

The Device Code Flow (officially: OAuth 2.0 Device Authorization Grant) is an OAuth 2.0 grant type designed for devices that don't have a browser or have limited input capabilities, such as smart TVs, gaming consoles, CLI tools, or IoT devices. It enables users to authorize these devices to access their resources by authenticating on a separate device (e.g., smartphone or computer) with a full browser.

Authenticate with an email or SMS one-time password in cidaas — the flow, the APIs, and how the code is delivered and verified.

Authenticate with FIDO2 in cidaas — let users sign in with FIDO2 compliant Keys, or via passkeys or platform authenticators.

Enrol FIDO2 in cidaas — register a security key or passkey / platform authenticator as a verification method, with the flow and APIs.

Group selection in cidaas — let users pick the group or context they log in with, enforce the selection, or auto-select one using the group_hint parameter.

Integrating cidaas with your business is simple and can be done for the Admin and User Service portals.

Authenticate with a magic link in cidaas — a passwordless sign-in link sent to the user, including the APIs for the login flow.

The cidaas MFA and suggest verification hosted page explained — guide users to configure additional verification methods after they sign in.

Passwordless authentication in cidaas — FIDO2 passkeys, TOTP, magic links, push, OTP, and biometric verification methods.

The password change process is a vital security feature that allows users to update their login credentials. This process ensures that users can maintain control over their account security by regularly updating their passwords or immediately changing them if they suspect any unauthorized access. Including a password change option on the user profile page enhances security, provides convenience, and empowers users to proactively manage their account safety. By enabling easy access to this feature, you promote a safer and more user-friendly environment.

To set a password there are multiple use cases for how to use the different APIs and when to use which API.

Authenticate with a pattern in cidaas — the user traces a pattern that is verified as a passwordless factor, with the flow and APIs.

Enrol pattern verification in cidaas — register the pattern as a verification method, in the cidaas Authenticator or your own app.

The Authorization Code Flow with PKCE (Proof Key for Code Exchange) is an extension of the Authorization Code Flow. It is specifically designed to authenticate native or mobile application users, but is recommended for all scenarios where user authentication is required, especially for public clients that cannot securely store a client_secret.

This document describes a 3-step authentication verification flow using OpenAPI specifications.

cidaas Public API guides — authentication, OAuth 2.0, MFA, passwordless, user management, and identity verification.

Authenticate with Smart Push in cidaas — the user picks the matching number from four shown in the mobile app to confirm the login.

Enrol push verification in cidaas — register a device for Smart Push, in the cidaas Authenticator or an app your users already have.

On-the-fly enrolment in cidaas — propose additional verification methods to users right after authentication for a smooth transition to modern authentication.

Authenticate with TOTP in cidaas — verify the time-based one-time password from an authenticator app as a passwordless or MFA factor.

Enrol TOTP in cidaas — register a time-based one-time password generator in an authenticator app as a verification method.

Authenticate with Touch ID in cidaas — use the phone's device biometrics as a passwordless or MFA factor, with the flow and APIs.

Enrol Touch ID or fingerprint verification in cidaas — register the device biometric as a verification method, with the flow and APIs.

Authentication is one of the major parts of security; it is the process by which we recognize the authenticity of the entity. Since cidaas offers a variety of authentication options, such as pattern, face, and many more, we take the utmost care about the originality of the identity.

Passwordless authentication of cidaas (Touch ID, Face Recognition, etc.) will help you seamlessly log in to your desired application without worrying about the authenticity of the actor, which will in turn save you time with our quick, secure, and dependable service.