Re: WSE 2.0 SP2: UsernameTokens must be encrypted to request SCT?
From: Sidd (ElCid_at_hotmail.com)
Date: 02/15/05
- Next message: William Stacey [MVP]: "Re: WSE 2.0 SP2: UsernameTokens must be encrypted to request SCT?"
- Previous message: SA: "Re: UserNameToken with SendNone on Password"
- In reply to: SA: "Re: WSE 2.0 SP2: UsernameTokens must be encrypted to request SCT?"
- Next in thread: William Stacey [MVP]: "Re: WSE 2.0 SP2: UsernameTokens must be encrypted to request SCT?"
- Reply: William Stacey [MVP]: "Re: WSE 2.0 SP2: UsernameTokens must be encrypted to request SCT?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 15 Feb 2005 13:36:20 -0800
Hi William,
Yes the article is accurate in its description about using a
UsernameToken to sign the initial RST. In WSE2 SP2 we require the client to
have encrypted the username token somehow, either with a Servers Cert, or
with https, but sending a plain RST signed with a username token in plain is
bad news and many people were doing it.
Offcourse there are ways to work around that. Currently, the check is
made both at the client and the service, and as always you can override the
default behavior to disable this checking.
Hope this answers your question.
Thanks,
Sidd [MSFT]
"SA" <informatica@freemail.nl> wrote in message
news:eAP5CjFEFHA.464@TK2MSFTNGP15.phx.gbl...
>
> >
> > If it does not matter, then don't even require a password or security.
> Just
> > keep it open. If it does require security, then don't use UTs unless
you
> > are using SSL or have a SCT and can encrypt them. If you can't use
certs
> to
> > get a SCT, have a look at my post on using just the public rsa key to
get
> a
> > SCT at
> >
>
http://spaces.msn.com/members/staceyw/Blog/cns!1pnsZpX0fPvDxLKC6rAAhLsQ!303.entry
> >
> Interesting article, thanks. Need to work my way trough it (and all
previous
> ones...), but basically you're using a key file made with the StrongName
> tool? Good idea...
>
> I meant actually that we need to keep track of logins for "auditing" and
> it's not a public web service either. So, we need some authentication
> mechanism. Some customers might be able to use Kerberos or X.509, but most
> won't. (this is for development of a commercial product)
>
>
- Next message: William Stacey [MVP]: "Re: WSE 2.0 SP2: UsernameTokens must be encrypted to request SCT?"
- Previous message: SA: "Re: UserNameToken with SendNone on Password"
- In reply to: SA: "Re: WSE 2.0 SP2: UsernameTokens must be encrypted to request SCT?"
- Next in thread: William Stacey [MVP]: "Re: WSE 2.0 SP2: UsernameTokens must be encrypted to request SCT?"
- Reply: William Stacey [MVP]: "Re: WSE 2.0 SP2: UsernameTokens must be encrypted to request SCT?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|