Re: establishing a security context using usernameForCertificateSecurity
- From: "Pablo Cibraro [MVP]" <pcibraro@xxxxxxxxxxx>
- Date: Fri, 11 Aug 2006 16:47:13 -0400
Yes, it could be ok as long as you secure that password (Using DPAPI for
example).
Anyway, you are still performing authentication by means of password
comparison. (I prefer to use the windows authentication since I do not need
to keep the user password).
Regards,
Pablo Cibraro.
"gbier" <george.bier@xxxxxxxxx> wrote in message
news:1155141978.702137.32420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks Pablo,
Your truly are "the man" when it comes to WSE!
If the MS patterns and practices book spelled out this rather big
difference between the two username choices (certficate versus over
transport) then I must have missed it. So thanks again.
You are absolutely right about the issue that I can't tell if it is the
same client if I cache the authorization in the custom token manager.
Thank you for pointing that out. I did not think of that.
Let me run the following by you, just to see if you can poke any holes
in it. I believe that the web services client/server protocal we are
using does not have any state, so secure conversation was just to avoid
the overhead of validating the user on every call, not to save state.
More specifically, the protocal we use is something along the lines of
Client calls Web method returns
--------------- -----------------------------
GetRecordsAvailable record id: 118, 139, 143.
GetRecord(118) record 118
GetRecord(139) record 139
GetRecord(143) record 143
This is greatly simplified, in reality there might be 100's or 1000's
of records, and GetRecord can request more then 1 record at a time.
The client is allowed to request the same record as often as it likes,
and if it requests a record that does not exist, it will get back an
error.
Do you see any problem if the Custom Token Manage saves the User
Id/Password in the HTTPCache for something on the order of 5 minutes?
thanks,
--george
.
- References:
- Prev by Date: Re: secure a WS called via GPRS
- Next by Date: Re: secure a WS called via GPRS
- Previous by thread: Re: establishing a security context using usernameForCertificateSecurity
- Next by thread: Re: Deplocy a ClickOnce Application with WSE 3.0 UsernameToken
- Index(es):
Relevant Pages
|
Loading