i have never liked any of the videos on youtube, no matter how good or bad they are. But idk why when ever i see sunchit teaching something, everything comes out of my heart and i emotionally get involved into it. such a great guy to teach. i would say BEST IN THE BUSINESS.
better start building something using springboot instead reading book. always doing as extra edge. if you are absolute beginner just start with basic crud operations then build any real time applications i would suggest an social media application initially it would be confusing in btn layers like service controller entity dto soon it will be a great fun to code using spingboot
Great video. I have been selfhosting an identity provider that supports auth2.0 and want to use it for single sign on to authorize users inside my network. Accordingly how do I build my services to play well with SSO. How would the interaction between the Authorization server and resource server look ? Would the resource server issue the JWT token or the identity provider ? If the identity provider issues the token, will the resource server redirect the token to the resource server to validate it ?
Thanks for your kind words, these are the steps involved in SSO Authorization Flow: Your Identity Provider (Auth Server) handles authentication and issues JWT tokens to authenticated users. Token Usage: The Resource Server (your APIs) will receive these tokens from clients and validate them directly-no need to redirect the token back to the Auth Server. Validation: The Resource Server checks the token locally using the Identity Provider's public key or an introspection endpoint. This setup enables secure SSO across services efficiently.
@CodeWithSunchitDudeja Ahh .. I can see the identity provider has a jwks_url endpoint. It would make sense for the resource server to self validate tokens to reduce unnecessary load on the auth server. Thanks for the reply 😁
i have never liked any of the videos on youtube,
no matter how good or bad they are.
But idk why
when ever i see sunchit teaching something, everything comes out of my heart and i emotionally get involved into it.
such a great guy to teach.
i would say BEST IN THE BUSINESS.
Love the passion. Love this form of teaching. Hats off 🎉
very helpful
Really thanks for the initiative ❤❤. Thank for your detailed explanation
Love your videos man 🙌
These tutorial are very helpful, keep it up
hello sir code link is not in the description , how can I get that code ?
Very Helpful, can you suggest a good book for spring boot concepts - for beginner to get to advance level
You can read spring boot in action.
better start building something using springboot instead reading book. always doing as extra edge. if you are absolute beginner just start with basic crud operations then build any real time applications i would suggest an social media application initially it would be confusing in btn layers like service controller entity dto soon it will be a great fun to code using spingboot
Great video. I have been selfhosting an identity provider that supports auth2.0 and want to use it for single sign on to authorize users inside my network.
Accordingly how do I build my services to play well with SSO. How would the interaction between the Authorization server and resource server look ? Would the resource server issue the JWT token or the identity provider ? If the identity provider issues the token, will the resource server redirect the token to the resource server to validate it ?
Thanks for your kind words, these are the steps involved in SSO
Authorization Flow: Your Identity Provider (Auth Server) handles authentication and issues JWT tokens to authenticated users.
Token Usage: The Resource Server (your APIs) will receive these tokens from clients and validate them directly-no need to redirect the token back to the Auth Server.
Validation: The Resource Server checks the token locally using the Identity Provider's public key or an introspection endpoint.
This setup enables secure SSO across services efficiently.
@CodeWithSunchitDudeja Ahh .. I can see the identity provider has a jwks_url endpoint. It would make sense for the resource server to self validate tokens to reduce unnecessary load on the auth server.
Thanks for the reply 😁
🙏🏻🙂