Guide request: simple authentication with biscuit about biscuit-rust

[divarvel]

I have opened an issue on the website repo.

To give you a short answer:

• you can make a biscuit that just contains user(<user_id>); as a first step; that would be like a signed cookie
• you can embed a biscuit in an email yes. Typically you would embed restrictions in the token to mitigate leaks (a TTL check, restrictions on operations, a nonce check, etc)
• role typically refers to something that relates to authorization, it's a way to group several rights in a a context-dependent or evolutive fashion: a role might give different rights on different services; a role might evolve over time
• biscuit can make moving to a μServices architecture easy if you have a good separation between the part that emits the token and the parts that read it in your monolith. Public-key crypto makes it easy to craft the token in one place, and have other services check it with just the public key. Datalog is also a good fit for making consistent auth policies even in a ployglot setting. Biscuit has been clearly designed with experience from μServices, but it can still be useful in a monolith (easy to review auth policies, tokens restrictions)

we're available on https://matrix.to/#/!MXwhyfCFLLCfHSYJxg:matrix.org if you want to discuss it further

[woile]

Thank you! I'll give it a try!

[divarvel]

closing this as a duplicate of biscuit-auth/website#41