Make storage interface more friendly about webauthn

[nsatragno]

individual credentials can be deleted by just setting a new object that omits that credential in particular. Anything wrong with that approach?

Hmmm, I think on a relational database that would require SELECTing the user, diffing against the user authenticators, and figuring out what to delete. I just realized that's the same thing for adding authenticators though 🤔.

Maybe that's acceptable for an MVP, and we should consider having two kinds of adapters, one for relational and one for document databases.

@nsatragno @inorganik what do you think about adding a new storage interface (and documentation) for the user session as well?

+1

[EternalDeiwos]

Agreed for the first two points -- on the last, I'd say that individual credentials can be deleted by just setting a new object that omits that credential in particular. Anything wrong with that approach?

@nsatragno @inorganik what do you think about adding a new storage interface (and documentation) for the user session as well? That would also give greater control on that front (CC #15)