Skip to main content

Introduction

JSON Web Signature (JWS) represents content secured with digital signatures or Message Authentication Codes (MACs) using JSON-based data structures. JWS are used to exchange authentication and authorization information and identities between various systems supporting OAuth 2.0. Authorization server issues JWS after successful identity verification, and it is validated by ILM Signing that acts as a resource server. JSON-based data structure contains claims to pass information about user and additional information that is required for authorization. The claims are digitally signed and can be verified with the public key and certificate of the resource server. The Extended JWS Authorizer allows having the authorization server separate from the signing application and provides eIDAS compliant authentication and authorization to signing and validation workers using multi-factor authentication (MFA).

info

The Extended JWS token provides authorization of the signing request and propagates valid claims information into the signing process that can use them in order to perform and configure some specific attributes of certificates.

Use case example​

There are several authorization servers available compliant to JWS specification according RFC 7515 and this implementation has been tested according that. The following use case example outlines authenticating authorization server to obtain JWS, then used it in the request sent from the client to the signing component. The client in the following overview could, for example, be an mobile application communicating with a document management system or remote signing backend.

Authentication and authorization flow​

Authentication walkthrough

Extended JWS

JWS
  • Users and applications
    Service consumer

    Request a service and authenticate.

  • Signing backend
    Client

    Coordinates authentication and the service request.

  • Authorization server
    Token issuer

    Authenticates the user and issues a JWS.

  • Signing component
    Resource server

    Validates the JWS and its claims, then signs or validates.

Trust setup

The worker in the signing component is configured to trust the public key of the authorization server. Authorization rules matching claims of the JWS are also configured.

Runtime request

Runtime request · Step 2 of 11

Request signing or validation

Users and applications → Signing backend

The user requests signing or validation services from the signing backend.

Select a step to follow its path. Read every step below.

Complete step reference

  1. Distribute the authorization server public keyTrust setup

    Authorization server → Signing component

    The worker in the signing component is configured to trust the public key of the authorization server. Authorization rules matching claims of the JWS are also configured.

  2. Request signing or validation

    Users and applications → Signing backend

    The user requests signing or validation services from the signing backend.

  3. Request authentication

    Signing backend → Authorization server

    The signing backend requests authentication from the authorization server, providing details about the user’s authentication domain.

  4. Provide authentication context

    Authorization server → Signing backend

    The authorization server provides the authentication context for the user to the signing backend.

  5. Forward authentication context

    Signing backend → Users and applications

    The signing backend forwards the authentication context to the user. The user uses this context to authenticate to the authorization server’s service.

  6. Authenticate the user

    Users and applications → Authorization server

    The user authenticates using credentials with the authorization server. When MFA is enabled, there may be multiple rounds in the authentication process.

  7. Produce JWS

    Authorization server → Users and applications

    Upon successful authentication, the user receives the JWS from the authorization server.

  8. Forward JWS

    Users and applications → Signing backend

    The user forwards the JWS to the signing backend as proof of successful authentication and authorization for the signing or validation request.

  9. Submit signing or validation request

    Signing backend → Signing component

    The signing backend submits the request with the JWS to the signing component.

  10. Perform the task and provide a response

    Signing component → Signing backend

    The signing component validates the JWS and its claims, performs the operation and provides a response to the signing backend.

  11. Return the response

    Signing backend → Users and applications

    The signing backend forwards the signing component’s response to the user.

Step 1 establishes trust. Steps 2–11 show authentication, authorization and the signing or validation request. Highlighted cards identify the participants in the selected step.