Checked with Shankar. The issue occurs with sign-only scenarios in
WSAS-nightly builds. It worked fine with UT ploicies. Also, this is a
regression issue in WSAS nightlies. Security config persists properly in
last WSAS release (2.2.1)
regards
Charitha
Charitha Kankanamge wrote:
Hi Samisa,
Samisa Abeysinghe wrote:
Afkham Azeez wrote:
The changes are persisted to the WSAS DB, so when you restart it, it
will be automatically applied.
I just tried this again, but it does not seem to work. I have to
re-enable sec on the service :(
I tried with WSAS-Snapshot on winxp/jdk15 and security configuration
was persisted once I restarted the server (either through UI or just
pressing ctrl+C).
Steps
=====
1. Logged in to WSAS management console
2. Select a service
3. Applied UT over https scenario
4. Restarted the server
5. Accessed 'Security Configuration' page again
Can you please let us know which WSAS version you are trying and the
exact steps to reproduce the issue?
Thanks,
Samisa...
Azeez
Samisa Abeysinghe wrote:
How can I ensure that the security config that I applied to a
service would be available when I restart the server?
Thanks,
Samisa...
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG. Version: 8.0.100 / Virus Database: 269.24.0/1459 -
Release Date: 5/21/2008 5:34 PM
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
