Aquest lloc web fa servir cookies pròpies i de tercers per millorar l’experiència de navegació, i oferir continguts i serveis d’interès. En continuar la navegació entenem que acceptes la nostra política de cookies. Per a més informació consulta aquí.
Launch of Prometheus-X new website! - Welcome to the future of Data Spaces in Europe

Technical group

Technical Working Group of the Education and Skills Data Space

Canvis a "How to handle decentralized identity in DASES?"

Mode de vista de comparació:
Vista HTML:

Descripció (English)

  • -

    Walt.id is a library developped to handle decentralized identity within european reglations: https://github.com/walt-id/waltid-ssikit

    This could be a strating point for this debate

    A page to introduce SSI (Self-sovereign identity) and decentralized identity : SSI Essentials: Everything you need to know about Decentralized Identity

    identity architectures history

    An explanation about DIDs (Decentralized Identity) and VCs (Verifiable Credentials) : What are Decentralized Identifiers (DIDs) & Verifiable Credentials (VCs)?

    The structure of a DID is:

    • DID Scheme: All DIDs begin with “did:”
    • DID method: This field specifies how to deal with this DID. When reading this part of the DID, computers understand where to go fetch the DID. It could be on a blockchain (EBSI) or on a DNS (web)
    • DID Method-specific identifier: Refers to the DID’s unique identifier within the method


    An user can request to associate one or several Verifiable Credentials to a DID. An Issuer will issue VC for this specific DID

    dids flow

    There are 3 components in a VC:

    1. Credential Metadata: Properties or attributes of the credential
    2. Claims: A statements about a subject (individual, legal entity, or thing).
    3. Proofs: cryptographic signatures tied to private keys that prove the user sharing the VC is the subject of the information

    vcs datamodel

    This article is based on https://gataca.io and https://medium.com/metadium/decentralized-identifiers-the-easy-guide-fb96429e8b24

  • +

    Walt.id is a library developped to handle decentralized identity within european reglations: https://github.com/walt-id/waltid-ssikit

    This could be a strating point for this debate

    A page to introduce SSI (Self-sovereign identity) and decentralized identity : SSI Essentials: Everything you need to know about Decentralized Identity

    identity architectures history

    An explanation about DIDs (Decentralized Identity) and VCs (Verifiable Credentials) : What are Decentralized Identifiers (DIDs) & Verifiable Credentials (VCs)?

    The structure of a DID is:

    • DID Scheme: All DIDs begin with “did:”
    • DID method: This field specifies how to deal with this DID. When reading this part of the DID, computers understand where to go fetch the DID. It could be on a blockchain (EBSI) or on a DNS (web)
    • DID Method-specific identifier: Refers to the DID’s unique identifier within the method


    An user can request to associate one or several Verifiable Credentials to a DID. An Issuer will issue VC for this specific DID

    dids flow

    There are 3 components in a VC:

    1. Credential Metadata: Properties or attributes of the credential
    2. Claims: A statements about a subject (individual, legal entity, or thing).
    3. Proofs: cryptographic signatures tied to private keys that prove the user sharing the VC is the subject of the information

    vcs datamodel

    This article is based on https://gataca.io and https://medium.com/metadium/decentralized-identifiers-the-easy-guide-fb96429e8b24


    Subjects to debate:

    • How to log in on Prometheus-X ?
    1. With an account
    2. With a wallet extension on the browser
    3. With a QR Code and a smartphone wallet
    • How to use personnal wallet/enterprise wallet?
    1. Both wallets are required and you have to swtich from one to the other
    2. The company can issue VCs (with enterprise wallet) and only personnal wallet is required on the platform (with rights granted by the company) to interact with services
    • Will it be possible to use several wallets?
    1. No, only one wallet will be used by Prometheus-X
    2. Yes, Prometheus-X is an open platform, PX compliants wallets will be able to be used
    • How will VCs be requested and issued?
    1. Not directly from PROMETHEUS-X, wallets or services accessible on Prometheus-X will be able to do it (or external services)
    2. Only a specific VC to authorize the access to PX services will be issued by PX following a request on the platform
    3. PX will provide internal services for VCs issuing
  • -<p>Walt.id is a library developped to handle decentralized identity within european reglations: https://github.com/walt-id/waltid-ssikit</p><p>This could be a strating point for this debate</p><p>A page to introduce SSI (Self-sovereign identity) and decentralized identity : <a href="https://gataca.io/blog/ssi-essentials-everything-you-need-to-know-about-decentralized-identity" rel="noopener noreferrer" target="_blank">SSI Essentials: Everything you need to know about Decentralized Identity</a></p><p><img src="https://gataca.io/static/dfefd68f3d6f79288978e50b5e0694c4/2bef9/identity_architectures_history.png" alt="identity architectures history"></p><p>An explanation about DIDs (Decentralized Identity) and VCs (Verifiable Credentials) : <a href="https://gataca.io/blog/self-sovereign-identity-ssi-101-decentralized-identifiers-dids-verifiable-credentials-vcs" rel="noopener noreferrer" target="_blank">What are Decentralized Identifiers (DIDs) &amp; Verifiable Credentials (VCs)?</a></p><p>The structure of a DID is:</p><p><img src="https://miro.medium.com/max/615/1*9vdtcu4m6Q5fkg_GievK6Q.png"></p><ul><li>DID Scheme: All DIDs begin with “did:”</li><li>DID method: This field specifies how to deal with this DID. When reading this part of the DID, computers understand where to go fetch the DID. It could be on a blockchain (EBSI) or on a DNS (web)</li><li>DID Method-specific identifier: Refers to the DID’s unique identifier within the method</li></ul><p><br></p><p>An user can request to associate one or several Verifiable Credentials to a DID. An Issuer will issue VC for this specific DID</p><p><img src="https://gataca.io/static/b0a55c652c503efe1be79d4decec8136/2bef9/dids_flow.png" alt="dids flow"></p><p>There are 3 components in a VC:</p><ol><li><strong>Credential Metadata</strong>: Properties or attributes of the credential</li><li><strong>Claims</strong>: A statements about a subject (individual, legal entity, or thing).</li><li><strong>Proofs</strong>: cryptographic signatures tied to private keys that prove the user sharing the VC is the subject of the information</li></ol><p><img src="https://gataca.io/static/8ccc1561ffed4a9cf089c8c1f0c0fa2a/2bef9/vcs_datamodel.png" alt="vcs datamodel"></p><p>This article is based on https://gataca.io and https://medium.com/metadium/decentralized-identifiers-the-easy-guide-fb96429e8b24</p>
  • +<p>Walt.id is a library developped to handle decentralized identity within european reglations: https://github.com/walt-id/waltid-ssikit</p><p>This could be a strating point for this debate</p><p>A page to introduce SSI (Self-sovereign identity) and decentralized identity : <a href="https://gataca.io/blog/ssi-essentials-everything-you-need-to-know-about-decentralized-identity" rel="noopener noreferrer" target="_blank">SSI Essentials: Everything you need to know about Decentralized Identity</a></p><p><img src="https://gataca.io/static/dfefd68f3d6f79288978e50b5e0694c4/2bef9/identity_architectures_history.png" alt="identity architectures history"></p><p>An explanation about DIDs (Decentralized Identity) and VCs (Verifiable Credentials) : <a href="https://gataca.io/blog/self-sovereign-identity-ssi-101-decentralized-identifiers-dids-verifiable-credentials-vcs" rel="noopener noreferrer" target="_blank">What are Decentralized Identifiers (DIDs) &amp; Verifiable Credentials (VCs)?</a></p><p>The structure of a DID is:</p><p><img src="https://miro.medium.com/max/615/1*9vdtcu4m6Q5fkg_GievK6Q.png"></p><ul><li>DID Scheme: All DIDs begin with “did:”</li><li>DID method: This field specifies how to deal with this DID. When reading this part of the DID, computers understand where to go fetch the DID. It could be on a blockchain (EBSI) or on a DNS (web)</li><li>DID Method-specific identifier: Refers to the DID’s unique identifier within the method</li></ul><p><br></p><p>An user can request to associate one or several Verifiable Credentials to a DID. An Issuer will issue VC for this specific DID</p><p><img src="https://gataca.io/static/b0a55c652c503efe1be79d4decec8136/2bef9/dids_flow.png" alt="dids flow"></p><p>There are 3 components in a VC:</p><ol><li><strong>Credential Metadata</strong>: Properties or attributes of the credential</li><li><strong>Claims</strong>: A statements about a subject (individual, legal entity, or thing).</li><li><strong>Proofs</strong>: cryptographic signatures tied to private keys that prove the user sharing the VC is the subject of the information</li></ol><p><img src="https://gataca.io/static/8ccc1561ffed4a9cf089c8c1f0c0fa2a/2bef9/vcs_datamodel.png" alt="vcs datamodel"></p><p>This article is based on https://gataca.io and https://medium.com/metadium/decentralized-identifiers-the-easy-guide-fb96429e8b24</p><p><br></p><p>Subjects to debate:</p><ul><li>How to log in on Prometheus-X ?</li></ul><ol><li>With an account</li><li>With a wallet extension on the browser</li><li>With a QR Code and a smartphone wallet</li></ol><ul><li>How to use personnal wallet/enterprise wallet?</li></ul><ol><li>Both wallets are required and you have to swtich from one to the other</li><li>The company can issue VCs (with enterprise wallet) and only personnal wallet is required on the platform (with rights granted by the company) to interact with services</li></ol><ul><li>Will it be possible to use several wallets?</li></ul><ol><li>No, only one wallet will be used by Prometheus-X</li><li>Yes, Prometheus-X is an open platform, PX compliants wallets will be able to be used</li></ol><ul><li>How will VCs be requested and issued?</li></ul><ol><li>Not directly from PROMETHEUS-X, wallets or services accessible on Prometheus-X will be able to do it (or external services)</li><li>Only a specific VC to authorize the access to PX services will be issued by PX following a request on the platform</li><li>PX will provide internal services for VCs issuing </li></ol>
Esborrats
  • -

    Walt.id is a library developped to handle decentralized identity within european reglations: https://github.com/walt-id/waltid-ssikit

    This could be a strating point for this debate

    A page to introduce SSI (Self-sovereign identity) and decentralized identity : SSI Essentials: Everything you need to know about Decentralized Identity

    identity architectures history

    An explanation about DIDs (Decentralized Identity) and VCs (Verifiable Credentials) : What are Decentralized Identifiers (DIDs) & Verifiable Credentials (VCs)?

    The structure of a DID is:

    • DID Scheme: All DIDs begin with “did:”
    • DID method: This field specifies how to deal with this DID. When reading this part of the DID, computers understand where to go fetch the DID. It could be on a blockchain (EBSI) or on a DNS (web)
    • DID Method-specific identifier: Refers to the DID’s unique identifier within the method


    An user can request to associate one or several Verifiable Credentials to a DID. An Issuer will issue VC for this specific DID

    dids flow

    There are 3 components in a VC:

    1. Credential Metadata: Properties or attributes of the credential
    2. Claims: A statements about a subject (individual, legal entity, or thing).
    3. Proofs: cryptographic signatures tied to private keys that prove the user sharing the VC is the subject of the information

    vcs datamodel

    This article is based on https://gataca.io and https://medium.com/metadium/decentralized-identifiers-the-easy-guide-fb96429e8b24

  • DID method: This field specifies how to deal with this DID. When reading this part of the DID, computers understand where to go fetch the DID. It could be on a blockchain (EBSI) or on a DNS (web)
  • DID Method-specific identifier: Refers to the DID’s unique identifier within the method


