Fix more wrong endpoints in openid-connect-client guide

#26372 did not catch all occurrances of the endpoints.
This commit fixes the missing ones.

Signed-off-by: Harald Albers <github@albersweb.de>
(cherry picked from commit 007ea98)

Author: albers

docs/src/main/asciidoc/security-openid-connect-client.adoc

@@ -31,7 +31,7 @@ In this example, we will build an application which consists of two JAX-RS resou
 * `/frontend/user-name-with-propagated-token`
 * `/frontend/admin-name-with-propagated-token`
 
-`FrontendResource` will use REST Client with `OpenID Connect Client Reactive Filter` to acquire and propagate an access token to `ProtectedResource` when either `/frontend/user-name-with-oidc-client` or `/frontend/admin-name-with-oidc-client` is called. And it will use REST Client with `OpenID Connect Token Propagation Reactive Filter` to propagate the current incoming access token to `ProtectedResource` when either `/frontend/user-name-with-propagated-token` or `/frontend/admin-name-with-propagated-token` is called.
+`FrontendResource` will use REST Client with `OpenID Connect Client Reactive Filter` to acquire and propagate an access token to `ProtectedResource` when either `/frontend/user-name-with-oidc-client-token` or `/frontend/admin-name-with-oidc-client-token` is called. And it will use REST Client with `OpenID Connect Token Propagation Reactive Filter` to propagate the current incoming access token to `ProtectedResource` when either `/frontend/user-name-with-propagated-token` or `/frontend/admin-name-with-propagated-token` is called.
 
 `ProtecedResource` has 2 endpoints:
 
@@ -264,7 +264,7 @@ public class FrontendResource {
 }
 ----
 
-`FrontendResource` will use REST Client with `OpenID Connect Client Reactive Filter` to acquire and propagate an access token to `ProtectedResource` when either `/frontend/user-name-with-oidc-client` or `/frontend/admin-name-with-oidc-client` is called. And it will use REST Client with `OpenID Connect Token Propagation Reactive Filter` to propagate the current incoming access token to `ProtectedResource` when either `/frontend/user-name-with-propagated-token` or `/frontend/admin-name-with-propagated-token` is called.
+`FrontendResource` will use REST Client with `OpenID Connect Client Reactive Filter` to acquire and propagate an access token to `ProtectedResource` when either `/frontend/user-name-with-oidc-client-token` or `/frontend/admin-name-with-oidc-client-token` is called. And it will use REST Client with `OpenID Connect Token Propagation Reactive Filter` to propagate the current incoming access token to `ProtectedResource` when either `/frontend/user-name-with-propagated-token` or `/frontend/admin-name-with-propagated-token` is called.
 
 Finally, lets add a JAX-RS `ExceptionMapper`:
 
@@ -485,15 +485,15 @@ Now lets check `FrontendResource` methods which do not propagate the existing to
 [source,bash]
 ----
 curl -v -X GET \
-  http://localhost:8080/frontend/user-name-with-oidc-client`
+  http://localhost:8080/frontend/user-name-with-oidc-client-token`
 ----
 
 will return `200` status code and the name `alice`, but
 
 [source,bash]
 ----
 curl -v -X GET \
-  http://localhost:8080/frontend/admin-name-with-oidc-client`
+  http://localhost:8080/frontend/admin-name-with-oidc-client-token`
 ----
 
 will return `403` status code.