Custom menu item restriction in TS6.1

Hi All,

I am using TS6.1 in Solaris. My project uses LDAP for maintaing groups and the same is used for providing restrictions to WA access.

Similarly I need to provide restriction to file dropdown menu items in my TS based on the group access.

In iw.cfg I have provided the entry like the below mentioned one.
custom_menu_item_dcr_metadata="File", "Set DCR Metadata", "setDCRMetadata.cgi","editor,master,admin", "scrollbars=yes,resiza
ble=yes,width=640,height=545"

Currently I need to make this 'Set DCR Metadata' value to be visible only to google_editor group which is already existing in LDAP.

PLease help me in providing your valuable suggestion as I have got struk up in this level.

Regards,
Varun.K

Find more posts tagged with

Comments

Adam Stoller

Hi All,

I am using TS6.1 in Solaris. My project uses LDAP for maintaing groups and the same is used for providing restrictions to WA access.

Similarly I need to provide restriction to file dropdown menu items in my TS based on the group access.

In iw.cfg I have provided the entry like the below mentioned one.
custom_menu_item_dcr_metadata="File", "Set DCR Metadata", "setDCRMetadata.cgi","editor,master,admin", "scrollbars=yes,resiza
ble=yes,width=640,height=545"

Currently I need to make this 'Set DCR Metadata' value to be visible only to google_editor group which is already existing in LDAP.

PLease help me in providing your valuable suggestion as I have got struk up in this level.

Regards,
Varun.K

Please read the TeamSite User Interface Customization Guide - custom menus are no longer handled within iw.cfg.
That aside, I do not believe group restrictions for custom menus exists in 6.1 (perhaps in 6.7.1 though I don't see that in the manual right now) - so I believe the only way to restrict it by group is within the code for the custom menu item itself - i.e.: the custom menu item is visible for all, but when run it checks the groups that the user belongs to and if they don't belong to the desired group it can display an error message indicating as much.

chicka

Hi Fish,

Thanks for your prompt reply.

I have already implemented the restriction in my code. But here the problem comes. When my menu item is selected, I am calling a CGI and at the same time it is checking the access restriction. So if a particular userid does not belong to the specified group, he get a popup with an error message and at the same time he is able to see the CGI in the background.

I want to know is there anyway to supress the CGI which is called and thereby providing the unauthorized users with a single popup containing error message.

Appreciate your help.

Adam Stoller

I have already implemented the restriction in my code. But here the problem comes. When my menu item is selected, I am calling a CGI and at the same time it is checking the access restriction. So if a particular userid does not belong to the specified group, he get a popup with an error message and at the same time he is able to see the CGI in the background.

What does "see the CGI in the background mean?

I want to know is there anyway to supress the CGI which is called and thereby providing the unauthorized users with a single popup containing error message.

Without knowing more about what you mean, and how you wrote the CGI code - I cannot answer this.

ISCBorisB

Hi Fish,

Thanks for your prompt reply.

I have already implemented the restriction in my code. But here the problem comes. When my menu item is selected, I am calling a CGI and at the same time it is checking the access restriction. So if a particular userid does not belong to the specified group, he get a popup with an error message and at the same time he is able to see the CGI in the background.

I want to know is there anyway to supress the CGI which is called and thereby providing the unauthorized users with a single popup containing error message.

Appreciate your help.

There is no need to *suppress* CGI, whatever that could possibly mean. All CGI output is generated by your code. You should be able to control it completely.
So, validate access rights first and fork your code to generate only one of the two mutually exclusive Pages, either "Access Denied" or "Go Ahead, do it..." Page