Open TradeArcher2020 opened 11 years ago
CMircea
commented
11 years ago Hi!
I haven't actually considered that option. I tried to get something simple out to be readily used; I haven't had the time to do that; I currently manage users myself and simply associate them with the username provided by the auth provider.
A pull request would be great though :)
TradeArcher2020
commented
11 years ago Ah, yes. That’s what I’m doing now, too. That will work for me for now, but maybe sometime in the future we can expand the flexibility of the AuthProvider.
Thanks,
Chris
From: Mircea Chirea [mailto:notifications@github.com] Sent: Wednesday, February 13, 2013 6:58 PM To: ravendb/ravendb.contrib Cc: Chris Subject: Re: [ravendb.contrib] Provide a way to use the Account object outside the AuthProvider (#22)
Hi!
I haven't actually considered that option. I tried to get something simple out to be readily used; I haven't had the time to do that; I currently manage users myself and simply associate them with the username provided by the auth provider.
A pull request would be great though :)
— Reply to this email directly or view it on GitHub https://github.com/ravendb/ravendb.contrib/issues/22#issuecomment-13527782 .
I would like to be able to extend the user's Account by associating it with a Profile object. However, I need to be able to access the Account from my web app so I can create the user Profile object and set it's AccountId to the Id of the Account for the specified user.
Also, it would be nice to be able to do more manipulation to the Account from outside the provider for more advanced user management than what the AuthProvider provides. Have you considered making the Account extensible by storing an IAccount rather than an account and giving the user the option of how to implement IAccount in their web application?