-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extending the user model, which one to use? #98
Comments
@afidegnum Hi. The CREATE TABLE users (
id SERIAL PRIMARY KEY,
email VARCHAR NOT NULL UNIQUE,
hashed_password VARCHAR NOT NULL,
reset_password_selector VARCHAR,
reset_password_verifier_hash VARCHAR,
created_at TIMESTAMP NOT NULL DEFAULT NOW(),
updated_at TIMESTAMP NOT NULL DEFAULT NOW()
); Barricade will just ignore those fields. Does that answer your question? |
Thanks, I'm immensely grateful for your prompt response, |
please permit me to also ask, what's the difference between actix-server/src/ |
So I had 2 use cased when I built this. One is for normal authentication implemented in the This is the one you would want to use.
|
One last question, how do i authenticate a protected page? i.e. a user is visiting |
@ianpurton What do I replace JWT with in your project? |
So barricade sits in front of your application and intercepts all requests. So you In your backend you will receive a HTTP header called You don't need to do anything else barricade handles the session for you. |
Hi,
I really love the authentication mechanism posted. I was looking to implement something secured in a similar manner.
I noticed there are 3 user models with different security implementation.
Which one is the definite model which can be extended on? i.e adding custom bio, picture etc... ?
The text was updated successfully, but these errors were encountered: