Page History

...

Data mappings for data retrieved as claims of the JWT token work similar to the data mappings of the resource uri described above.

Since eSignAnyWhere 21.40, the field value can reference to hierarchical data structures within the JWT/JSON. Therefore use the dot (.) separator to address different levels.

Example:

Assuming the JSON structure is:

{
  "person_data" : {
    "given_name" : "John",
    "family_name" : "Doe" 
  }
}

Then, the given name can be accessed as

person_data:given_name

In case the JWT contains claims with a name that contains the dot (.) or colon (:), ensure to wrap the identifier within ['..']

Assuming the JSON structure is:

{
  "given_name" : "John",
  "family_name" : "Doe", 
  "urn:pvpgvat:oidc.bpk" : "1234567+"
}

Then, the bpk value can be accessed as

['urn:pvpgvat:oidc.bpk']

Note that eSignAnyWhere up to (including) version 21.31 does NOT support addressing elements within complex data structures in the JWT. Therefore, in these releases you have to use the identifier of a flat structure, without ['..']

Sending an Envelope with OAuth 2.0 / OIDC authentication

...