SAP Customer Identity and Access Management (SAP CIAM), formerly Gigya and SAP Customer Data Cloud, is a multi-tenant SaaS customer identity platform on SAP Business Technology Platform. It covers registration and login (password, social, passwordless with FIDO passkeys, phone, email OTP, and magic links), two-factor and risk-based authentication, consent and preference management, and B2B contact and partner management. SAP CIAM can act as an OpenID Connect provider (authorization code, implicit, hybrid, client credentials, device, and token exchange flows) and relying party, and as a SAML identity provider and service provider. Sites are hosted in United States, European Union, Australian, or Chinese data centers, with global site groups for cross-region SSO. Pricing is subscription-based per block of 10,000 monthly active users, with optional enhanced security and consent add-ons.
Fonctionnalités
Si vous souhaitez comparer les fonctionnalités OpenID Connect de différents fournisseurs, consultez le benchmark des fournisseurs OpenID Connect.
Vous cherchez les fonctionnalités (C)IAM de SAP CIAM comme MFA, SSO et gestion des utilisateurs ? Voir SAP CIAM sur le benchmark des fournisseurs d'identité (C)IAM.
Foire aux questions
SAP CIAM prend-il en charge Authorization Code grant type ?
SAP CIAM prend en charge Authorization Code grant type. The OIDC provider supports the authorization code flow, along with implicit and hybrid flows using the code, token, and id_token response types. En savoir plus
SAP CIAM prend-il en charge Refresh Token grant type ?
SAP CIAM prend en charge Refresh Token grant type. Refresh tokens are issued (for example in the device flow) and can be used to obtain a new access token, ID token, and refresh token; they keep the permissions of the original token. En savoir plus
SAP CIAM prend-il en charge Client Credentials grant type ?
SAP CIAM prend en charge Client Credentials grant type. Requests go to the token endpoint with grant_type, client_id, and client_secret; only an access token is returned, without refresh or ID tokens. En savoir plus
SAP CIAM prend-il en charge Implicit grant type ?
SAP CIAM prend en charge Implicit grant type. The implicit flow is supported with the id_token and token response types. En savoir plus
SAP CIAM prend-il en charge Token Exchange grant type ?
SAP CIAM prend en charge Token Exchange grant type. RFC 8693 token exchange can reduce or extend the permission scopes of an existing token, and supports an actor_token to add an act claim for single-level delegation. En savoir plus
SAP CIAM prend-il en charge Device Authorization Grant grant type ?
SAP CIAM prend en charge Device Authorization Grant grant type. The OIDC device flow (RFC 8628) is supported for all relying parties, with configurable code expiry, polling interval, and verification URI. En savoir plus
SAP CIAM prend-il en charge Authorization Endpoint endpoint ?
SAP CIAM prend en charge Authorization Endpoint endpoint. The OIDC provider serves its endpoints under https://fidm.<data-center>/oidc/op/v1.0/<API key>/. En savoir plus
SAP CIAM prend-il en charge Token Endpoint endpoint ?
SAP CIAM prend en charge Token Endpoint endpoint. The token endpoint is available at https://fidm.<data-center>/oidc/op/v1.0/<API key>/token. En savoir plus
SAP CIAM prend-il en charge UserInfo Endpoint endpoint ?
SAP CIAM prend en charge UserInfo Endpoint endpoint. Access tokens can be used at the userinfo endpoint as specified in the OpenID Connect specification. En savoir plus
SAP CIAM prend-il en charge Device Authorization Endpoint endpoint ?
SAP CIAM prend en charge Device Authorization Endpoint endpoint. The device_authorization endpoint is listed in the OP metadata. En savoir plus
SAP CIAM prend-il en charge OpenID Connect Discovery Endpoint endpoint ?
SAP CIAM prend en charge OpenID Connect Discovery Endpoint endpoint. Metadata is published at the .well-known/openid-configuration URL of the provider, and can also be viewed from the console. En savoir plus
SAP CIAM prend-il en charge client_secret_basic méthode d'authentification du token endpoint ?
SAP CIAM prend en charge client_secret_basic méthode d'authentification du token endpoint. Confidential clients authenticate to the token endpoint with Basic authorization, as in the token exchange flow. En savoir plus
SAP CIAM prend-il en charge client_secret_post méthode d'authentification du token endpoint ?
SAP CIAM prend en charge client_secret_post méthode d'authentification du token endpoint. The client credentials example sends client_id and client_secret in the token request body. En savoir plus
SAP CIAM prend-il en charge RP-initiated Logout fonctionnalité ?
SAP CIAM prend en charge RP-initiated Logout fonctionnalité. The provider exposes an end_session_endpoint that accepts id_token_hint and a trusted post logout redirect URI, letting the user sign out of the RP only or of the OP and all connected RPs. En savoir plus
Comparer avec d'autres fournisseurs
Remarque : Les données actuelles sont basées sur la documentation/l'expérience des fournisseurs et peuvent ne pas être exactes à 100 %.