Suppose your application accesses an AppServer and the following are true:
The same AppServer contains application components for download and business logic for your application.
The application detects that the security cache does not contain authentication information.
Note: These conditions occur when WebClient has not yet downloaded any as-needed application components from the AppServer.
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, as compiled (.r) files, in the WebClient installation at OpenEdge-Install-Directory\wcadd. If the CODEBASE-LOCATOR handle contains only some of the required values, these values can be passed into these routines as default values, allowing the user to fill in the remaining values.
When using the authentication dialogs, consider the following:
To make the dialogs look exactly the same as when WebClient invokes them, obtain the prompt input parameter from CODEBASE-LOCATOR:END-USER-PROMPT.
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.
After calling an authentication dialog, the application is responsible for setting the appropriate CODEBASE-LOCATOR attributes with the information obtained from the end user.
The same AppServer contains application components for download and business logic for your application.
