Remove unwanted resource path and permission in custom role

nandishnandy
Participant III

Hi Guys,

I have created custom role which contains unwanted resource path and permission as shown in below.

I want to remove or delete below resource paths in the custom role through management API call, please suggest how to proceed.

{
"organization" : "xxxx",
"path" : "/developers",
"permissions" : [ ]
}, {
"organization" : "xxxx",
"path" : "/companies",
"permissions" : [ ]
}, {
"organization" : "xxxx",
"path" : "/applications",
"permissions" : [ ]
}, {
"organization" : "xxxx",
"path" : "/apiproducts",
"permissions" : [ ]
}, {
"organization" : "xxxx",
"path" : "/reports",
"permissions" : [ ]
}, {
"organization" : "xxxx",
"path" : "/apps",
"permissions" : [ ]
}, {
"organization" : "xxxx",
"path" : "/apps/*",
"permissions" : [ ]
}, {
"organization" : "xxxx",
"path" : "/developers/*/apps",
"permissions" : [ ]
}, {
"organization" : "xxxx",
"path" : "/developers/*/apps/*",
"permissions" : [ ]
}, {
"organization" : "xxxx",
"path" : "/companies/*/apps",
"permissions" : [ ]
}, {
"organization" : "xxxx",
"path" : "/companies/*/apps/*",
"permissions" : [ ]
}

Thanks In Advance

Nandeesha

1 8 1,293
8 REPLIES 8

HI @Nandeesha

Delete Permission for Resource Management API is what you need

Thanks,

Not Permission for Resource, the permissions already empty, i want to delete unwanted resources as shown in below.

{
"organization" : "xxxx",
"path" : "/developers/*/apps",
"permissions" : [ ]
}

Thanks In Advance

Hello @Sai

Is there a way to delete muliple permissions(get, put, delete) in single curl.

Thanks

estebansp
Participant II

Hi @Nandeesha

I think you can't do that. When you create an empty custom role in Edge, it assigns a bunch of empty resources, and a few other with just get permissions.

This just a empty list of resources that you can assign get, put, or delete permissions later on if needed to. But leaving them empty is harmless.

Regards,

Hi @Nandeesha - I checked with our engineering team, and here's what you need:

/v1/o/{org}/userroles/{role}/permissions?path={path}&delete=true"

Be sure to URL encode slashes & wildcards. For example, /floyd is %2Ffloyd.

Apologies for not having this in the docs. We're going to add it.

Thanks for your patience, and ping us back if you have any trouble with that call.

(Thanks for the info, @Rampradeep Krishnamurthy!)

Thanks its working as expected.

Working for me too. The http method to use is DELETE

Former Community Member
Not applicable

@jonesfloyd this is still not updated in the doc