Sanjay, I have a case but I don't have it configurued. That's why I said I am intrested in an answer. Now that I reviewed my queries in the past I see it was Neethi/C that doesn't support alternatives yet. Appologize for the confusion.
Best Regards, George -----Original Message----- From: Sanjay Vivek [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 12:01 PM To: [email protected] Subject: RE: Editing the services.xml to allow both Basic Auth and Rampart auth. Hi George, You mentioned how you have a user case scenario of UsernameToken + Basic Auth. How did you go about configuring this? Could you attach your policy.xml for this scenario pls? It would be very helpful in my user case scenario. I think you misunderstood me about the alternative policies. A single policy can support one or more policy alternatives as described at http://wso2.org/library/3132 Cheers Sanjay -----Original Message----- From: George Stanchev [mailto:[EMAIL PROTECTED] Sent: Mon 21/04/2008 17:38 To: [email protected] Subject: RE: Editing the services.xml to allow both Basic Auth and Rampart auth. I also have similar use case scenarios - besides the username token+basic auth, I have Username token + saml token (either can be supplied). Last time I checked Neethi did not support alternative policies. I am not sure if that has been improved. I am also intrested in an answer. ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **********************************************************************
