Skip to content

eu-digital-identity-wallet/eudi-lib-jvm-rqes-csc-kt

EUDI rQES CSC library

âť— Important! Before you proceed, please read the EUDI Wallet Reference Implementation project description

License

Table of contents

Overview

This is a Kotlin library, targeting JVM, that supports the Cloud Signature Consortium API (version 2) protocol.

Implemented features

The library supports the following remote service API endpoints:

Method Support
info âś…
auth/login ❌
auth/revoke ❌
credentials/list âś…
credentials/info âś…
credentials/authorize ❌
credentials/authorizeCheck ❌
credentials/getChallenge ❌
credentials/extendTransaction ❌
signatures/signHash âś…
signatures/signDoc ❌
signatures/signPolling ❌
signatures/timestamp ❌

Additionally, the library supports the following authorization methods:

OAuth 2.0 Explicit
Service ✅ ❌
Credential ✅ ❌

âť—Important note on hash calculation and signature embedding

This library is exposing methods for calculating a document's digest and for embedding a signature to the document. However, this functionality is not implemented in the library itself, but is delegated to an external component.
This component is not part of the library and must be provided by the library consumer. Alternative, the library consumer can implement the hash calculation and signature embedding logic in their own application.

In future versions of the library, this functionality may be implemented directly in the library.

Interactions between the library, the caller and the RSSP

Legend

Symbol Description
Caller The application that is using the library to interact with the RSSP
Lib This library
RSSP The Remote Signing Service Provider
Remote SCA A remote component that is responsible for hash calculation and signature embedding

Get RSSP information

sequenceDiagram
    autonumber
    Caller ->> Library: Request RSSP information
    activate Library
    Note left of Library: Inputs: <br/>1) the RSSP URL
    Library ->> RSSP: call /info endpoint<br/>
    activate RSSP
    Note left of RSSP: (Check CSC API section 11.1)
    RSSP ->> Library: Return info
    deactivate RSSP
    Library ->> Caller: Return info
    deactivate Library
    Note left of Library: Outputs: <br/>1) the RSSP information
Loading

Service authorization

Authorization Code flow

sequenceDiagram
    autonumber
    Caller ->> Library: Initiate service authorization
    activate Library
    Library ->> Caller: return authorization URL
    deactivate Library
    Note over Caller, Library: At this point the Caller is responsible<br/>to open the authorization URL<br/> in a browser. <br/>After the authorization is complete, <br/>the Caller must obtain<br/> the authorization code
    Caller ->> Library: provide authorization code
    activate Library
    Library ->> Authorization Server: Use token endpoint to exchange<br/> auth code for access token
    activate Authorization Server
    Authorization Server ->> Library: return access token
    deactivate Authorization Server
    Library ->> Caller: return access token
    deactivate Library
Loading

Authorization Code flow with Pushed Authorization Requests (PAR)

sequenceDiagram
    autonumber
    Caller ->> Library: Initiate service authorization
    activate Library
    Library ->> Authorization Server: push authorization request
    activate Authorization Server
    Authorization Server ->> Library: return request uri
    deactivate Authorization Server
    Library ->> Caller: return authorization URL
    deactivate Library
    Note over Caller, Library: At this point the Caller is responsible<br/>to open the authorization URL<br/> in a browser. <br/>After the authorization is complete, <br/>the Caller must obtain<br/> the authorization code
    Caller ->> Library: provide authorization code
    activate Library
    Library ->> Authorization Server: Use token endpoint to exchange<br/> auth code for access token
    activate Authorization Server
    Authorization Server ->> Library: return access token
    deactivate Authorization Server
    Library ->> Caller: return access token
    deactivate Library
Loading

Credentials list

sequenceDiagram
    autonumber
    Caller ->> Library: Request list of credentials
    activate Library
    Note left of Library: Inputs: <br/>1) the service access token
    Library ->> RSSP: call /credentials/list endpoint<br/>
    activate RSSP
    Note left of RSSP: (Check CSC API section 11.4)
    RSSP ->> Library: Return credentials list
    deactivate RSSP
    Library ->> Caller: Return credentials list
    deactivate Library
