• It is now allowed to have multiple identity providers in use for a single recipient. Please note that this is only allowed if the providers have a completely identical set of update rules.
• Nested JSON in JWT are now also accepted by the OAuth2 checks.
• The separation is now more visible between the OAuth2 Authorization Providers and the OAuth2 Identity Providers. In detail:
  • In the OAuth2 Authorization Providers list you will now only find OAuth2 providers with just validation rules
  • In the OAuth2 Identity Providers list you will now only find OAuth2 providers with at least one update rule
• Stabilization of OAuth2
  
  • Stabilization of the OAuth2 provider authentication via api.
  • The template which was created from an envelope with OAuth2 configuration now also includes the OAuth2 configuration from the original envelope.

For more information about the OAuth2 configuration please have a look at the OAuth2 guide and for samples please also see the OAuth2 sample guide.

• Additionally to the hash of the finished envelope you can now also find the hash of the initial document in the audit trail
• The audit trail now also contains the eSAW version information
• The audit trail sealing now considers PAdES signature level.
• Stabilization of the audit trail
  • You can now find information about the OAuth2 authentication in the audit trail.
  • Timezone formatting issue fixed.
  • Chinese characters are now supported to be displayed correctly in the audit trail.

For more information about the audit trail please see the electronic signature guide.

There will no longer appear exceptions if a document is uploaded with predefined syntax which do not meet the requirements. Instead you will get the following warning:

You can either proceed with the uploaded document or cancel the upload.

For more information about the field markup handling in general please see the following guide: Field markup