Place holder for issues on Roles SPA
See original GitHub issueAs part of supporting granular auth https://github.com/gocd/gocd/issues/7222, the Roles SPA was modified to support policy
. Below is the list of issues on the Roles SPA,
- Error while adding policy to roles if none of the attributes are selected. Add a client side error handling before making a API call.
- When a new role is added, a default Deny policy is added. Is this required or do we leave it upto to the user to add a policy?
- The current message
The default policy is to deny access to all GoCD entities. Configure permissions below to override that behavior.
seems confusing. We need to change the message and provide link to Policy documentation.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
[Pipeline Config SPA] [Placeholder] Issues with new ... - GitHub
This is a placeholder issue to document issues with in-development pipeline config SPA. Tabs ready for QA All Tabs are ready for QA...
Read more >Advanced: Placeholders | Jira Service Management Data ...
Placeholders can replace different data for different contexts (custom fields, automation, post functions). Automation rules. For more info on ...
Read more >ARIA live regions - Accessibility - MDN Web Docs - Mozilla
Including an aria-live attribute or a specialized live region role (such as role="alert" ) on the element you want to announce changes to...
Read more >Placeholders in Form Fields Are Harmful
One last issue to consider is that placeholder text is generally bad for accessibility. Certainly, accessibility software and modern ...
Read more >Authorize access to blobs with AzCopy & Azure Active Directory
To learn how to verify and assign roles, see Assign an Azure role for ... Replace the <tenant-id> placeholder with the tenant ID...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@kritika-singh3 @GaneshSPatil
Point 1: Since both All and administer are essentially the same I am of the opinion we should drop the support for * from the policy for actions.
For point 2: We can keep the (*). We will document it properly
Verified on 19.11.0 (10687-c532a61bb240ffbe59fe356445bea6433005563f)