stephanbcbauer
commented
1 week ago Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)
- Status currently in Inbox. ⇾ Only features with status backlog are considered in open planning
- Please add missing sections from the feature template, or fill them out
MaximilianHauer
evegufy
Overview
Explain the topic in 2 sentences
When customers subscribe to the Golden Record Service, a technical user is created in their profile but is inaccessible due to private settings, and the operator uses it to manage assets in the EDC. The proposed update will notify customers of the technical user’s creation for operator use, grouping it separately in their profile without revealing sensitive details.
What's the benefit?
Security and user experience.
The technical users cannot be used because the network settings for these endpoints are set to private. However, if a release or other circumstances were to mistakenly change this setting, this solution provides an added layer of security.
UX: The customer sees something in the process that they cannot use and may not understand its purpose.
What are the Risks/Dependencies ?
What happens to the current implementation, where the customer has access to those technical users?
Detailed explanation
Current implementation
When the customer/user clicks "subscribe" to the Golden Record Service from BPDM, they are shown a technical user in their profile that they cannot use. This is because the service endpoints are "private" and accessible only via EDC as a proxy. However, the operator still requires the technical users generated in step 2 to create the assets within the EDC.
Proposed improvements
Before the subscription process, the customer must acknowledge that a technical user linked to their identity will be created and used by the operator. Once the subscription is approved, a pop-up will notify the customer that the technical user has been created, but no details will be displayed. In the section where the customer can view all their technical users, there will be a separate segment listing the technical users utilized by the operator, again without detailed information (such as client secrets, etc.).
Feature Team
Contributor
Committer
User Stories or related features
https://github.com/eclipse-tractusx/portal-iam/issues/168 https://github.com/eclipse-tractusx/sig-release/issues/918
Acceptance Criteria
Before completing the subscription process, the customer must see and confirm an acknowledgment message stating that a technical user linked to their identity will be created and managed by the operator for service operation.
Upon successful subscription, a pop-up notification appears to inform the customer that the technical user has been created. This pop-up will not display any technical details about the user.
In the customer's technical user section, a dedicated segment will list technical users utilized by the operator. This segment will display only minimal information (e.g., user name) without exposing sensitive details such as client secrets or access tokens.
Only the operator can access and use these technical users.
Test Cases
Test Case 1
Steps
Expected Result
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented:
Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)
Additional information