A Forum reader recently asked:

“I’m trying to SSO into a homemade application that has a user/password field and an OK button, as usual. It fails, and SSO can’t push the user/password correctly; it looks like the dialog ID of the three fields are changing everytime the app starts. Is there another way to fill the credentials without the dialog ID, such as picking up the first text box available?”

And here’s the reply from SecureLogin expert David Guest …


This normally happens when an application has been developed without specifying the Ctrl-ID’s inside the code.

We get around this by using the “keyboard” within NSL. Normally, the cursor is found in the first field, and there is a TAB between the fields. In that case, the following should work:

Type $Username
Type \T
Type $Password
Type \T
Type $OtherField
Type \T
Type \N

You may find that you don’t need the last “Type \T” if the OK button is the default for the Enter key.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

No Comments
By: dguest
Nov 8, 2006
12:00 am
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow