Enhancement of Technical User E2E Experience in Dataspace

[jjeroch]

Summary:

This epic aims to significantly improve the end-to-end experience for technical users in the dataspace environment. It encompasses the expansion of the current API to include additional technical user information, UI enhancements for better information sharing, and the introduction of a central service for consistent user management.

Objectives:

1. API Enhancement: Expand the GET technical user information API to include the type of technical user (synchronous/asynchronous) and the associated service endpoint.
2. UI Enhancements: Upgrade the User Interface to display the new technical user type and service endpoint information during the technical user creation process and on the technical user detail page.
3. Naming Convention Review: Analyze and, if necessary, revise the portal table naming convention for external technical users, which is currently labeled "DIM".
4. Central Service Introduction: Develop and integrate a central service that will provide comprehensive details about technical user management, similar to the existing KITS (Knowledge Information Tracking System).

User Stories:

User Story 1: API Expansion for Technical User Information

Description:
As an API Developer, I need to enhance the GET technical user information API to include the technical user type and service endpoint so that this information can be programmatically retrieved and utilized in various systems.

Acceptance Criteria:

• The API should return whether the technical user is synchronous or asynchronous.
• The API should provide the service endpoint associated with the technical user.
• The API changes must maintain backward compatibility with existing integrations.

User Story 2: UI Enhancement for Technical User Creation

Description:
As a Frontend Developer, I need to update the technical user self-service creation UI to include fields for technical user type and service endpoint so that operators can specify and view this information during user setup.

Acceptance Criteria:

• The UI should have appropriate controls for viewing technical user types.
• The UI should have an input field for specifying the service endpoint.
• The UI must validate the service endpoint format.
• The UI should inform the enduser about the technical user status details sig#803: Add Technical User "Status" inside the technical user management page portal-frontend#944

User Story 3: UI Enhancement for Technical User Detail Page

Description:
As a Frontend Developer, I need to enhance the technical user detail page to display the new technical user type and service endpoint information for better transparency and user experience.

Acceptance Criteria:

• The detail page should clearly display whether the technical user is synchronous or asynchronous.
• The detail page should show the associated service endpoint.
• The UI should handle scenarios where this new information is not available for existing technical users.
• The UI should inform the enduser about the technical user status details.

User Story 4: Portal Table Naming Review for External Technical Users

• Asynchron Tech Users - Portal Table Naming Review for Clarity and Consistency portal-backend#879

Description:
Review and possibly rename the portal table for external technical users to ensure clarity and consistency across the platform.

Acceptance Criteria:

• The naming should be intuitive and self-explanatory.
• Any changes in naming should be communicated and documented.
• The change should be reflected across all instances in the platform where it is used.

User Story 5: Central Service Introduction for Technical User Management (Documentation)

Description:
Introduce a central service that provides detailed information about technical user management to streamline the process and make it consistent across the portal.

Acceptance Criteria:

• The service should act as a single source of truth for technical user management details.
• The service must integrate seamlessly with the existing portal UI.
• Documentation for the central service should be available and accessible via the portal UI.

Tasks:

• Define the API contract for the new technical user information.
• Implement the API changes and ensure backward compatibility.
• Design the UI changes for the technical user creation and detail pages.
• Develop the UI enhancements and integrate them with the backend services.
• Conduct a comprehensive review of the naming convention for external technical users.
• Develop and document the central service for technical user management.
• Perform thorough testing for all new features and changes.
• Prepare and execute a deployment plan.

Out of Scope:

• Overhauling the entire technical user management system is out of scope for this epic.
• Any changes to unrelated systems or features not mentioned in the user stories.

Milestones:

1. API and Backend Development Completion: tbd
2. UI Design and Development Completion: tbd
3. Central Service and Documentation Completion: tbd
4. PR Creation for review by committers: tbd
5. Full Integration and Testing Completion: tbd

[evegufy]

Committers:
@evegufy
@Phil91
@ntruchsess
@oyo

[MaximilianHauer]

Feature enhanced by the following sub-stories :

Backend

• sig#789 - API Expansion for Technical User Information portal-backend#976
• sig#789 Rename technical user Type to OWNED from OWN  portal-backend#978
• sig#789 - Enable internal technical User to get multiple roles assigned  portal-backend#977
• sig#789 - Enhance the Servicerelease Technical-user-profile API to provide more information portal-backend#1007
• sig#789 - API Expansion for Role Information portal-backend#1022

Frontend

• sig#789 - Enhance technicalUserManagement creation page by type + serviceurl portal-frontend#1077
• sig#789 - Enhance the Technical User Overview with UserType Column portal-frontend#1082
• sig#789 - UI Enhancement for Technical User Detail Page portal-frontend#1078
• sig#789 - Rename the Button in the serviceSubscription portal-frontend#1124
• sig#789 - Update ServiceReleaseProcess Form  portal-frontend#1125
• sig#789 - Refurbish the Servicerequest activation Form portal-frontend#1126