Loading

Credentials info

sequenceDiagram
    autonumber
    Caller ->> Library: Request information on credential
    activate Library
    Note left of Library: Inputs: <br/>1) the service access token
    Library ->> RSSP: call /credentials/info endpoint<br/>
    activate RSSP
    Note left of RSSP: (Check CSC API section 11.4)
    RSSP ->> Library: Return credential information
    deactivate RSSP
    Library ->> Caller: Return credential information
    deactivate Library
Loading

Credential Authorization flow

sequenceDiagram
    autonumber
    Caller ->> Library: Initiate credential authorization
    Note left of Library: Inputs: <br/>1) the credential<br/>2) the document to be signed<br/>3) the service access token
    activate Library
    Library ->> Library: Calculate document hash
    Library ->> Caller: return prepared authorization URL
    deactivate Library
    Note over Caller, Library: At this the Caller is responsible<br/>to open the authorization URL<br/> in a browser. <br/>After the authorization is complete, <br/>the Caller must obtain<br/> the authorization code
    Caller ->> Library: provide authorization code
    activate Library
    Library ->> Authorization Server: Use token endpoint to exchange<br/> auth code for access token
    activate Authorization Server
    Authorization Server ->> Library: return access token
    deactivate Authorization Server
    Library ->> Caller: return access token
    deactivate Library
Loading

Credential Authorization flow with remote SCA

sequenceDiagram
    autonumber
    Caller ->> Library: Initiate credential authorization
    activate Library
    Note left of Library: Inputs: <br/>1) the credential<br/>2) the document to be signed<br/>3) the service access token
    Library ->> Remote SCA: request hash calculation
    activate Remote SCA
    Remote SCA ->> Library: return hash
    deactivate Remote SCA
    Library ->> Caller: return prepared authorization URL
    deactivate Library
    Note over Caller, Library: At this the Caller is responsible<br/>to open the authorization URL<br/> in a browser. <br/>After the authorization is complete, <br/>the Caller must obtain<br/> the authorization code
    Caller ->> Library: provide authorization code
    activate Library
    Library ->> Authorization Server: Use token endpoint to exchange<br/> auth code for access token
    activate Authorization Server
    Authorization Server ->> Library: return access token
    deactivate Authorization Server
    Library ->> Caller: return access token
    deactivate Library
Loading

Hash signing

sequenceDiagram
    autonumber
    Caller ->> Library: request signing
    activate Library
    Note left of Library: Inputs: <br/>1) the credential<br/>2) the document to be signed<br/>3) the credential access token
    Library ->> RSSP: /signHash
    activate RSSP
    Note left of RSSP: (check CSC API section 11.10)
    RSSP ->> Library: return digital signature
    deactivate RSSP
    Library ->> Caller: return digital signature
    deactivate Library
Loading

Disclaimer

The released software is an initial development release version:

  • The initial development release is an early endeavor reflecting the efforts of a short timeboxed period, and by no means can be considered as the final product.
  • The initial development release may be changed substantially over time, might introduce new features but also may change or remove existing ones, potentially breaking compatibility with your existing code.
  • The initial development release is limited in functional scope.
  • The initial development release may contain errors or design flaws and other problems that could cause system or other failures and data loss.
  • The initial development release has reduced security, privacy, availability, and reliability standards relative to future releases. This could make the software slower, less reliable, or more vulnerable to attacks than mature software.
  • The initial development release is not yet comprehensively documented.
  • Users of the software must perform sufficient engineering and additional testing in order to properly evaluate their application and determine whether any of the open-sourced components is suitable for use in that application.
  • We strongly recommend to not put this version of the software into production use.
  • Only the latest version of the software will be supported

How to contribute

We welcome contributions to this project. To ensure that the process is smooth for everyone involved, follow the guidelines found in CONTRIBUTING.md.

License

Third-party component licenses

License details

Copyright (c) 2024 European Commission

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

About

Implementation of CSC protocol (wallet's role) in Kotlin

Topics

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Packages

No packages published

Contributors 3

  •  
  •  
  •  

Languages