Managing ISE Enabled Users

About ISE Enabled Users

Cisco Internet Script Editor (ISE) is an application for managing routing and administration scripts within the Cisco platform. Analytics can provide a layer of security to ISE scripts and resources. This requires the linking of Analytics user accounts with Unified CCE user accounts. 

ISE enabled users are Analytics users that are linked in this way. When the linked Unified CCE user runs ISE, Analytics security is applied to the scripts and resources so that the Unified CCE user is only able to access the ISE scripts and resources that the linked Analytics user is able to access.

There are two ways to create a linked Unified CCE and Analytics user so that eGain Analytics security can be applied to ISE scripts and resources:

  • Create the user in Analytics and specify that they should be ISE-enabled. Analytics automatically creates the linked Unified CCE user. 
    eGain Analytics Administration Guide, chapter Remote Resource Provisioning, section Partitioned Internet Script Editor.

  • If a suitable user already exists in Unified CCE, Analytics can automatically import it. They can then be configured as an ISE enabled user in Analytics.

For more information about configuring ISE to use eGain Analytics security and creating ISE enabled users, see eGain Analytics Administration Guide,

Configuring Imported UCCE Users for ISE Integration

This section describes the specific approach to creating users in Analytics who should be enabled for ISE. For general user creation, see Managing Users.

To configure an imported Unified CCE user for partitioned ISE access:
  1. Open the Tools Tools menu.

  2. Select Security > Users.

  3. In User Manager, select the folder in which you want to create the new user.

  4. Click the New option. The Create a New User page opens.

  5. Provide details for the following fields:

    • Login Name: Type a Login Name for the user. This must be unique across Analytics. The recommended format in order to ensure uniqueness is to use the person’s business email address.

      For users who access via Single Sign-on (SSO), the appropriate username formatfor the SSO system must be used. For example, for Windows login authentication, the login name must correspond to an existing Windows Active Directory user and must be formatted as <domain-name\username>, where <username> is the Window username and <domain-name> is the NetBIOS domain name. The login name must exactly match the details in the corresponding Active Directory entry.

      The ISE users are local, and the application no longer validates the login username and password against the Active Directory.

    • Optionally provide the following details:

      • First Name and Last Name

      • Email Address: Address for receiving notifications from Analytics.

      • Description: A description of the user or their role.

    • Culture: Select the user’s culture from the drop-down list. This determines their language, locale and date format.

    • User Home Folder: Select the User Home Folder. There are two options:

      Every user must have a designated Home Folder, although it does not need to be unique to that user. It does not need to be the folder in which the user is actually located. The Home Folder is the default location that most Analytics tools open to and save items into for this user. The user can change their Home Folder later in their User Settings.

      • If the folder already exists, you can select it directly. 

      • If the folder does not exist yet, you can select the path in which it should be located, and check the box marked Create a new folder for this user. The folder is created automatically under the selected folder, when the user is saved.

    • Advanced Mode: Check the box to grant the user access to Advanced Mode, which is required for dashboards, security management, full resource management and information notice management.

    • Account Enabled: Check the box to permit the user to login. If this is unchecked, they are not able to login even with the correct password.

    • Local Login Enabled: Check the box to permit local login. This is required for ISE enabled users. Provide further details:

      • Password and Confirm Password: For details on the password policy, see User Settings.

      • User must change password at next login: Check this box to force the user to change their password when they next access Analytics. This ensures that the password you have provided is temporary only.

      • Password never expires: Check this box if the password should be applicable indefinitely without needing to be changed. This should generally only be used for system accounts.

      • User cannot change password: Check this box to prevent the user from changing their password themselves.  

  6. Check the box marked Internet Script Editor Enabled.

  7. Optionally, check the box marked Create Another if you have more users to create. This keeps you in the creation screen after saving the current user.

  8. Click Save to save the user, or click Back to discard it and return to the list.

  9. Ensure that the user has permission to browse reportable resources in the folders containing the ISE scripts and resources. 

    • Typically this is done by making the user a member of one of the default groups, Basic Users or Advanced Users, which has permissions over the folder. For more details, see Groups.

    • Alternatively, you can use the Permissions tool to grant the user the Basic or Advanced folder role over the folder. For more details, see Permissions

Configuring Imported UCCE Users for ISE Integration

Existing Unified CCE administrator users are automatically imported into Analytics in a format which supports Internet Script Editor (ISE) partitioning. These Analytics users need to be configured before the corresponding Unified CCE users can use the ISE for partitioned editing.

To configure an imported Unified CCE user for partitioned ISE access:
  1. Open the Tools Tools menu.

  2. Select Security > Users.

  3. In User Manager, select the folder in which the user is located.

    The imported user is in your default import location unless you have moved the user after the import. The user name is formatted as  <domain-name\username>, where <username> is the Windows username and <domain-name> is the fully qualified Windows domain name. An example of an imported user name could be iseuser1@testdomain.local.

  4. In the list, find the user you want to edit and click their name. The user properties screen opens.

  5. Under the Details tab, check the box marked Account Enabled to enable the user.

  6. Ensure that the user has permission to browse reportable resources in the folders containing the ISE scripts and resources. 

    1. Typically this is done by making the user a member of one of the default groups, Basic Users or Advanced Users, which has permissions over the folder. For more details, see Groups.

    2. Alternatively, you can skip this step for now, save the user and then use the Permissions tool to grant the user the Basic or Advanced folder role over the folder. For more details, see Permissions.  

  7. Click Save to save the changes or click Back to discard any changes without saving.

  8. If your Analytics installation does not use single sign on, then before this user can be used to access ISE, you must log into Analytics as this user, and supply a password when prompted. This password must be the same as the password for the corresponding Windows active directory user. If your Analytics installation uses single sign on, this step is not required.

Related Information