HealthCast

To open the Administrator Application:

Organization Map

The Organization Map frame is located in the upper left-hand portion of the application screen. This frame contains the Organization Map, which lists the control items (applications) and the roles that have access to them.

Typically, only one level of control items is used. Each application can be listed separately under the root level. Roles can then be associated with each application. Alternatively, a number of applications can be put under a larger control item (access privileges cascade down to the lower level control items). The way the Organization Map is set up must be carefully considered in regard to how your organization works.

Click on the (+) to expand the list. Sub-items will be displayed. Under each control item or application is an item named “Roles”. Control items under the “Roles” item are the roles that have access to this application. Click on the (+) beside the “Roles” item to see these roles. For each role listed, you can click on the (+) to see the users associated with the role. Both XA and non-XA users are displayed.

Non-XA users are users who are associated with the Directory Service that have not been added to ExactAccess.

Applications Frame

The Applications frame is located in the upper right-hand portion of the application screen. It contains the list of applications that are registered in XA.Applications must be registered in XA before they can be used within the Administrator tool. Register all appropriate applications before continuing. If sub-control items are available, they may be displayed by clicking on the (+). Using the mouse, applications may be dragged over to the Organization Map frame and dropped into place.

Options are available to create application links from the context menu of the Organization Map. Right click on the Applications frame to view available options.

Select "Enable New Application..." to add a new application to the list.

Four application types have been added to the Snap App window (Enable Application):

The new functions of Snap App allows for shortcuts, file links and executable applications to be dropped on the configuration window. This enables them to be configured with default information respective of the type selected (Web, Windows, Link and Library).

Registering a published application with PubLancherSF

See Snap-App in action.

Example of creating a Web Snap-App

Example of creating a Windows Snap-App

Check "Active Directory Passthrough" to indicate that the username and password will use the passthrough credentials for the application, rather than storing them in the ExactAccess server.

This defines the way in which a user name will be passed to an application that requires Active Directory Passthrough.

The display name is what will appear on the ExactAccess Desktop presentation. You may specify a short and long name by separating them with the pipe (|) character. Ex: Short|Followed by a long name. The short name will be displayed directly on the desktop, while the long name will be used as a hover hint that will pop up when the mouse is placed over the link. See Application Registration for importing an XML file for Connectors that have been modified with these properties.

For Snap-App applications, this field will change depending on the type of application being defined:

The application executable is the name and extension of the file to be launched without the path specified. Ex: xaGeneric.exe

The Application ID is a Globally Unique Identifier (GUID) that will uniquely identify this application in the system. If you are creating a Connector for a specific application, and the application requires parameters such as username and password, your Connector must know this value in order to retrieve the associated parameter values for a user at log-in time. Snap-App applications automatically handle acquiring this ID during startup.

Similar to the Create application option above, an administrator may edit the application. All fields with the exception of the application ID be edited after the application information has been created. Once defined and saved, the ID cannot be modified.

Applications may be deleted, but they first must be removed from the Organization map. Once there are no further links to the application on the organization map, the application and parameters can be deleted from the applications list.

Roles Frame

The Roles frame is located in the lower left-hand portion of the application screen. It shows the roles that are associated with the Directory Service. Using the mouse, roles may be dragged to the Organization Map frame to associate groups of users with applications. The count above the frame is the number of roles found in the configured directories.

All Users Frame

The All Users frame is located in the lower right-hand portion of the application screen. It shows the users that are associated with the Directory Service. Right-clicking on a portion of the list will display a pop-up menu with several options. The count above the frame is the number of users found in the configured directories.

Users may be filtered to show only those users that have been activated in ExactAccess. Press the filter button to the right of the GO button.

Search Without user filtering

Search after user filtering applied

To be available for XA users, applications must be registered with XA. The registration process includes:

Application Registration

The below is a typical example of an XML document used to register an application with ExactAccess. The "name" attribute may be modified to provide both a short and a long name.

Example XML Expand source

<!-- SERVER XML FILE; Used for registering wrapper with XA. -->
<controlitems>
   <!-- 
    CONTROL ITEM: 
      id: Uniquely identifies application with XA;  
      name: The name that is displayed on the XA desktop;  
      desktoplink: The exe that is launched by XA, which in turn launches the application. 
    -->
   <controlitem id="{41763644-DE4C-4D30-BDC5-D07489689E16}" name="short|long name designation" kind="" desktoplink="application.exe">
      <params>
         <param name="username" ismasked="False" default=""/>
         <param name="password" ismasked="True" default=""/>
      </params>
   </controlitem>
</controlitems>

Adding an Application to the Organization Map (XA)

Once an application has been enabled and registered within ExactAccess, it will appear as a Control Item in the Applications Frame and is available to click-and-drag onto the Organization Map.

Assigning a Role to an Application

To assign a role to an application:

All of the users within that role will have access to that application. Continue to give access to that application to as many roles as desired. Also, you may give a single role access to as many applications as desired.

Setting an Application’s Parameters

Application parameters are established at the time an enabled application is registered within ExactAccess. Application parameters are any information that an application needs in order to login (or log off) a user. Parameters include items such as username, password, group identifiers, URLs, etc.

Application parameter values can be configured at the application level as “default values” in which case these values will apply to all users/roles that are granted access to the application.

Adding a Role to ExactAccess

All of the roles associated with the Directory Service are available in the Roles frame of the Administrator application. To add a role to ExactAccess:

Removing a Role from ExactAccess

Adding a User to ExactAccess

Users that are set up in your Directory Service are displayed in the All Users frame. To have access to XA-registered applications, users will need to be added to XA.

Removing a User from ExactAccess

Default User Access

Users need to be assigned permissions within the Administration area to access their applications and certain features within ExactAccess. For example, a user’s role could be added to the “SDK: Edit a Control Item Parameters” control item to give them permission to change/update their passwords within the application when prompted to do so. ExactAccess users need to be a part of this control item. Without it, they cannot perform general functions such as retrieving parameters for their applications, locking, and logging off.

Giving a user access to general functionality

Setting User Parameters

User parameter values are required for a user to login to an application. For example, passwords and usernames are values that a user would need to access an application. Application parameters are defaults for all users that have access to an application. User parameters are specific to each user.

The application Connector determines whether or not the ExactAccess Administrator is required to enter the actual values in the administration environment for first-time use.

Setting User Parameter Values

User and role values are cached within the ExactAccess Administrator application. When users or roles are added to the Directory Service and you want the changes to be reflected immediately within the Administrator application, you must refresh the server. To do so:

Organizational items are control items created by the administrator (using the administrator tool) for the purpose of organizing applications into logical groupings. These items may only be created in the Applications frame under the “ExactAccess Administrator” application control item.

Creating a New Organizational Item:

Search Criteria

When entering search criteria, the wildcard asterisk (*) can be placed at the beginning or end of the data to indicate finding any item containing the specified string.

Search strings are not case-sensitive.

Given the domain names as ADDOMAIN, DOMTEST the following examples show searching for roles or users in these domains: