Custom Menu Restrictions

I am interested in finding way to control what custom pull-down menu options a user has access to execute? I am aware that I can restrict access by the role, but what if only specific users within that role should have access to the option. Such as in the case where the custom pull-down menu item is specific to one team rather then all users in the role.

Thanks in advance for your help.
%david

Find more posts tagged with

Comments

james1

I don't know of a way to restrict the appearance of a custom menu item according to username or group. However, you could add the menu item for a particular role, and then have your CGI program check the username (and group memberships), and if the menu item doesn't apply, then you can just put up a "Sorry, go away" message.

Hope this helps.
-- James

Migrateduser

You may consider creating a username accesss config file and having your CGI consult it. This would allow you to easily add/remove users.

John Narbaitz
john.narbaitz@interwoven.com
Senior Sales Engineer
Interwoven

tvaughan

I implemented this by a blatant rip off of the available_templates.cfg, available_templates.ipl and available_templates.dtd file.

If you check out the IPL, you'll see very quickly a way to modify it so that you can set up ACLs for any given menu item. The architecture, simply is:

1) User selects a menu item CGI that parses their username, role, and vpath.

2) The CGI asks your version of available_templates.ipl what set of resources that (uid, role, path) tuple is authorized for.

3) The CGI forwards the parameters to an appropriate "worker" CGI.

Tom

Migrateduser

As long as you already have all of this logic in place, you could have a single custom menu item (something like "Other...") that brings up a window with just those options that are available to the current user, role, path, etc.

It would probably make for a nicer user experience if only the available options were shown.

Brinko Kobrin
Interwoven Staff Engineer