From 497854127263e68336eb07aa7a1623b4b156803f Mon Sep 17 00:00:00 2001 From: Andrew Jandacek Date: Fri, 27 Dec 2024 11:29:19 +0100 Subject: [PATCH] fix typos Signed-off-by: Andrew Jandacek --- .../api-mediation/configuration-saf-resource-checking.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/user-guide/api-mediation/configuration-saf-resource-checking.md b/docs/user-guide/api-mediation/configuration-saf-resource-checking.md index ea78c8893f..f95e132aba 100644 --- a/docs/user-guide/api-mediation/configuration-saf-resource-checking.md +++ b/docs/user-guide/api-mediation/configuration-saf-resource-checking.md @@ -46,7 +46,7 @@ strictly define a provider. If verification is disabled, select the `endpoint` o To use the endpoint provider, you also need to enable the endpoint property and customize the URL corresponding to the SAF resource authorization. By default, the ZSS API is configured and used. 1. Open the file `zowe.yaml`. -2. Find or add the folowing properties: +2. Find or add the following properties: - `components.gateway.apiml.security.authorization.provider: endpoint` - `components.gateway.apiml.security.authorization.endpoint.enabled: true` - `components.gateway.apiml.security.authorization.endpoint.url: ` @@ -107,11 +107,12 @@ The following YAML presents the structure of the file: :::note Notes - Classes and resources are mapped into a map with user IDs contained in a list. -- The load method does not support formatting with periods `.`, such as shown in the following example: +- The load method does not support formatting with periods (`.`), such as shown in the following example: + **Example:** `{CLASS}.{RESOURCE}` - Ensure that each element is separated. +- Ensure that each element is separated. - The field `safAccess` is not required to define an empty file without a definition. - Classes and resources cannot be defined without the user ID list. -- When a user has multiple definitions of the same class and resource, only the most privileged access level loads. +- When a user has multiple definitions of the same class and resource only the most privileged access level loads.