An user can request to associate one or several Verifiable Credentials to a DID. An Issuer will issue VC for this specific DID

dids flow

There are 3 components in a VC:

  1. Credential Metadata: Properties or attributes of the credential
  2. Claims: A statements about a subject (individual, legal entity, or thing).
  3. Proofs: cryptographic signatures tied to private keys that prove the user sharing the VC is the subject of the information

vcs datamodel

This article is based on https://gataca.io and https://medium.com/metadium/decentralized-identifiers-the-easy-guide-fb96429e8b24


Subjects to debate:

  • How to log in on Prometheus-X ?
  1. With an account
  2. With a wallet extension on the browser
  3. With a QR Code and a smartphone wallet
  • How to use personnal wallet/enterprise wallet?
  1. Both wallets are required and you have to swtich from one to the other
  2. The company can issue VCs (with enterprise wallet) and only personnal wallet is required on the platform (with rights granted by the company) to interact with services
  • Will it be possible to use several wallets?
  1. No, only one wallet will be used by Prometheus-X
  2. Yes, Prometheus-X is an open platform, PX compliants wallets will be able to be used
  • How will VCs be requested and issued?
  1. Not directly from PROMETHEUS-X, wallets or services accessible on Prometheus-X will be able to do it (or external services)
  2. Only a specific VC to authorize the access to PX services will be issued by PX following a request on the platform
  3. PX will provide internal services for VCs issuing
Addicions
  • DID method: This field specifies how to deal with this DID. When reading this part of the DID, computers understand where to go fetch the DID. It could be on a blockchain (EBSI) or on a DNS (web)
  • DID Method-specific identifier: Refers to the DID’s unique identifier within the method


