Configuring Integrated RunAs

Applications that support Integrated Windows Authentication (IWA) typically do not have native login screens. As a result, you cannot create an Imprivata SSO profile for these types of applications and deploy it to users of shared kiosk workstations.

Imprivata OneSign Integrated RunAs provides an alternative to an SSO profile, and as such, lets you extend Imprivata SSO to applications that use IWA.

Beginning with Imprivata OneSign 6.2, the ISXRunAs command line utility (ISXRunAs.exe) is installed with the Imprivata agent. This utility lets you configure a custom shortcut that lets an authenticated user:

  • Launch and run an IWA enabled application under their user profile, instead of the local (generic) Windows user on the shared workstation.

  • Access network resources, such as mapped drives and network printers, from within the application.

Requirements

Imprivata OneSign Integrated RunAs is included with the Imprivata OneSign Single Sign–on (SSO) license. In addition to being licensed for SSO:

  • Users must be a member of the Microsoft Active Directory (AD) domain that is synchronized with the appliance.

  • The domain in which the Imprivata OneSign users are members must have a trust relationship with the endpoints domain.

  • Non–AD users, including those that are part of an Imprivata Directory, are not supported.

Before You Begin

Verify that IWA is functioning normally in your Windows environment, independent of Imprivata, before you begin.

Support for IWA extends to an environment and applications that are already configured to support IWA.

About the ISXRunAs Utility

The ISXRunAs utility is a command line tool that is installed with the Imprivata agent. The default location of the utility is:

  • 64–bit — C:\Program Files (x86)\Imprivata\OneSign Agent

This utility lets you configure custom shortcuts that let an authenticated user:

  • Launch and run an IWA enabled application under their user profile, instead of the local (generic) Windows user on the shared workstation.

  • Access network resources, such as mapped drives and network printers, from within the application.

The following describes the syntax for this command:

ISXRunAs [/noprofile | /profile | /netonly] program [optional program parameters]

Parameter Description
/noprofile

Specifies that the user's profile should not be loaded when the application is launched.

The application runs under the authenticated user, but the default user profile is loaded to the application.

/profile

This is the default parameter.

Specifies that the user's profile should be loaded when the application is launched.

The application runs under the authenticated user.

/netonly

The application runs as the generic Windows user.

However, the token of the authenticated user is used to access network resources, such as printers or network shares.

program

The full path to the application executable.

This path can also include optional parameters that are specific to the application.

NOTE: Valid usage of the profile parameters is determined by the application. For example — if an application is designed to require the user's profile, it cannot be launched in /noprofile or /netonly mode.

Deploy a Custom Shortcut to Workstations

A custom shortcut can be deployed to:

  • A single workstation manually

  • Multiple workstations through a group policy object (GPO)

The same shortcut can be deployed to single–user computers and shared kiosk workstations. Consider the following behavior:

  • Single–user computer — The application launches normally as the local Windows user.

  • Shared kiosk workstation — Non–AD users and users without an SSO license continue to have access to the application, but it runs under generic Windows user. Subsequent behavior is application specific. For example, some applications may launch and immediately exit, while others may display a warning message or prompt for credentials.

Reporting

You can use the User Activity, Computer Activity, and Application Activity reports to determine which applications have been launched using ISXRunAs.

NOTE: For more information about managing reports, see Using Reporting Tools.

Troubleshooting

Symptom

Running the desktop shortcut does not work.

Solution

Be sure that the target path of the shortcut is configured with the proper syntax. For more information, see the provided examples.