In memory Connection repository

[marceloverdijk]

While looking at code of ConnectController and ProviderSignInController they both seem to be tight to UsersConnectionRepository.
As I only need to sign in with Facebook/Client (and not storing any information itself) I think I'm better of creating my own Controller? Or would you advise differently?

[habuma]

You're right that both are tied to UsersConnectionRepository and that even during the course of an implicit signup (as is demonstrated in the quickstart), a connection is saved to the connection table. But you still don't need a local user database...just a database to hold those connections.

Even then, I probably wouldn't write a custom controller. Instead, I'd consider writing a custom connection repository pair. It's important that ProviderSignInController know about those connections or else it will force a signin again the next time they visit your app. Maybe that's what you want...in which case, the custom connection repository could store nothing and always report that it can't find a connection.

But your point is well-taken that there needs to be an example or better guidance on writing apps that don't maintain any sort of local database and only rely on the provider for all user data. I'll add that to my list of examples to put together. Of course, I welcome anyone else who might want to contribute such an example.

[marceloverdijk]

Yes I was also thinking of writing custom connection pair as well.

One question related to the quickstart sample is that I'm wondering if there would be a benefit storing the connections in the database without a local user?
It probably means the user can be connected automatically when he/she tries wants to connect at the same provider, right? Thus without having to accept access to the application again.
If this is right it would make sense to store the connection indeed.