An user can request to associate one or several Verifiable Credentials to a DID. An Issuer will issue VC for this specific DID

dids flow

There are 3 components in a VC:

  1. Credential Metadata: Properties or attributes of the credential
  2. Claims: A statements about a subject (individual, legal entity, or thing).
  3. Proofs: cryptographic signatures tied to private keys that prove the user sharing the VC is the subject of the information

vcs datamodel

This article is based on https://gataca.io and https://medium.com/metadium/decentralized-identifiers-the-easy-guide-fb96429e8b24

  • +

    Walt.id is a library developped to handle decentralized identity within european reglations: https://github.com/walt-id/waltid-ssikit

    This could be a strating point for this debate

    A page to introduce SSI (Self-sovereign identity) and decentralized identity : SSI Essentials: Everything you need to know about Decentralized Identity

    identity architectures history

    An explanation about DIDs (Decentralized Identity) and VCs (Verifiable Credentials) : What are Decentralized Identifiers (DIDs) & Verifiable Credentials (VCs)?

    The structure of a DID is:

    • DID Scheme: All DIDs begin with “did:”
    • DID method: This field specifies how to deal with this DID. When reading this part of the DID, computers understand where to go fetch the DID. It could be on a blockchain (EBSI) or on a DNS (web)
    • DID Method-specific identifier: Refers to the DID’s unique identifier within the method


    An user can request to associate one or several Verifiable Credentials to a DID. An Issuer will issue VC for this specific DID

    dids flow

    There are 3 components in a VC:

    1. Credential Metadata: Properties or attributes of the credential
    2. Claims: A statements about a subject (individual, legal entity, or thing).
    3. Proofs: cryptographic signatures tied to private keys that prove the user sharing the VC is the subject of the information

    vcs datamodel

    This article is based on https://gataca.io and https://medium.com/metadium/decentralized-identifiers-the-easy-guide-fb96429e8b24


    Subjects to debate:

    • How to log in on Prometheus-X ?
    1. With an account
    2. With a wallet extension on the browser
    3. With a QR Code and a smartphone wallet
    • How to use personnal wallet/enterprise wallet?
    1. Both wallets are required and you have to swtich from one to the other
    2. The company can issue VCs (with enterprise wallet) and only personnal wallet is required on the platform (with rights granted by the company) to interact with services
    • Will it be possible to use several wallets?
    1. No, only one wallet will be used by Prometheus-X
    2. Yes, Prometheus-X is an open platform, PX compliants wallets will be able to be used
    • How will VCs be requested and issued?
    1. Not directly from PROMETHEUS-X, wallets or services accessible on Prometheus-X will be able to do it (or external services)
    2. Only a specific VC to authorize the access to PX services will be issued by PX following a request on the platform
    3. PX will provide internal services for VCs issuing
    • Esborrats
    • -<p>Walt.id is a library developped to handle decentralized identity within european reglations: https://github.com/walt-id/waltid-ssikit</p><p>This could be a strating point for this debate</p><p>A page to introduce SSI (Self-sovereign identity) and decentralized identity : <a href="https://gataca.io/blog/ssi-essentials-everything-you-need-to-know-about-decentralized-identity" rel="noopener noreferrer" target="_blank">SSI Essentials: Everything you need to know about Decentralized Identity</a></p><p><img src="https://gataca.io/static/dfefd68f3d6f79288978e50b5e0694c4/2bef9/identity_architectures_history.png" alt="identity architectures history"></p><p>An explanation about DIDs (Decentralized Identity) and VCs (Verifiable Credentials) : <a href="https://gataca.io/blog/self-sovereign-identity-ssi-101-decentralized-identifiers-dids-verifiable-credentials-vcs" rel="noopener noreferrer" target="_blank">What are Decentralized Identifiers (DIDs) &amp; Verifiable Credentials (VCs)?</a></p><p>The structure of a DID is:</p><p><img src="https://miro.medium.com/max/615/1*9vdtcu4m6Q5fkg_GievK6Q.png"></p><ul><li>DID Scheme: All DIDs begin with “did:”</li><li>DID method: This field specifies how to deal with this DID. When reading this part of the DID, computers understand where to go fetch the DID. It could be on a blockchain (EBSI) or on a DNS (web)</li><li>DID Method-specific identifier: Refers to the DID’s unique identifier within the method</li></ul><p><br></p><p>An user can request to associate one or several Verifiable Credentials to a DID. An Issuer will issue VC for this specific DID</p><p><img src="https://gataca.io/static/b0a55c652c503efe1be79d4decec8136/2bef9/dids_flow.png" alt="dids flow"></p><p>There are 3 components in a VC:</p><ol><li><strong>Credential Metadata</strong>: Properties or attributes of the credential</li><li><strong>Claims</strong>: A statements about a subject (individual, legal entity, or thing).</li><li><strong>Proofs</strong>: cryptographic signatures tied to private keys that prove the user sharing the VC is the subject of the information</li></ol><p><img src="https://gataca.io/static/8ccc1561ffed4a9cf089c8c1f0c0fa2a/2bef9/vcs_datamodel.png" alt="vcs datamodel"></p><p>This article is based on https://gataca.io and https://medium.com/metadium/decentralized-identifiers-the-easy-guide-fb96429e8b24</p>
    Addicions
    • +<p>Walt.id is a library developped to handle decentralized identity within european reglations: https://github.com/walt-id/waltid-ssikit</p><p>This could be a strating point for this debate</p><p>A page to introduce SSI (Self-sovereign identity) and decentralized identity : <a href="https://gataca.io/blog/ssi-essentials-everything-you-need-to-know-about-decentralized-identity" rel="noopener noreferrer" target="_blank">SSI Essentials: Everything you need to know about Decentralized Identity</a></p><p><img src="https://gataca.io/static/dfefd68f3d6f79288978e50b5e0694c4/2bef9/identity_architectures_history.png" alt="identity architectures history"></p><p>An explanation about DIDs (Decentralized Identity) and VCs (Verifiable Credentials) : <a href="https://gataca.io/blog/self-sovereign-identity-ssi-101-decentralized-identifiers-dids-verifiable-credentials-vcs" rel="noopener noreferrer" target="_blank">What are Decentralized Identifiers (DIDs) &amp; Verifiable Credentials (VCs)?</a></p><p>The structure of a DID is:</p><p><img src="https://miro.medium.com/max/615/1*9vdtcu4m6Q5fkg_GievK6Q.png"></p><ul><li>DID Scheme: All DIDs begin with “did:”</li><li>DID method: This field specifies how to deal with this DID. When reading this part of the DID, computers understand where to go fetch the DID. It could be on a blockchain (EBSI) or on a DNS (web)</li><li>DID Method-specific identifier: Refers to the DID’s unique identifier within the method</li></ul><p><br></p><p>An user can request to associate one or several Verifiable Credentials to a DID. An Issuer will issue VC for this specific DID</p><p><img src="https://gataca.io/static/b0a55c652c503efe1be79d4decec8136/2bef9/dids_flow.png" alt="dids flow"></p><p>There are 3 components in a VC:</p><ol><li><strong>Credential Metadata</strong>: Properties or attributes of the credential</li><li><strong>Claims</strong>: A statements about a subject (individual, legal entity, or thing).</li><li><strong>Proofs</strong>: cryptographic signatures tied to private keys that prove the user sharing the VC is the subject of the information</li></ol><p><img src="https://gataca.io/static/8ccc1561ffed4a9cf089c8c1f0c0fa2a/2bef9/vcs_datamodel.png" alt="vcs datamodel"></p><p>This article is based on https://gataca.io and https://medium.com/metadium/decentralized-identifiers-the-easy-guide-fb96429e8b24</p><p><br></p><p>Subjects to debate:</p><ul><li>How to log in on Prometheus-X ?</li></ul><ol><li>With an account</li><li>With a wallet extension on the browser</li><li>With a QR Code and a smartphone wallet</li></ol><ul><li>How to use personnal wallet/enterprise wallet?</li></ul><ol><li>Both wallets are required and you have to swtich from one to the other</li><li>The company can issue VCs (with enterprise wallet) and only personnal wallet is required on the platform (with rights granted by the company) to interact with services</li></ol><ul><li>Will it be possible to use several wallets?</li></ul><ol><li>No, only one wallet will be used by Prometheus-X</li><li>Yes, Prometheus-X is an open platform, PX compliants wallets will be able to be used</li></ol><ul><li>How will VCs be requested and issued?</li></ul><ol><li>Not directly from PROMETHEUS-X, wallets or services accessible on Prometheus-X will be able to do it (or external services)</li><li>Only a specific VC to authorize the access to PX services will be issued by PX following a request on the platform</li><li>PX will provide internal services for VCs issuing </li></ol>
    Número de versió 6 de 8 Mostra totes les versions Tornar al debat
    Autoria de la versió
    Avatar: Perrin Perrin
    Versió creada el 13/12/2021 17:53