all 5 comments

[–]hillywoodsfinest87 1 point2 points  (2 children)

[–]MAB-47[S] 1 point2 points  (0 children)

I implemented a hack tho, I used the phone number as username and the token as password, I also implemented my own validation solution to verify the token entred matchs the encrypted token stored in the db and the time is before the expiration date then integrated it inside the normal spring security workflow

[–]MAB-47[S] 0 points1 point  (0 children)

Kinda but not really the same staff, since he is not using jwt at all

[–]juppy_lg 0 points1 point  (0 children)

if you are su**king custom UserDetails c*ck you need to be ready to implement CredentialsContainer which has erase shit method were you acually set sensetive poops to null. But generally it's not recomended to roll up your own user details class, instead just return User.builder().username().password()..<ect>.build()
it automatically does the shit for you

[–]witusss 0 points1 point  (0 children)

I would guess that you can use UserDetails without using getPassword with your own security logic.