Repository navigation
Replies: 1 comment
|
Thanks for considering this proposal. We have decided to pause the full Authorization Services article for now and focus first on maintaining the existing Apache APISIX integration entry in the Keycloak website. That smaller update is being tracked in keycloak/keycloak-web#815 and keycloak/keycloak-web#816. I’ll close this discussion to avoid leaving an inactive proposal open. We may revisit the Authorization Services topic later with a fully validated, version-pinned reproduction. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello Keycloak community,
I’m Yilia Lin, an Apache APISIX Committer. We would like to contribute a follow-up to the 2021 Keycloak article “How to Integrate Keycloak for Authentication with Apache APISIX.”
The proposed article is:
“Beyond Login: Enforcing Keycloak Authorization Services at the API Gateway with Apache APISIX”
Instead of repeating the basic OIDC login flow, it would focus on resource- and scope-based authorization:
authz-keycloakplugin;We would provide a version-pinned Docker Compose example, Keycloak realm configuration, APISIX configuration, and reproducible positive and negative tests. The article would be Keycloak-first, with no product comparison, performance claims, or sales call to action.
Would this topic be useful to the community? If so, would you prefer it as a Keycloak website guest post or as a documentation/tutorial contribution?
Yilia Lin, Apache APISIX Committer
All reactions