Question

I’m investigating ServiceStack’s Authorization feature and want to use Couchbase as my data store. I understand there isn’t an IUserAuthRepository implementation for Couchbase so I’d have to develop my own, which isn’t a problem.

The issue I am having is if I store the built-in UserAuth object as-is, CB it uses the Id field as the document identifier. This is a problem because I believe the identifier should be object type specific, otherwise a separate ‘bucket’ would be required to prevent conflicting id’s across different objects. I don’t really want to have lots of buckets unless I have to.

My preference would be to have the document id set to the type of the object plus the object specific identifier.

eg Using Id “UserAuth_1234” or using UserName “UserAuth_MikeGoldsmith”

Is my assumption of trying to re-use a bucket for different application objects valid or should I be thinking about a bucket per object-type / namespace?

Any direction would be welcome, both from Couchbase and ServiceStack enthusiasts.

Thanks

Additional Info

Ok, so from John’s answer I will assume my additional property for the object type is valid.

I found this post where Mythz suggests the BootStrapApi example extends the AuthUser with custom properties. However, to me it looks like the AuthUser is persisted twice, first as the AuthUser and again as the User object (both times using the OrmLiteAuthRepository). Am I right?

Essentially, I want to utilise the SS auth feature, but control the POCO object that will be saved into Couchbase. Can someone give some direction if this is possible and if so, what I need to implement / hook into?

I tried implementing a Couchbase version of IUserAuthRepository, however it uses the UseAuth concrete type so I can’t use my own object.

I also tried hooking into the OnAuthenticated method of AuthUserSession but at this point the UserAuth POCO will have been persisted using the register IUserAuthRepository.

I’m happy to use the CredentialsAuthProvider as I just want username/password authentication. More could be added later.

Thanks again!

Answer 1

I’ve come across the ServiceStack UseCase examples, with one that addresses my Custom Authentication issue directy.

I was able to override the TryAuthenticate method and use my own UserRepository that backs onto Couchbase.