Try OpenEdge Now
skip to main content
WebClient Applications
Designing Security : Single sign-on and security caching : Using WebClient logon dialogs in your applications

Using WebClient logon dialogs in your applications

Suppose your application uses the same AppServer for application components downloads and for accessing business logic, and suppose further that an application needs to access the AppServer before WebClient downloads any As Needed application components from the AppServer. (An application can determine this because the security cache does not contain authentication information such as user IDs or passwords.) As a result, the application must prompt the end user for the logon information. To do so, your application can display the security dialogs that WebClient uses, providing the end user with a consistent interface.
For information on calling the authentication dialogs that WebClient uses from the application, see the Using WebClient's authentication dialogs .