Skip to content

Instantly share code, notes, and snippets.

View rp-arielrodriguez's full-sized avatar

Ariel Rodriguez rp-arielrodriguez

View GitHub Profile
@rp-arielrodriguez
rp-arielrodriguez / keycloak-self-exchange.md
Last active October 31, 2025 06:17
Keycloak token exchange proposal I

Keycloak Token Flow — Self-Exchange (with API Gateway)

Single confidential client recarga performs both exchanges from the API Gateway.
The Mobile App never receives the enriched (full) JWT; it only holds the lightweight token.
Gateway validates, self-exchanges, and forwards to downstream APIs.


A) Session Bootstrap — Gateway (recarga) exchanges Google → Keycloak (lightweight)

@rp-arielrodriguez
rp-arielrodriguez / pr_etiquette.md
Created November 19, 2024 02:31 — forked from mikepea/pr_etiquette.md
Pull Request Etiquette

Pull Request Etiquette

Why do we use a Pull Request workflow?

PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.

Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories

Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.