# Specific technical standards

Specific implementations of OAuth 2.0 and OpenID Connect 1.0 are used to facilitate an ecosystem in which parties can interact with previously unknown parties. Pre-registration, therefore, is not a prerequisite, and this requires alterations to the official standards. Also, for the authentication of parties within an iSHARE (data spaces/network) context, it uses PKI and digital certificates relating to all participating parties.

### Technical standards used in iSHARE and configuration aspects <a href="#generictechnicalstandards-technicalstandardsusedinishareandconfigurationaspects" id="generictechnicalstandards-technicalstandardsusedinishareandconfigurationaspects"></a>

The iSHARE Trust Framework also prescribes various general interface specifications described in the corresponding topic pages. More information on the technical standards can be found in the [Knowledge Base.](https://app.gitbook.com/s/fKDJDsmddUm6vG90kdzt/apply-ishare/technical-standards)

<table><thead><tr><th>Technical standard</th><th width="264">Character</th><th>Description</th></tr></thead><tbody><tr><td><a href="specific-technical-standards/pki">PKI</a></td><td>Architectural principle</td><td>For interoperability on a European scale, all trusted roots under the eIDAS regulation will be trusted within data spaces/iSHARE network.</td></tr><tr><td><a href="specific-technical-standards/oauth-2.0">OAuth 2.0</a></td><td>Open standard for authentication</td><td>The OAuth 2.0 subpage describes the generic Authentication flow.</td></tr><tr><td><a href="specific-technical-standards/openid-connect-1.0">OpenID Connect 1.0</a></td><td>Open standard for authentication of humans</td><td>Functions as an additional layer on top of the OAuth 2.0 protocol.</td></tr><tr><td><a href="specific-technical-standards/http-response-codes">HTTP(S)</a></td><td>Communication protocol</td><td>An overview of relevant iSHARE HTTP response codes can be found here.</td></tr><tr><td><a href="specific-technical-standards/tls">TLS</a></td><td>Cryptographic protocol</td><td>Within data spaces/iSHARE network, TLS 1.2 MUST be used for securing all HTTP communications.</td></tr><tr><td><a href="specific-technical-standards/json-web-token-jwt">JSON Web Token (JWT)</a></td><td>Open standard for definition of access tokens</td><td>A JSON Web Token (JWT) is used in data spaces/ iSHARE network when non-repudiation between parties is required.</td></tr><tr><td><a href="specific-technical-standards/xacml-3.0">XACML 3.0</a></td><td>Access control policy language</td><td>Within data spaces/ iSHARE network, a JSON port of XACML 3.0 is used to enable parties to communicate delegation evidence.</td></tr><tr><td><a href="specific-technical-standards/caching">Caching</a></td><td>Temporary data storage</td><td>In iSHARE, caching is used to optimise API interactions by reducing latency and load on services while ensuring data consistency and security.</td></tr><tr><td><a href="#did">DID</a></td><td>Identifier</td><td>A Decentralised Identifier (DID) is assigned to legal entities during onboarding in compliance with the iSHARE framework using the did:ishare method.</td></tr><tr><td><a href="#utc">UTC</a></td><td>Time Format</td><td>All dates and times in iSHARE must be communicated in UTC and formatted as Unix timestamps.</td></tr><tr><td><a href="#x.509">X.509</a></td><td>Cryptographic protocol</td><td>In iSHARE, X.509 certificates are used for secure identity verification, authentication, and encryption</td></tr><tr><td><a href="specific-technical-standards/verifiable-credentials-vc">Verifiable Credentials (VC)</a></td><td>Open standard for verifiable digital credentials</td><td>Verifiable Credentials, as defined by the W3C Verifiable Credentials Data Model 2.0, enable participants to issue, present, and verify digitally signed credentials. They provide cryptographic assurance of identity and authorisation, support selective disclosure for privacy, and ensure interoperability with frameworks such as eIDAS 2.0 and EBSI.</td></tr></tbody></table>