-
Title
Switch the asset value in the connection string for Remote app auto-login to be the application asset rather than the application name -
Description
When making a request for an RDP application session, the connection string is incorrectly passing the "asset" variable using the Access Request Policy > Security tab > "Application Display Name" field rather than the actual asset name of the application asset.
A critical part of any remote application session is the OILauncher that is installed on the remote application host. The OILauncher not only launches the remote application, it also injects 3 parameters into an application's commandline before the remote application is launched. These 3 parameters are {username}, {password} and {asset}. The initial problem was that the Application Display Name was being sent through to the OILauncher as the injected {asset} parameter rather than the actual Application asset name. Keep in mind that when we are talking about an asset now, the asset isn't necessarily a platform or a piece of hardware. With remote application sessions there is a new kind of asset which is the application itself. (ie. Notepad, MySql client, Oracle client, etc.). When you define an asset with accounts to be used in an application session, the asset here is the application and the application (aka. asset) can have accounts associated with it.
Getting back to the problem. The Application Display Name is defined as part of the access policy on the Security tab.This is the value that was being passed in as the {asset} to the OILaunch, which was wrong. What should have been passed in as the asset is the actual application asset name as it was defined under asset management on the Asset Management->Properties->General tab.
-
Resolution
STATUS:
Change Request # 330917 will fix this issue in a future release of SPP versions 7.1 and 7.0.1 (subject to successful QA and Product Management Approval) so that the "asset" variable is passed correctly using the actual asset name of the application asset.
If a workaround was applied were depending on the value of the Application Display Name to be injected into the the remote application, that will be broken when you upgrade to SPP 7.0.1 \ 7.1.0. Therefore you will need to take the value that was in the Application Display Name and make it the actual asset name instead. -
Change Request
330917