You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AS a User WHEN i subscribe an app/service where i accepted the terms that the technical user data is managed by the app/service provider THEN i dont want to be able to see the technical user in the overview.
The endpoint GET: /api/administration/serviceaccount/owncompany/serviceaccounts should filter out technical users that were created from a technical user profile which has the flag AccessibleForProviderOnly set to true
Acceptance Criteria
adjust CompaniesLinkedTechnicalUser view to use the newly created type PROVIDER_OWNED if type is PROVIDER_OWNED the provider and owners should be set to the offer provider
adjust logic of GET: /api/administration/serviceaccount/owncompany/serviceaccounts to filter out techncical users of type 'PROVIDER_OWNED'
Additional Information
The text was updated successfully, but these errors were encountered:
* adjust view `CompanyLinkedTechnicalUsers` to include `PROVIDER_OWNED` technical users
* adjust logic of `GET: /api/administration/serviceaccount/owncompany/serviceaccounts` to filter out technical users of type 'PROVIDER_OWNED'
---------
Refs: #1211
Co-authored-by: Phil Schneider <[email protected]>
Reviewed-by: Phil Schneider <[email protected]>
Description
AS a User
WHEN i subscribe an app/service where i accepted the terms that the technical user data is managed by the app/service provider
THEN i dont want to be able to see the technical user in the overview.
The endpoint
GET: /api/administration/serviceaccount/owncompany/serviceaccounts
should filter out technical users that were created from a technical user profile which has the flagAccessibleForProviderOnly
set to trueAcceptance Criteria
PROVIDER_OWNED
if type isPROVIDER_OWNED
the provider and owners should be set to the offer providerAdditional Information
The text was updated successfully, but these errors were encountered: