mojoMembershipProvider, mojoRoleProvider not requiring HttpContext

This is a forum to suggest new features for mojoPortal. 

This thread is closed to new posts. You must sign in to post in the forums.
12/9/2008 4:38:46 AM
alabax
Gravatar
Total Posts 4
View Posts

mojoMembershipProvider, mojoRoleProvider not requiring HttpContext

Hi, Joe

Can you please make mojoMembershipProvider and mojoRoleProvider classes not requiring to be hosted in ASP.NET app so it could be an easy way to implement authentication/authorization for stand-alone WCF services utilizing the same user registry.

Thanks,

Misha

12/9/2008 6:02:28 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: mojoMembershipProvider, mojoRoleProvider not requiring HttpContext

Hi Misha,

Why does it need to be stand alone?

FYI, in svn trunk I already have a WCF AuthenticationService at Web/Services/AuthenticationService.svc.
I also have a WCF role service at Web/Services/RoleService.svc.
I am using both currently from Silverlight.

Its possible to create a separate WCF project and reference mojoPortal.Web project to be able to use these providers.

Internally these providers have dependencies on other mojoportal objects and HttpContext is required to get SiteSettings object from the cache. I see no reason to avoid dependency on httpcontext in a web application or WCF application.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.