This article is based on Ballerina Swan Lake Update 6 (2201.6.0).

This article is based on Ballerina Swan Lake Update 4 (2201.4.0).

In the rapidly evolving tech landscape, the promise of control reigns supreme. And, it’s why founders, CEOs, and technical decision-makers are increasingly drawn to the idea of building in-house platforms. The appeal is understandable: complete sovereignty over every layer of the tech stack, from the user interface down to the most granular data interactions. It's an intoxicating vision that promises a bespoke solution tailored precisely to a company's unique needs.

In the world of API security, OAuth 2.0 plays a crucial role in authorization. OpenID Connect (OIDC) works seamlessly with OAuth 2.0, providing an identity layer that ensures standardized authentication and user information for applications. Among various grant types, the Authorization Code stands out as a recommended standard. It's known for its advanced security features, support for refresh tokens, reduced exposure of credentials, and adaptability for both server-side and front-end applications.