Progress
on the Web


Using WebClient’s Authentication Dialogs in Your Application

Suppose your application needs to access the AppServer and the following are all true:

To access the AppServer in this situation, your application can prompt the end user for security items by displaying the security dialogs that WebClient uses. This provides the end user with a consistent interface.

These routines reside, in the form of procedure (.r) files, in the WebClient installation at $DLC/wcadd, where $DLC represents the Progress installation directory.

NOTE: To make the dialogs look exactly the same as when WebClient invokes them, obtain the prompt input parameter from CODEBASE-LOCATOR:END-USER-PROMPT.

NOTE: Before calling an authentication dialog, the application is responsible for obtaining the relevant attribute values from the CODEBASE-LOCATOR handle to pass to these routines. For example, the value of NOT PERSISTENT-CACHE-DISABLED should be passed for the second parameter, enable-persistent-checkbox.

Also, if some but not all the required values are available from the CODEBASE-LOCATOR handle, they can be passed in as default values, allowing the user to fill in the remaining values.

NOTE: After calling an authentication dialog, the application is responsible for setting the appropriate CODEBASE-LOCATOR attributes with the information obtained from the end user.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095