Corporate scripts are normal scripts that are assigned to a Container object instead of to a User object.
Because they are automatically rolled out to all User objects held in the Container object, corporate Scripts simplify implementing and administering SecureLogin single sign-on. By using this method, you don't have to configure applications for each individual user in your organization. All users read and use the same scripts.
Windows Application, Web, Startup, and Terminal Launcher scripts can all be implemented as corporate scripts.
In a Microsoft ADS environment, use the Microsoft Management Console (MMC) to create corporate scripts. In an NDS or eDirectory environment, use ConsoleOne to create corporate scripts. This section describes how to use ConsoleOne.
Log in as Admin.
In ConsoleOne, navigate to the Container object where you want to create the corporate script.
Right-click the Container object, then click Properties.
Select the Novell SecureLogin tab, then click New.
Select New Application, enter the executable name of the program that you want to create a script for, select the script Type, then click OK.
Double-click the new application in the application list.
Select Script, then type the script into the text box.
Browse the NDS or eDirectory tree and select a User object that is within the Container object that you just created the corporate script for.
Right-click the User object, then click Properties > Novell SecureLogin.
The User object has inherited the corporate script. Corporate scripts are distinguished from local scripts in the list by a small black triangle in the lower left-hand corner of the icon that sits beside the application name.
Exempting a User Object from a Corporate Script
Local scripts take precedence over corporate scripts. Occasionally, you might want a particular user to use a different script to the corporate script for a particular application. To do this, create a local script for the application at the User object level.
If you have a corporate script for an application, and you have a user that should not have that application single sign-on enabled, create a blank local script for the application at the User object level.
You can also use this procedure to exempt a Container object from corporate scripts inherited from Container objects that are higher in the directory tree.
