Hi All,
I was using a token which contains more than user name and password. I
was doing
token = CustomToken(name, pass, age);//my class
RequestSoapContext.Security.Tokens.Add(token);
RequestSoapContext.Security.Elements.Add(new MessageSignature(token));
with this it was working fine in WSE2.0, could someone help me convert
this to WSE3.0? or point me to a document I can read to convert this
one?
Thanks.
Pablo Cibraro - 02 Jun 2006 15:17 GMT
Hi,
In order to do the same in WSE, you need to use a custom security assertion.
I wrote an small article about that topic in my blog,
http://weblogs.asp.net/cibrax/archive/2005/07/19/419921.aspx .
You can find more examples in the WSE quickstarts.
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
> Hi All,
>
[quoted text clipped - 10 lines]
>
> Thanks.
DBC User - 02 Jun 2006 15:57 GMT
Thanks Pablo,
As I was reading I noticed we need to use the policy at both ends. Is
it true? Since the web side they are still using the requestsoapcontext
and they say it seems to be working. So If I change the client side
code to use policy will I break anything?
Thanks.
> Hi,
>
[quoted text clipped - 21 lines]
> >
> > Thanks.
Pablo Cibraro - 02 Jun 2006 17:26 GMT
Hi,
No, the client and service are independent.
If you change the client to use a policy, the service should work as long as
the client policy uses the same custom token.
Regards,
Pablo.
> Thanks Pablo,
>
[quoted text clipped - 30 lines]
>> >
>> > Thanks.
DBC User - 02 Jun 2006 18:46 GMT
Thanks Pablo. I am new to Policy and how to use it. Is there any
documentation I can read and understand??
> Hi,
>
[quoted text clipped - 39 lines]
> >> >
> >> > Thanks.
Pablo Cibraro - 05 Jun 2006 15:23 GMT
Yes, this is best article I found. It was written by Tomasz Janczuk, one of
the WSE developers.
http://msdn.microsoft.com/msdnmag/issues/06/02/WSE30/
Regards,
Pablo.
> Thanks Pablo. I am new to Policy and how to use it. Is there any
> documentation I can read and understand??
[quoted text clipped - 46 lines]
>> >> >
>> >> > Thanks.
DBC User - 05 Jun 2006 16:10 GMT
Gracias Pablo.
> Yes, this is best article I found. It was written by Tomasz Janczuk, one of
> the WSE developers.
[quoted text clipped - 54 lines]
> >> >> >
> >> >> > Thanks.
UserNameToken - 16 Sep 2006 21:52 GMT
> Hi All,
>
[quoted text clipped - 10 lines]
>
> Thanks.
We are trying to upgrade our existing app from WSE2.0 to WSE3.0 we are not able to add the UsernameToken to Context object of our webservice we had done the same thing using WSE2.0 it was working. but in WSE3.0 it breaks,following is my code
public string CreateAuthenticationToken(string strEncryptedUserName, string strEncryptedPassword)
{
//Microsoft.Web.Services3.Security.Tokens.UsernameToken userToken = new Microsoft.Web.Services3.Security.Tokens.UsernameToken(strEncryptedUserName, strEncryptedPassword, PasswordOption.SendHashed);
UsernameToken objUserToken = new UsernameToken("admin", "admin");
//Security security = null;
GateKeeper proxy = new GateKeeper();//our Websservice
SoapContext context = wservice.RequestSoapContext;
try
{
//proxy.r
context.Security.Tokens.Add(objUserToken);
return "AAA";
}
catch (Exception strException)
{
throw (strException);
return strException.Message;
}
}
Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.
Pablo Cibraro [MVP] - 18 Sep 2006 14:59 GMT
WSE 2.0 and WSE 3.0 use different ways to configure the web service
security. WSE 3.0 uses a set of pre-defined scenarios for security.
You can configure one of these scenarios through a WSE policy file or code
(Or using the WSE wizard).
In your case, you need to configure a UsernameOverTransport turn-key
scenario, in other words, "Authentication by means of a Username token".
Take a look to this article for more information,
http://msdn.microsoft.com/msdnmag/issues/06/02/WSE30/
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
>> Hi All,
>>
[quoted text clipped - 45 lines]
> Posted from http://www.topxml.com/renntp using reNNTP: the website based
> NNTP reader.