|
Problem(Abstract) |
When security is enabled on your server, your thick client
application receives a challenge dialog during the initial connection,
prompting for an id and password. Once dismissed, the application connects
and functions as expected. This also occurs regardless of you securing the
application. |
|
|
|
Resolving the
problem |
Problem Summary:
During the initial connection of your thick client application, a
challenge dialog is received asking for id and password. Once dismissed,
the application connects and functions as expected. Security is enabled
and you do not think that the challenge should be presented during the
initial connection. Also, if the application is actually secured, why is
it that you can get into the application without supplying an id and
password?
Solution:
There are two ways to resolve this issue:
- As long as security is enabled on your server, the client will prompt.
This is regardless of authorization policy of the application. If you do
not intend to secure the application, you can grant everyone access to
your application.
- You can disable prompt in client by disabling security in client
(through the sas.client.props file).
Note: You only gain access to resources with EVERYONE
access when server security is enabled. You do not get prompted whether
your application is secured or not, if you disable client security.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|