The comment about being a 'toy service' is disingenuous... The comment about customers is possibly valid, the difference entirely your use case. If you consume

The comment about being a 'toy service' is disingenuous... The comment about customers is possibly valid, the difference entirely your use case. If you consume services as a corp, and your goal is to be able to decouple any employee quickly, then you do not need SSO, assuming each service you use allows you the option to delete by username (with proper auth, ofc). SSO is only needed when you want to give a customer federated access (ability to assign roles without activation on their part). For an internal corp it is largely unnecessary and a convenience thing not a security one (it is much more secure to require different passwords for every service versus a global SSO credential that gets you everywhere). If your "customers" are your own employees, then this is your decision not a use case or a business requirement.