How to use DevForce entities in authentication

Hi Alexander,

Hi Alexander,

Katit: You are correct, I ended up having to use that magic EntityManager to get around my issue. I still wanted to use the ASP.NET security and the AspAuthenticatingLoginManager, so what I did was this:

public class MyAspAuthenticatingLoginManager : AspAuthenticatingLoginManager, IEntityLoginManager
{
    private static void SetProviderEntityManager( EntityManager entityManager )
    {
        MyMembershipProvider membershipProvider = Membership.Provider as MyMembershipProvider;
        if( membershipProvider != null )
            membershipProvider.AuthenticatedEntityManager = entityManager;

        MyRoleProvider roleProvider = Roles.Provider as MyRoleProvider;
        if( roleProvider != null )
            roleProvider.AuthenticatedEntityManager = entityManager;

        MyProfileProvider profileProvider = ProfileManager.Provider as MyProfileProvider;
        if( profileProvider != null )
            profileProvider.AuthenticatedEntityManager = entityManager;
    }

    public new IPrincipal Login( ILoginCredential credential, EntityManager entityManager )
    {
        SetProviderEntityManager( entityManager );

        return base.Login( credential, entityManager );
    }

    public new void Logout( IPrincipal principal, EntityManager entityManager )
    {
        SetProviderEntityManager( entityManager );

        base.Logout( principal, entityManager );
    }
}

As you can see, I'm passing the magic entityManager over to my custom ASP.NET Provider classes before I let the AspAuthenticatingLoginManager do its thing.

Well, as soon as one problem is solved, another one pops up.

When using the WCF Authentication Service, after configuring it properly, you simply make a call in the client app, like so:

if( System.Web.Security.Membership.ValidateUser( "alexander", "password" ) )
{
    Content = "LOGGED IN";
}
else
{
    Content = "DIDN'T LOG IN";
}

which magically ends up calling the ValidateUser method on the MembershipProvider on the server. As you can see from my implementation above, my MembershipProvider requires the magic EntityManager that gets supplied by the IEntityLoginManager. When using the WCF Authentication Service, the IEntityLoginManager is bypassed, and the call to ValidateUser is direct, which means that my "AuthenticatedEntityManager" property is null.

Is there something I can do to acquire that "magic" EntityManager in some other way or otherwise get around the whole Entity authentication issue some other way? All these obstacles I keep running into are getting just a smidgen annoying...