Programmatic logins do not automatically propagate security credentials to all threads, beginning in V4.0.2
 Technote (FAQ)
 
Problem
If you use programmatic logins in your security implementation on WebSphere® Application Server V4.0.1, upgrading to a newer release of V4.0 might cause unexpected problems. Beginning in V4.0.2, the security credentials are no longer propagated to every application thread; this might result in unexpected login prompts that display during your application's runtime.
 
Solution
The three basic types of logins are:
  • prompt logins
  • properties logins
  • programmatic logins.

Prompt and properties logins are designed to provide an automatic credential to each thread.

In V4.0.1, the programmatic login incorrectly propagated the credential to every thread associated with the process. After V4.0.1, the programmatic login was designed to NOT propagate the credentials to each application thread associated with the process. The programmatic login logic can determine whether to set different credentials on each thread, if necessary.

From a usability standpoint, it is not possible to have such precise control using a prompt or properties login.
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Security
Operating system(s): HP-UX
Software version: 4.0
Software edition:
Reference #: 1145492
IBM Group: Software Group
Modified date: Jan 19, 2004