Skip to content

Update Wallet Metadata and EC#1092

Open
giadas wants to merge 19 commits into
italia:eudiwfrom
giadas:iss-1076-wpmetadata
Open

Update Wallet Metadata and EC#1092
giadas wants to merge 19 commits into
italia:eudiwfrom
giadas:iss-1076-wpmetadata

Conversation

@giadas

@giadas giadas commented Apr 17, 2026

Copy link
Copy Markdown
Collaborator

This PR resolves

The files modified are 6:

  • remote-flow.rst (en and it)
  • wallet-solution-metadata.rst (en and it)
  • test-plans-wallet-provider.rst (en and it)

the others result from the switch from italia:versione-corrente to italia:eudiw

@giadas giadas added this to the 1.4.2 milestone Apr 17, 2026
@github-actions

Copy link
Copy Markdown
Contributor

📢 Documentation Preview 🔍

This PR comes from a forked repository, so the documentation preview was not automatically generated.

⚠️ For repository maintainers only:

You can generate a preview using the manual workflow, with PR Number: 1092 as an input.

Once generated, the preview link will be added as a comment to this PR.

@giadas giadas added the LTS label Apr 17, 2026
@giadas giadas requested a review from grausof April 17, 2026 12:59
Comment thread docs/it/wallet-solution-metadata.rst Outdated
Comment thread docs/it/wallet-solution-metadata.rst Outdated
Comment thread docs/it/remote-flow.rst Outdated
@manuraf

manuraf commented Apr 21, 2026

Copy link
Copy Markdown
Collaborator

It might be worth revisiting this part for the test-plans-wallet-provider, for ex. WP_083a currently describes the wallet_metadata runtime including the authorization_endpoint.

With the changes introduced in this PR, the authorization_endpoint has been removed from the runtime wallet_metadata. As a result, few test cases seems to be no longer aligned with the updated specification.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Wallet Provider Entity Configuration (EC) metadata structure and related documentation to align with issues #1075 and #1076 by removing the wallet_metadata wrapper and trimming presentation-time wallet metadata parameters.

Changes:

  • Updated the WP EC example to remove wallet_metadata and move wallet metadata fields to the wallet_solution top level.
  • Updated wallet solution metadata docs (IT/EN) to document the metadata fields at the top level (no wallet_metadata container).
  • Updated remote-flow docs (IT/EN) examples/tables to remove presentation-time wallet_metadata fields that are no longer required.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 7 comments.

Show a summary per file
File Description
examples/ec-wp.json Moves wallet metadata fields out of wallet_metadata into the wallet_solution object.
docs/it/wallet-solution-metadata.rst Updates IT documentation to reflect the new metadata structure and adds guidance about authorization endpoint links.
docs/it/remote-flow.rst Updates IT remote-flow examples/tables to reflect reduced wallet_metadata during presentation.
docs/en/wallet-solution-metadata.rst Updates EN documentation to reflect the new metadata structure and adds guidance about authorization endpoint links.
docs/en/remote-flow.rst Updates EN remote-flow examples/tables to reflect reduced wallet_metadata during presentation.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread docs/it/wallet-solution-metadata.rst Outdated
Comment thread docs/it/remote-flow.rst Outdated
Comment thread docs/it/wallet-solution-metadata.rst Outdated
Comment thread docs/it/wallet-solution-metadata.rst Outdated
Comment thread docs/it/wallet-solution-metadata.rst Outdated
Comment thread docs/en/wallet-solution-metadata.rst Outdated
Comment thread docs/en/wallet-solution-metadata.rst Outdated
@peppelinux peppelinux removed the LTS label Apr 28, 2026
@peppelinux peppelinux modified the milestones: 1.4.2, 1.5.0 Apr 28, 2026
@peppelinux peppelinux changed the base branch from versione-corrente to eudiw April 28, 2026 13:10
Comment thread docs/it/wallet-solution-metadata.rst Outdated
Co-authored-by: Manuel Rafeli <manuel.rafeli@pagopa.it>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Giada Sciarretta <giada.sciarretta@gmail.com>
@github-actions

Copy link
Copy Markdown
Contributor

📢 Documentation Preview 🔍

This PR comes from a forked repository, so the documentation preview was not automatically generated.

⚠️ For repository maintainers only:

You can generate a preview using the manual workflow, with PR Number: 1092 as an input.

Once generated, the preview link will be added as a comment to this PR.

@github-actions

Copy link
Copy Markdown
Contributor

📢 Documentation Preview 🔍

This PR comes from a forked repository, so the documentation preview was not automatically generated.

⚠️ For repository maintainers only:

You can generate a preview using the manual workflow, with PR Number: 1092 as an input.

Once generated, the preview link will be added as a comment to this PR.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 24 out of 24 changed files in this pull request and generated 7 comments.

"credentials": [
{
"version": "1.0",
"version": "1",
Comment thread docs/en/registry.rst
2. **Private Sector AS** (Flexible Integration): Private entities provide specialized data through custom arrangements:

- **Custom APIs**: ``"integration_method": "custom_api"`` for business-specific data access patterns.
- **Custom APIs**: ``"integration_method": "pdnd"`` for business-specific data access.
Comment thread docs/en/registry.rst

- **Custom APIs**: ``"integration_method": "custom_api"`` for business-specific data access patterns.
- **Custom APIs**: ``"integration_method": "pdnd"`` for business-specific data access.
- **Regulatory Compliance**: Full transparency requirements with public catalog publication.
Comment thread docs/it/registry.rst
2. **FA del Settore Privato** (Integrazione Flessibile): Le entità private forniscono dati specializzati tramite accordi personalizzati:

- **API Personalizzate**: ``"integration_method": "custom_api"`` per pattern di accesso ai dati specifici del business.
- **API Personalizzate**: ``"integration_method": "pdnd"`` per l'accesso ai dati specifici del business.
Comment thread docs/it/registry.rst

- **API Personalizzate**: ``"integration_method": "custom_api"`` per pattern di accesso ai dati specifici del business.
- **API Personalizzate**: ``"integration_method": "pdnd"`` per l'accesso ai dati specifici del business.
- **Conformità Normativa**: Requisiti di piena trasparenza con pubblicazione pubblica nel catalogo.
Authentic Source entities MUST undergo registration procedures that validate their data authority, declare their available claims from the standardized Claims Registry, and establish technical integration mechanisms. Authentic Source entities specify intended use cases (formally ``purposes``) that determine catalog eligibility per Supervisory Body policies.

Public Authentic Sources MUST leverage PDND integration to provide government data through standardized national infrastructure.
Public and Private Authentic Sources MUST leverage PDND integration to provide government data through standardized national infrastructure.
Le Fonti Autentiche Private POSSONO stabilire interfacce di servizio personalizzate che soddisfano requisiti organizzativi o normativi specifici.

Entrambe i flussi DEVONO assicurare standard di qualità dei dati e stabilire tracce di audit per tutte le attività di fornitura dati.
Le Fonti Autentiche Pubbliche e Private DEVONO sfruttare l'integrazione PDND per fornire dati governativi attraverso l'infrastruttura nazionale standardizzata.
Comment thread docs/en/registry.rst
* - **organization_info.tos_uri**
- string
- REQUIRED only for Private AS. URL to terms of service document.
- OPTIONAL. URL to terms of service document.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fmarino-ipzs is this compliant with GDP positions?

@vcarollo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants