Move to axum-login once it supports tower-sessions
iJustErikk opened this issue · comments
Hi,
I think axum-login will simplify the code a bit. It is agnostic to storage. Right now, it depends on axum-sessions, but I see they are working on migrating to tower-sessions. When they migrate, I could switch it over.
Does this sound like a good idea?
@iJustErikk , no problem adding axum-login
once it also migrates from axum-sessions
. axum-login
adds functionality related to authentication and user store which currently isn't provided in this template. I like that it provides arbitrary user types and arbitrary storage backends. As a template, I don't want to bind the package to a specific user setup or storage method. Thanks.
Just chiming in to mention that axum-login
has migrated to tower-sessions
.
@iJustErikk Let me know if you want to take a stab at adding....
Can take a look in next 2 days
hey @jbertovic
just got done with being sick. do you think we should add some authorization starter code in the template? we could just keep this simple by checking if the username is admin or something
Sounds good. No worries adding a bit more logic in the template with starter code.