@@Kehrlann Thanks alot :) I am working on a mutli-module app and want to ask if it is okay to: 1) Use a single login for down stream services hoping to extract useful claims such as roles or username and use this to assign tasks at controller level? Or do you think it is okay to define a security filter chain in the a) spring cloud gateway (and enable oauth2 login) and b) tdefine another security filter chain at the down stream services?
In case I have say serviceA (moduleA) which manages user login and serviceB (moduleB) which manages another typer of users......in case I want to assign different roles to serviceA user to perform specific actions on serviceC, is it okay to extract claims or tokens (in a particular way) and use this to authorize users managed via serviceA? I can create a minimal example or a diagram. Thanks your talk really (if your a Daniel).
Excellent presentation!! I have a question, if controller would never see the password, then if i want a controller to register an user, how could i do it? I mean, for registration user, the user has to send his credentials, I supossed that is in the controller, then do I have to create a filter for it?
Hey @rodanmuro! In that case, for user registration, it does makes sense to do it in a Controller - it's not performing "authentication", but actually some business logic for "creating" a user.
![Spring Security - Аутентификация, Авторизация, oAuth, и все остальное - [СЛИВ]](http://i.ytimg.com/vi/wcbqwYFfG70/mqdefault.jpg)
The most clear presentation on Spring Security. Thank you so much Daniel
What a great presentation, perfect english, very legible, congrat.
Awesome content and presentation. Thanks for putting it together and making it happen Daniel! Really appreciated it!
Wow, very good described Daniel! Thank you.👍
Awesome presentation, learned a lot, even some coding practices not related to Spring Security, thanks!!
Awesome presentation. Thank you very much.
Amazing bro! I´d like to see more videos about this topic !
Great presentation on Spring Security. Thanks.
Very good talk!
Great presentation👏👏👏
Awesome presentation dude❤
Great, great presentation. I have a question.
How may I help you? 😊
@@Kehrlann Thanks alot :) I am working on a mutli-module app and want to ask if it is okay to: 1) Use a single login for down stream services hoping to extract useful claims such as roles or username and use this to assign tasks at controller level? Or do you think it is okay to define a security filter chain in the a) spring cloud gateway (and enable oauth2 login) and b) tdefine another security filter chain
at the down stream services?
In case I have say serviceA (moduleA) which manages user login and serviceB (moduleB) which manages another typer of users......in case I want to assign different roles to serviceA user to perform specific actions on serviceC, is it okay to extract claims or tokens (in a particular way) and use this to authorize users managed via serviceA? I can create a minimal example or a diagram. Thanks your talk really (if your a Daniel).
Excellent presentation!! I have a question, if controller would never see the password, then if i want a controller to register an user, how could i do it? I mean, for registration user, the user has to send his credentials, I supossed that is in the controller, then do I have to create a filter for it?
Hey @rodanmuro!
In that case, for user registration, it does makes sense to do it in a Controller - it's not performing "authentication", but actually some business logic for "creating" a user.
beep boop Daniel 😊
Vielen Dank!
Where's the link to the slides and repo?
stop the video where he shows the linnks!
I really liked it
Perfectionist