[Story] FEAT-DATSET-14: Add credentials for an InvenioRDM instance

[sven1103-agent]

Parent Feature

#1466

Requirement IDs

DATA-R-03

User Story

As a researcher, I want to provide my access token for an available InvenioRDM instance, so that I can connect access-restricted resources in a project.

Acceptance Criteria

• Given a user is in their account settings, When they navigate to the InvenioRDM configuration section, Then the system offers a way to configure InvenioRDM instances.
• Given the user is configuring instances, When they view available InvenioRDM instances, Then the system displays the list of available InvenioRDM instances to configure (e.g. Zenodo, FDAT).
• Given the user pastes or enters a token, When they submit it, Then the token is validated against the InvenioRDM instance via its API.
• Given a token is invalid, When the validation fails, Then the token is not added to the user's account and the user is informed that the token is invalid.
• Given a token is valid, When the validation succeeds, Then the user is informed that a valid token has been added and the InvenioRDM instance is now connected.
• Given the user is viewing the InvenioRDM configuration section, When they see the benefits of providing a token, Then the system highlights a description of what the benefits are (the connection of access-restricted datasets to a project).

Notes & Context

• Part of FEAT-DATASET-CONNECTION (Connect associated InvenioRDM datasets with Data Manager projects)
• Stable Story ID: FEAT-DATSET-14
• Persona: Researcher
• Depends on: No prerequisite — can be implemented independently; Stories 05 and 06 (restricted dataset access) depend on this story
• Source document: 2026-06-19_FEATURE_Connect_associated_datasets_with_DM_projects.docx (stakeholder space — see parent feature [Feature] Connect associated InvenioRDM datasets with Data Manager projects #1466 §Stakeholder Artifacts) — Story 14
• Tokens must be stored encrypted per project vault requirements (see AGENTS.md §10).