Space characters and role permissions

Not applicable

Hi,

we're using custom roles to separate access to individual API Proxies and Products. This is giving us some headaches with regards to space characters in the name of either of those.

Whenever a Proxy or Product is created with a space character in the name (not the display name), Edge fails to grant proper permissions to the role that created the object. This is especially bad because the product that gets autogenerated when selecting "Publish API Product" from the API Proxy Wizard also creates a Product with a space character in its name.

There seems to be some mix-up with urlenconding somewhere, as a permission does get created, it just doesn't work.

The first and obvious effect is that the role cannot see or access the proxy or product. The second and more problematic issue is with the way Edge UI works: It will parse the permission and try to load the corresponding proxy or product. As the permission will not fit to the actual object, this call will fail and no more proxies or products will be loaded. This leads to incomplete lists in the Edge UI and randomly missing proxies and products.

The only solution we could find right now is to manually delete those erroneous via management API as deleting through the Edge UI also doesn't work.

Is this a known issue, is there a fix on the horizon and are there any known workarounds?

Regards,

Philipp

0 3 198
3 REPLIES 3

Hi @Philipp Schleier - I'm assuming this is cloud. If you're on-prem, please let us know the version you're on.

This is a known issue (MGMT-2695), but I've added this post to the ticket so show how it's affecting RBAC. Thanks for posting!

Thanks for you answer, @Floyd Jones. We're running on-prem v4.17.01.

Thanks for that, @Philipp Schleier. Meantime, underscores are probably already your new friend. :]