Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow multiple roles / managed technical users per service #175

Open
3 tasks
Sebastian-Wurm opened this issue Aug 21, 2024 · 0 comments
Open
3 tasks

Allow multiple roles / managed technical users per service #175

Sebastian-Wurm opened this issue Aug 21, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@Sebastian-Wurm
Copy link

Sebastian-Wurm commented Aug 21, 2024

Description

As a BPDM architect,
I want that technical users for Portal roles "BPDM Sharing Input Manager" and "BPDM Sharing Output Consumer" are automatically created when a company admin subscribes to the BPDM Sharing service,
so that the BPDM operator can create the corresponding EDC assets for the BPDM Gates of each BPDM Sharing Member.

Acceptance Criteria

  • it MUST be possible to configure multiple Portal roles for automatic creation of (managed) technical users per service, which is available for subscription via the Service Marketplace
  • technical users for "BPDM Sharing Input Manager" and "BPDM Sharing Output Consumer" MUST be created automatically on subscribing to the BPDM Sharing service
  • a technical user for "BPDM Pool Consumer" MUST be created automatically on subscribing to the BPDM Golden Record service

Additional Information

  • this is already working for "BPDM Sharing Input Manager" and the BPDM Sharing service; these technical users are required for the BPDM operator to configure the corresponding BPDM assets for a BPDM Gate
    • FullAccessGateInputForSharingMember -> BPDM Sharing Input Manager
    • ReadAccessGateOutputForSharingMember -> BPDM Sharing Output Consumer
  • for the BPDM Golden Record service, only one role / managed technical user per subscription is currently required for the BPDM operator to configure the corresponding BPDM asset for the BPDM Pool
    • ReadAccessPoolForCatenaXMember -> BPDM Pool Consumer

Out of Scope

  • for BPDM value-added services, it depends, how many roles / managed technical users per subscription are required; it may be required to create the following managed technical users per subscription of the BPDM value-added service, so that the BPDM operator can configure the corresponding BPDM assets for BPDM Gate and BPDM Pool:
    • ReadAccessGateInputForSharingMember -> BPDM Sharing Input Consumer
    • ReadAccessPoolForCatenaXMember-> BPDM Pool Consumer
  • this is an additional requirement which needs to be filed against portal-iam from each BPDM value-added service separately
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: NEW USER REQUEST
Development

No branches or pull requests

3 participants