This is an automated email from the ASF dual-hosted git repository.
young pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git
The following commit(s) were added to refs/heads/master by this push:
new 65cdc8bab57 fix: front matter (#1482)
65cdc8bab57 is described below
commit 65cdc8bab57d31f4144a428f0e9d597b94a3b383
Author: Young <[email protected]>
AuthorDate: Fri Jan 20 12:07:48 2023 +0800
fix: front matter (#1482)
Fixes https://github.com/apache/apisix-website/issues/1481
---
...from_everywhere_with_keycloak_authentication.md | 22 ++++++++++------------
1 file changed, 10 insertions(+), 12 deletions(-)
diff --git
a/blog/en/blog/2023/01/02/accessing_apisix-dashboard_from_everywhere_with_keycloak_authentication.md
b/blog/en/blog/2023/01/02/accessing_apisix-dashboard_from_everywhere_with_keycloak_authentication.md
index 468e91252f7..e464b8adcc4 100644
---
a/blog/en/blog/2023/01/02/accessing_apisix-dashboard_from_everywhere_with_keycloak_authentication.md
+++
b/blog/en/blog/2023/01/02/accessing_apisix-dashboard_from_everywhere_with_keycloak_authentication.md
@@ -2,7 +2,7 @@
title: "Accessing APISIX-Dashboard from Everywhere with Keycloak
Authentication"
authors:
- name: "Busico Mirto Silvio"
- title: ""
+ title: "Author"
url: "https://github.com/MirtoBusico";
image_url:
"https://avatars.githubusercontent.com/u/11090934?s=400&u=644e4f87c2fad56760f6eb4f46cbcb4db059880a&v=4";
keywords:
@@ -13,9 +13,7 @@ keywords:
- Keycloak
description: This guest blog shares how to expose the APISIX Dashboard using
APISIX to authenticate access with the OpenID-Connect plugin and Keycloak
server to manage identities.
tags:
- - APISIX Basics
- - API Gateway Concepts
- - Authorization & Authentication
+ - Ecosystem
cover: https://static.apiseven.com/uploads/2023/01/19/FKDU7U6j_blog01a.png
---
@@ -37,14 +35,14 @@ Here I'll present instructions, examples, code and
screenshots taken from my hom
The framework used in this article consists of some KVM virtual machines (from
now VM):
-| VM Name | Role | Services | Description |
-|-------------|------|----------|-------------|
-| hdev | Development |kubectl, istioctl, helm |
workstation from where manage the cluster |
-| hserv | external services | DNS server, Nginx, Keycloak |
services used by the cluster VM and external users |
-| hkm | Kubernetes master | master node | control plane
manager for K8S |
-| hkw1 | K8S worker 1 | first worker node | node for
hosting pods |
-| hkw2 | K8S worker 2 | second worker node | node for
hosting pods |
-| hkw3 | K8S worker 3 | third worker node | node for
hosting pods |
+| VM Name | Role | Services | Description
|
+| ------- | ----------------- | --------------------------- |
-------------------------------------------------- |
+| hdev | Development | kubectl, istioctl, helm | workstation from
where manage the cluster |
+| hserv | external services | DNS server, Nginx, Keycloak | services used by
the cluster VM and external users |
+| hkm | Kubernetes master | master node | control plane
manager for K8S |
+| hkw1 | K8S worker 1 | first worker node | node for hosting
pods |
+| hkw2 | K8S worker 2 | second worker node | node for hosting
pods |
+| hkw3 | K8S worker 3 | third worker node | node for hosting
pods |
The **hserv** VM have two lan cards: one on an external lan to expose services
and one an internal lan to communicate with the Kubernetes (from now K8S)
cluster.
All the other VM are only connected to the internal lan.
