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
When creating a Repository Content Selector privilege via the REST API, it's possible to set the action as "ALL" instead of specifying each action individually. For example, you can POST the following definition to the /service/rest/v1/privileges/repository-content-selector endpoint:
However, when you view the privilege details in the UI, none of the actions appear as selected, which can be confusing. Despite the misleading display, the privilege seems to function as expected, allowing the intended actions to be performed.
Tested with Nexus 3.72 and 3.73
The text was updated successfully, but these errors were encountered:
When creating a Repository Content Selector privilege via the REST API, it's possible to set the action as "ALL" instead of specifying each action individually. For example, you can POST the following definition to the
/service/rest/v1/privileges/repository-content-selector
endpoint:However, when you view the privilege details in the UI, none of the actions appear as selected, which can be confusing. Despite the misleading display, the privilege seems to function as expected, allowing the intended actions to be performed.
Tested with Nexus 3.72 and 3.73
The text was updated successfully, but these errors were encountered: