SecureLogin fails with .Net application

  • 7000472
  • 24-Feb-2009
  • 26-Apr-2012

Environment

Novell SecureLogin
NSL6.x

Situation

SecureLogin does not work with .Net application
NSL "Type" command does not enter credentials in dot net application
Unable to identify Windows control IDs
Control IDs change each time application is launched

Resolution

Use "type -order"  (this is preferred)
Use "type -raw"    

In most instances of .Net applications, the control IDs for the edit fields (UID
and Password) change/are generated with each new instance of the
program.  SSO enabling such applications is accomplished by using the "-order" tag on the "type" command rather than the standard control ID "#"
designation.

 
 

Additional Information

In order to identify the order of the various fields, use a script such as the following:

Type -order "1" #1
Type -order "22" #2
Type -order "333" #3
Type -order "4444" #4
Type -order "55555" #5

Feedback service temporarily unavailable. For content questions or problems, please contact Support.