flash - Token-Based Authentication in WCF -
I am creating a website that will have both ASP.Net page and a Flash applet. I want to include my business logic in a WCF service that will be exposed through two concluding points: one can be used on the internet via HTTP (s), for use of Flash Client, and Application Server Data center for use by If it does not look like a good attitude, then stop me here; Otherwise, I will go ahead ...
The question is how to authenticate the requests that come from the Flash client. Since I do not want to store the user's password in a browser cookie, therefore do not want to send a password with each request, and do not want to use HTTPS after the initial login, I would not like to even do a token-based authentication system The user must enter the flash client after entering the site already, so I can find the token to the flash client I'm planning to use Javascript to sync.
I
The question is, then,: WCF know that to implement the login control. Supports to use the NET framework's built-in security framework (System.Security).
How can I pass a token to the WCF service when I'm asked by flash, and how do I process the token on the server?- An "ongoing token" authentication mode in WCF, but it appears that it intends to use a full token service and SAML token in a fully developed federation scenario. Is it possible to use this mode with its own "simple random string" token that I really want a bit of complexity? if so, how? Be sure to keep this requirement compatible with Flash.
- I could potentially pass a token (possibly a SOAP header or HTTP header) at the top. In this case, once I have determined that which users are requesting, how can I inform the setting so that the system Do security checks work?
- Should I consider different perspectives? Whatever is avoided sending password to every request, give me the system. Lets use security, and works with Flash is a possibility.
It seems that the original question has been answered, I will keep this brief , But an approach must actually pass authentication token in an HTTP header and override CheckAccess (OperationContacts Operation Contact, Ref message message)
in a Custom ServiceAdministrator Manager
You have already configured the service to use custom policy which is IAuthorizationPolicy
applies.
Whatever remains, implement simple IIdentity
and IPrincipal
classes to store your authorization status.
Many good articles are present:
I think it's still a "roll-yourself" "May feel like a solution, but at least be assured when you have the benefit of black-boxing your authorization code from your service practices after an established pattern.
Comments
Post a Comment