Security Setup Problem With WAS V 3.5

We have tried to set-up the WebSphere Security as described in the Version 3.5 handbook but was not able to configure it successfully.
We tried Basic Authentication as described in the handbook
we were not able to get WAS to work. Similarly for Client Authentication we have set-up directoy service using SecureWay but we were not successful.
In both instances, after configuration we will restart the default server and found that the security policy had not taken effect. For example, after configuration of Basic Authentication or Client Authentication , we down and re-start the default server from Admin console, the browser does not prompt for user name and password , nor client certificate.
However when we down the IBM AdminServer service and tried to re-start it we encounter problem with the starting of the Admin Service. We had to re-install WAS to in-order to try again.
Has any one out there able to configure client authentication witb WAS 3.5 successfully ? If there is, I hope that you can share your experience.

For 3.5 you can use OS or LDAP server to config you security. Try OS if you have the are the root on Unix. If you don't want to use OS the LDAP server form IBM you mentioned is also fine. Make sure you configured security the right way. If your admin server cannot find LDAP server or the password or user name for LDAP server is not right, you cannot start the application server.
Client side login is another issue. There is a class called LoginHelper. You need it. Also, sas.client.props in properties folder you need this also. When you run your client make sure to use system property to specify the location your props file. This is a complex topic. I don't think you can get a thorough answer from me by posting messages. Read the document at IBM web site carefully. It is doable. I am using it every day on both 3.5 and 4.0.

Hi Joel,
did you find the solution of your problem.
If yes, could you explain me what to do:
After configuring and when i restart the server
the security policy had not taken effect.
Thanks
barry