;
};
アイデンティティ用語に不慣れな方から経験豊富な開発者までを対象に、アイデンティティ関連の用語集をまとめました。アイデンティティ用語に関する混乱の解消に役立てば幸いです。
Application Settings.",
},
{
term: "Client Secret",
description:
"Secret used by a client (application) to authenticate with the Authorization Server; it should be known to only the client and the Authorization Server and must be sufficiently random to not be guessable.",
},
{
term: "Confidential Client",
description:
"According to the OAuth 2.0 protocol, clients (applications) can be classified as either confidential or public. Confidential clients can hold credentials securely and require a trusted backend server to do so. They can use grant types that require authentication by specifying their client ID and secret when calling the token endpoint.",
},
{
term: "Confused Deputy",
description:
"Situation in which an attacker tricks a client or service into performing an action on their behalf.",
},
{
term: "Connection",
description:
"Relationship between Auth0 and the sources of users for your applications. Examples include identity providers, passwordless authentication methods, or user databases.",
},
{
term: "Consumption Device",
description:
"The device that helps the user consume a service in the Client-Initiated Backchannel Authentication Flow.",
},
{
term: "Custom Domain",
description: "Third-party domain with a specialized, or vanity, name. Also known as a CNAME.",
},
{
term: "Deprecation",
description:
"Product release stage indicating that the referenced feature or behavior is not supported for new subscribers, is not actively being enhanced, and is being only minimally maintained.",
},
{
term: "Digital Identity",
description:
"Set of attributes that define a particular user in the context of a function delivered by a particular application.",
},
{
term: "Digital Signature",
description:
"Encrypted string that protects bits in a token from tampering. If the bits are changed or tampered with, the signature will no longer be able to be verified and it will be rejected.",
},
{
term: "Directory",
description:
"Centralized repository of users (the most well-known of which is Active Directory) which centralizes credentials and attributes and makes it unnecessary for each application to have their own local identity setup.",
},
{
term: "Early Access",
description:
"Product release stage during which the referenced feature or behavior is provided to a limited number of subscribers or customer development partners (CDPs) to test and provide feedback.",
},
{
term: "End of Life",
description:
"Product release stage indicating that the referenced feature or behavior is removed from the platform. Continued use will likely result in errors.",
},
{
term: "End of Life Date",
description:
"Date when access to a feature or behavior is removed from the platform. End Of Life Dates can vary between different plan types.",
},
{
term: "Fine-grained Authorization (FGA)",
description:
"Auth0’s SaaS product that gives individual users access to specific objects or resources within your application.",
},
{
term: "Flow",
description:
"Processes that can be extended using Actions. Each Flow is made up of one or more Triggers and represents the logical pipeline through which information moves during a single point in the Auth0 journey.",
},
{
term: "General Availability",
description:
"Product release stage during which the referenced feature or behavior is fully functional and available to all subscribers for production use.",
},
{
term: "Group",
description:
"Set of one or more users. In the Auth0 Authorization Extension, use groups to grant access to many users at a time.",
},
{
term: "ID Token",
description:
"Credential meant for the client itself, rather than for accessing a resource. It has a fixed format that clients can parse and validate.",
},
{
term: "Identity Provider (IdP)",
description:
"Service that stores and manages digital identities. Auth0 supports trusted social, enterprise, and legal identity providers.",
},
{
term: "JSON Web Token (JWT)",
description:
"Open, industry standard RFC 7519 method for representing claims securely between two parties. At Auth0, ID Tokens are always returned in JWT format, and Access Tokens are often in JWT format.",
},
{
term: "Localization",
description: "Ability to render the New Universal Login experience into a supported language.",
},
{
term: "Lock",
description:
"Auth0's UI widget for authenticating users. It is ready to go as-is and is the default face of the Classic Universal Login experience.",
},
{
term: "Management API",
description: "Auth0's API to manage Auth0 services and perform administrative tasks programatically.",
},
{
term: "Metadata",
description:
"Information users can update, such as preferences or profile settings. Metadata is added to ID tokens and can be stored in user profiles.",
},
{
term: "Migration",
description:
"Process by which a customer moves away from a particular feature or behavior. Migrations should occur during the Deprecation stage.",
},
{
term: "Multi-factor authentication (MFA)",
description:
"Authentication process that considers multiple factors. Typically the first factor is username/password, and the second is a code or link via email/SMS, or OTP via an app.",
},
{
term: "Nonce",
description:
"Arbitrary (often random or pseudo-random) number issued in an authentication protocol that can be used to help detect and mitigate replay attacks.",
},
{
term: "OAuth 2.0",
description:
"Authorization framework that defines authorization protocols and workflows. OAuth 2.0 defines roles, authorization grants, authorization requests and responses, and token handling.",
},
{
term: "OpenID",
description:
"Open standard for authentication that allows applications to verify users are who they say they are without needing to collect or store login information.",
},
{
term: "Organizations",
description:
"Auth0 product that allows B2B customers to categorize end-users and define specific roles, login experience, and access to resources.",
},
{
term: "Passwordless",
description:
"Form of authentication where the first factor is not a password. Instead, it could be a one-time password received by email or SMS, a push notification, or a biometric sensor.",
},
{
term: "Perimeter",
description:
"Set of boundaries that encompass a directory, all of its users, and all of the applications which use the directory.",
},
{
term: "Product Release Stages",
description: "Phases that describe how Auth0 stages, releases, and retires product functionality.",
},
{
term: "Public Client",
description:
"According to the OAuth 2.0 protocol, clients can be confidential or public. Public clients cannot hold credentials securely, so should only use grant types that do not require the use of their client secret.",
},
{
term: "Raw Credential",
description:
"Shared secret or set of information that is agreed upon between the user and the resource that allow the resource to verify the identity of a user.",
},
{
term: "Refresh Token",
description:
"Special kind of token that can be used to obtain a renewed Access Token. It is useful for renewing expiring Access Tokens without forcing the user to log in again.",
},
{
term: "Refresh Token Rotation",
description:
"Strategy of frequently replacing refresh tokens to minimize vulnerability. Each exchange also returns a new refresh token.",
},
{
term: "Relying Party",
description:
"Entity (such as a service or application) that depends on a third-party identity provider to authenticate a user.",
},
{
term: "Resource Owner",
description: "Entity (such as a user or application) capable of granting access to a protected resource.",
},
{
term: "Resource Server",
description:
"Server hosting protected resources. Resource servers accept and respond to protected resource requests.",
},
{
term: "Role",
description:
"Aspect of a user’s identity assigned to the user to indicate the level of access they should have to the system.",
},
{
term: "Scope",
description:
"Mechanism that defines the specific actions applications can be allowed to do or information they can request on a user’s behalf.",
},
{
term: "Security Assertion Markup Language (SAML)",
description:
"XML-based standardized protocol by which two parties can exchange authentication information without the use of a password.",
},
{
term: "Security Token",
description: "Digitally-signed artifact used to prove that the user was successfully authenticated.",
},
{
term: "Session Cookie",
description:
"Entity emitted by middleware after it establishes that the token it is receiving is signed, valid, and comes from a trusted source.",
},
{
term: "Shadow Account",
description:
"Difficult-to-sustain practice of manually provisioning a user from a local directory separately in a remote directory when they need access to remote applications.",
},
{
term: "Signing Algorithm",
description:
"Hashing algorithm used to digitally sign tokens to ensure the token has not been tampered with.",
},
{
term: "Single Sign-On (SSO)",
description:
"Service that, after a user logs into one application, automatically logs them into other applications as well. Single Logout works similarly in reverse.",
},
{
term: "Subscription",
description: "Agreement that defines the features and quotas available for each of your tenants.",
},
{
term: "Suspicious IP Throttling",
description:
"Form of attack protection that protects your tenant against suspicious logins targeting too many accounts from a single IP address.",
},
{
term: "Tenant",
description:
"A logically-isolated group of users who share common access with specific privileges to a single software instance.",
},
{
term: "Token Endpoint",
description: "Endpoint on the Authorization Server that is used to programmatically request tokens.",
},
{
term: "Trigger",
description:
"Event that automatically invokes an Action when a specific operation, such as a user logging in, occurs at runtime.",
},
{
term: "Trust",
description:
"A resource trusts an identity provider or authority when that resource is willing to believe what the authority says about its users.",
},
{
term: "Universal Login",
description:
"Auth0’s implementation of the authentication flow, which is the key feature of an Authorization Server.",
},
{
term: "Web Service Federation (WS-Fed)",
description:
"Protocol for managing user identities between systems, domains, and identity providers with established trust using WS-Trust. Mainly used for Microsoft products.",
},
]}
/>