judahgabriel / ravendb.aspnet.identity Goto Github PK

Any plans to update this to support .NET Core 1.0 now that the RavenDb client supports it?

As ASP.NET 5 has an RC out, what would it take to get RavenDB.AspNet.Identity to run on DNX Core 5?

It looks like some of the plumbing is here for this feature, but without diving in too deeply, it looks like it's not complete. I've set the shouldLockout to true, but that doesn't have any effect on the AccessFailedCount value in the ApplicationUsers document with failed login attempts.

Hi,

Thanks for doing this project - as a RavenDB lover this is a huge step in the right direction when trying to handle everything without having to have a secondary database. :)

However, I have a problem. I have tried using the project in an MVC5 app (created in Visual Studio 2012 from the blank template, using elements from this article http://httpjunkie.com/2013/340/develop-mvc-5-with-asp-net-identity-in-visual-studio-2012/ to get somewhere). For development I run RavenDB on my local machine, port 8080. I have no problem accessing data or writing data.

When I try to use the /account/register method, it seems that RavenDB.AspNet.Identity checks for the presence of the username, but never actually creates it. I see the following in my RavenDB console log:

Request # 8: GET - 0 ms - TestDB - 404 - /docs/ApplicationUsers/RuneJ

So it checks to see if there is a user by the name I am trying to register, but it never actually creates the document - this is the only request passed to RavenDB for the duration of the register method.

I don't know for sure that the problem is in your code, it could be the UserManager that does it, but I get no errors or anything, so I wouldn't know where to start.

I'll be happy to provide anything from my project or try any suggestions.

If it matters, if I try to login, I get another request on the RavenDB server:

Request # 12: GET - 0 ms - TestDB - 404 - /docs/ApplicationUsers/RuneJ

Any hints?

Btw, here is my AccountController constructor, just in case you want to see it.

    public AccountController(IDocumentSession session)
    {
        _session = session;
        UserManager = new UserManager<ApplicationUser>(
            new UserStore<ApplicationUser>(() => _session));
    }

Hi,
I've upgraded to RavenDB 3 and it compiles well.

However, when I run a simple ASP.NET 5 MVC web site, having followed you instructions, I get some problems. The users are not persisted in the store.
I had to call this.session.SaveChanges(); in the CreateAsync method of the UserStore class.
I guess I missed something. I'm using RavenDB Embedded.

By the way, how do you make the calls to RavenDB "Store" persistent? I provide a RavenDB open session to the usermanager, who should call savechanges and dispose the session?
Isn't there a paradigm problem here?

There is a problem in the ASP.NET web site too, it create a instance of User with only a Name (no Id) at registration, and your provider doesn't fill automatically the Id from the Name. We can easily fix the AccountController to do that.
I would not do that in real life, but the ASP.NET MVC5 "Demo" does not work as is with

These are not big deals, but it did not work as simply as the tutorial. Great piece of code, very useful, thanks.

In my application, users register with an email address and I wanted to be able to have IdentityUser.UserName represent the email and IdentityUser.Id represent a GUID identifier. This approach isn't working, as I can see in the implementation of UserStore.CreateAsync() that the IdentityUser.Id property is always being generated based off the UserName.

It seems like the Microsoft.AspNet.Identity.IUser interface was intended to have two different pieces of information, a unique id for the user and the user name. In this implementation, I can only really store one piece of information, which is the username.

I know that supporting both Id and UserName as distinct fields on IdentityUser would require a RavenDB index on UserName (in order to support the FindByNameAsync() method). That seems like a reasonable tradeoff to me, but there might be other downsides that I'm not seeing.

I'm interested in your thoughts on this matter.

Unable to resolve dependencies. 'RavenDB.Client 4.0.2' is not compatible with 'RavenDB.Database 3.5.5 constraint: RavenDB.Client (= 3.5.5)'.

The notes said that updates were committed to allow for RavenDB 4. Am I reading this wrong? This error occurs when trying to add the newest RavenDB.Client via nuget.

Are there any plans on updating your provider and support vNext?

Any plans to upgrade to RavenDb 4?