5.3. Relying Party Solution¶
A Relying Party, as an Organizational entity relying upon IT-Wallet, provides Technical Solutions (Relying Party Solution) that could combine software, hardware, services, settings, and configurations, including Relying Party Instances for User authentication and Digital Credential verification.
In order to implement and provide Technical Solutions, a Relying Party could take advantage of services provided by an Intermediary Entity. A Relying Party Intermediary is an Organization Entity that may act on behalf of the Relying Party offering services to it, making the Relying Party able to connect to Wallet Instance and authenticate Users and verify User's Digital Credentials.
A Relying Party provides at least one of the following components:
Relying Party Backend: It handles Relying Party Instances registration and the relative Certificate management. It obtains X.509 Certificate according to the The Infrastructure of Trust. It SHOULD also provide a X.509 Certificate to its Relying Party Instances. It also may implement additional web services and business logic for its own purposes and use cases.
Relying Party Instance: It is a frontend provided to Users in order to access Relying Party Services, and it may be provided as:
Web Client.
Mobile Application.
The following diagram depicts the Relying Party Solution High Level Architecture.
Relying Party Solution Table of Contents
- 5.3.1. Relying Party Solution Requirements
- 5.3.2. Relying Party Instance
- 5.3.3. Mobile Relying Party Instance
- 5.3.4. Web Relying Party Instance
- 5.3.5. Relying Party Entity Configuration
- 5.3.6. Relying Party Metadata