No they are different concepts. SSO is managed by a particular company who manage user rights themselves. OAuth is handled by large organisations who ask the user for what permissions they want to extend to the requesting website.
We can go hybrid, I mean at the time of onboarding oAuth is best option, after that we can maintain user details with null password (no password) and give user option to setup a password to after email verification. And done , now you don't have to worry about vendor. Hope this makes sense 😅.
The first part of the title let me belief that you will be talking about auth in distributed systems like where a gateway will authenticate the caller and all microservices won't deal with auth themselves. Another interesting topic for another video?
Objectively: InterviewReady has over 220 videos on System Design, Live Classes twice a month and lifetime validity. ByteByteGo doesn't offer any of the above. Subjectively: InterviewReady users have changed their thinking about tech after going through our courses. The in-depth explanations helped secure better salaries, switch companies and add value in team discussions. In short: Over 15000 users have found the courses awesome. We are rated >4.5/5 on average :D Your tech team will be glad that you made this investment.
