feat: enhance technical user detail page #1093
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oyo
approved these changes
Sep 17, 2024
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Note: Roles data, which is retrieved from the backend API under the key "roles," is already displayed on the page as "Permission."
Dependency:
This change depends on the backend update to include the
usertype, authenticationServiceUrlfields in the API response fromGET: api/administration/serviceaccount/owncompany/serviceaccounts/{GetServiceAccountId}. The backend implementation for this feature is tracked under sig#789 - API Expansion for Technical User Information portal-backend#976.Why
To ensure complete service details are displayed and users are informed if information is missing for older profiles
Issue
1078
Checklist