Skip to main content

🏷️ Share: Secure Information Exchange

A feature designed to simplify the process of exchanging information securely. It implements advanced encryption using JSON Web Encryption (JWE) to ensure that transferred data is protected from unauthorized access. This feature allows users to fill out forms seamlessly, making cross-platform interactions more efficient and easier.

How can INApas Share improve your digital services?​

High Security with JSON Web Encryption (JWE):​

  • Data is encrypted using the JWE standard, ensuring the security of information sent between users and the platform.

Based on OIDC 1.0 and OAuth 2.0 Standards:

  • Follows the OpenID Connect (OIDC) version 1.0 and OAuth 2.0 protocols, two globally recognized standards for authentication and authorization.

Automated Form Filling and Seamless Data Exchange:

  • Enables users to automated form filling with seamless integration to multiple platforms, reducing repetitive manual input.

How INApas Share Works​

1️⃣ Integration with Authentication Flows

  • INApas Share connects with user authentication systems that use OIDC 1.0 and OAuth 2.0.

2️⃣ Automated Form Filling with Verified Data

  • Enables automatic form filling using verified data, reducing the need for manual input.

3️⃣ Encryption of All Data Transfers

  • Any data transferred is encrypted using JSON Web Encryption (JWE) to maintain confidentiality and security.

4️⃣ Explicit User Consent

  • Before data is shared, users must provide explicit consent, ensuring transparency in the use of personal information.

5️⃣ Efficient Data Exchange between Platforms

  • Enables fast and secure data exchange across multiple digital services without technical barriers.

Main Foundations: Regulatory Compliance and Data Security

Compliance with the Personal Data Protection Law (PDP Law)​

  • INAPAS “Sharing” is designed with the principles of personal data protection in mind as per UU No. 27 of 2022 on Personal Data Protection (PDP Law).
  • User data is only collected and used** in accordance with the consent given.
  • Supports the principle of data minimization, i.e. only accessing data that is relevant for a particular process.

Data Request: Flow Explanation and Transparency​

Data Request Process​

  • Each data request is made via an access token issued using OIDC 1.0 and OAuth 2.0 protocols.
  • Only data that is specific** to the needs of the service will be provided.
  • Ensure that users provide explicit consent** before their data is processed or shared.
  • What information is requested, the reason for the request, and the accessing party will be explained transparently to the user.