SSO invocation of TDV Studio should auto-detect the username of the invoker

Background / Issue Description

This is current as of TDV Studio 7.0.7.

We were advised to use the following CLI mechanism to invoke SSO based login to Studio:

C:\Program Files\TIBCO\TDV Studio 7.0.7\bin\studio.bat" -ide -server={hostname} -port={port} -userName=" " -password=" " -domain={our_domain}

In combination with an appropriate krb5.properties file, this CLI allows studio to start up, skip the login prompt, and immediately present the user with the designer UI. This works as expected.

However, passing -userName = " " causes the persistence files in .compositesw to be missing the username of the user - studio.properties contains lines that resemble:

{blank_value}.{domain}.{server}.{port}.resources={persistence data in XML format}

this causes user persistence data (i.e, open resource tabs) to be lost when Studio is re-launched. 

Removing the -userName and -password arguments results in a similar, equally problematic behavior: all entries get written as though they are associated to the admin user:

admin.composite.{server}.{port}.resources={persistence data in XML format}

As the majority of our users do not use the admin ID, this is not ideal. 

Currently, the workaround for this is to hardcode the username, e.g:

C:\Program Files\TIBCO\TDV Studio 7.0.7\bin\studio.bat" -ide -server={hostname} -port={port} -userName="{username}" -password=" " -domain={our_domain}

this works, but makes it difficult to generalize the single-sign on invocation (we currently use a C# wrapper that detects the current windows username, and populates the value - this is an acceptable short term workaround). 

Support has advised us that both behaviors are by design. 

Enhancement Request

We would like to request that Studio be enhanced to allow for SSO without hardcoding the username, while also maintaining the ability to store accurate username based preference entries. Preferably, SSO would not require specifying -userName or -password at all. 

It would be acceptable for this to be a new command line parameter (-sso , for example).