SAP Knowledge Base Article - Preview

3796412 - CDC OIDC Outbound Federation — Choosing the Correct JWT/Token Approach and M2M Limitations

Symptom

which JWT mechanism to use when implementing CDC as an OIDC Provider (outbound federation):

  • Option 1: fidm.oidc.op.createRP + OIDC OP token endpoint + JWKS validation
  • Option 2: accounts.getJWT + accounts.getJWTPublicKey

A secondary variant arises when the customer's use case is device/application registration with no user identity in the token — a machine-to-machine (M2M) flow.


Read more...

Environment

Environment

FieldValue
ProductSAP Customer Data Cloud (Gigya)
Feature AreaOIDC Outbound Federation, JWT APIs
Affected APIsfidm.oidc.op.createRP, accounts.getJWT, accounts.getJWTPublicKey
DatacentersAll (us1, eu1, au1, cn1, ru1)

Product

SAP Customer Data Cloud all versions

Keywords

  • OIDC outbound federation
  • OIDC OP
  • OpenID Connect Provider
  • fidm.oidc.op.createRP
  • JWT validation
  • JWKS endpoint
, KBA , CEC-PRO-API , Core REST API & Server SDKs (JWT / PHP / Java) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.