System Users and Application Users
This is a question that comes up relatively often in the RavenDB mailing list. How do I handle multiple users with RavenDB? Does it support multiple users? Does it supports the Membership Provider?
Those questions usually confuse a very key concept regarding users. Whose users are they?
In particular, we need to make a distinction between System Users and Application Users. Despite using the same term for both, there is actually very little connection between the two.
Here is an example of a System User:
<connectionStrings> <add name="RavenDB" connectionString="Url=http://scotty.ravendb.net;user=beam;password=up"/> </connectionStrings>
As you can probably surmise, this is a connection string, and the user is ‘beam’. This user is a System User, if you call the Ops Team and ask them why the password expired, they can help you there.
This is a system user, it controls access to external resources, and usually you have very few of those. Usually they control things like what parts of the disk you can write to, what databases you can connect to, etc. For the most part, they aren’t in your control, you don’t manage them and neither does you application
In contrast to that, here is a great example of an Application User:
An Application User is unique to its application. It is usually manifested as a document (or a database row) and doesn’t have any existence beyond that. If you called the Twitter Team Ops and told them that the RavenDB account password need resetting, they would be pissed that you are wasting their time.
This distinction is important, because it implies a lot about how we use those two different types of users.
System Users are used… well, for the system. Application Users are the actual users using the system. Very rarely are they one and the same. Usually our application use service accounts, and any security checks for what an Application User can do are implemented as part of the business logic, not by setting ACLs.
Don’t confuse the two, despite the common name.
And coming back all the way to the original question. RavenDB comes with the notion of System Users via Windows Auth and OAuth, and it helps with Application Users using the Authorization Bundle. But you really don’t want to use the membership API, regardless of the underlying storage.