One Keycloak to Rule Them All - Our Products Started Talking to Each Other. Security Was Not Amused.

Client Credentials, Token Exchange, and why forwarding JWTs everywhere is probably not the architecture we want. Products work individually -> products need each other’s APIs -> user tokens aren’t always appropriate -> introduce service identities and delegation. 😵

In the previous post, we finally got our products to use Keycloak for authentication.

One Keycloak to Rule Them All - It Was Just a Login Page. What Could Possibly Go Wrong?

How we ended up using Keycloak for authentication and Single Sign-On across multiple products. One product -> more products -> duplicate login headaches -> Keycloak -> SSO finally works.

It all started with a simple requirement: users should be able to log in.

One Keycloak to Rule Them All - Everybody Wants Access. Nobody Wants to Ask Permission

Building OAuth integrations with Keycloak, user consent, and organization administrator approval without accidentally giving everyone access to everything. Internal communication works -> external developers arrive -> OAuth clients and scopes -> user consent -> admin approval -> secure external integrations.

In the previous two posts: post 1, post 2, we managed to solve user authentication and internal communication between our products.

Beyond the Hype: Start Building Intelligent Systems from First Principles

“Building an AI agent? It’s not just about picking the flashiest toolbox like LangChain or CrewAI and praying for magic. It’s more like assembling IKEA furniture with the mind of Sherlock Holmes, the patience of a monk, and the logic of Mr. Spock.” — ChatGPT 🤣
Before you glue parts together, teach your system how to think — define its brain loops, give it memory, a plan, eyes and hands… then finally decide if it needs to be a one-man-band or a full-on Avengers team of sub-agents.
Start with brains, add tools later, frameworks don’t fix chaos 😘

The world of AI is overflowing with powerful tools: LangChain, AutoGen, LangGraph, CrewAI, and many others. But with so many options, it’s easy to feel overwhelmed. Where should you begin?

Multi-tenancy with spring boot (Shared Database and Shared Schema) - Part 2

Khởi đầu với Multi-tenancy with spring boot - Part 1 tôi đã phun một tràng về lý thuyết cũng như các cách impl multi-tenancy trong spring (và tất cả chỉ là nói mồm 😆). Tiếp nối series multi-tenancy, bài viết này tôi sẽ giới thiệu cụ thể về cách impl Shared Database and Shared Schema với spring.

Lý thuyết về Shared Database and Shared Schema trong multi-tenancy tôi sẽ không nói nữa (nói nữa các bạn lại đấ* tôi vì lắm mồm 🥲). Bài hôm nay tôi sẽ bê từ How to integrate Hibernates Multitenant feature with Spring Data JPA in a Spring Boot application, ok, let’s start.

Pagination


Copyright © 2022. All rights reserved.