From 8a2c49dde5ba008696722b580837a09a1eb9948a Mon Sep 17 00:00:00 2001 From: Dimitrij Drus Date: Tue, 13 Dec 2022 15:51:21 +0100 Subject: [PATCH] further clarifications --- docs/content/docs/getting_started/concepts.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/docs/getting_started/concepts.adoc b/docs/content/docs/getting_started/concepts.adoc index 97faec98c..0d98b5079 100644 --- a/docs/content/docs/getting_started/concepts.adoc +++ b/docs/content/docs/getting_started/concepts.adoc @@ -15,7 +15,7 @@ Everything you need to know. == Pipeline -As described in the link:{{< relref "/docs/welcome.adoc" >}}[Welcome] section and also shown in the diagram below, heimdall authenticates and authorizes incoming HTTP requests, rejecting unauthenticated or unauthorized ones, as well as enriches the valid requests with further contextual information and transforms resulting subject information into a format, required by the upstream services. This is done in upstream service specific link:{{< relref "/docs/configuration/rules/overview.adoc" >}}[rules], which define the required individual pipelines by making use of different link:{{< relref "/docs/configuration/rules/pipeline_mechanisms/overview.adoc" >}}[mechanisms]. +As described in the link:{{< relref "/docs/welcome.adoc" >}}[Welcome] section and also shown in the diagram below, heimdall authenticates and authorizes incoming HTTP requests, rejecting unauthenticated or unauthorized ones, as well as enriches the valid requests with further contextual information and transforms resulting subject information into a format, required by the upstream services. This is done in upstream service specific link:{{< relref "/docs/configuration/rules/overview.adoc" >}}[rules], which assemble the required individual pipelines by making use of different link:{{< relref "/docs/configuration/rules/pipeline_mechanisms/overview.adoc" >}}[mechanisms]. [[_fig_heimdall_request_pipeline]] .Request Pipeline