Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

minor language refactoring and link fix #3574

Merged
merged 1 commit into from
Mar 28, 2024
Merged

minor language refactoring and link fix #3574

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 6 additions & 7 deletions docs/user-guide/cli-using-integrating-apiml.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ You can use tokens or client certificates to integrate with API ML.

Tokens allow you to access services through API ML without reauthenticating every time you issue a command. Tokens allow for secure interaction between the client and server. When you issue commands to API ML, the layer routes requests to an appropriate API instance based on system load and available API instances.

Some users prefer to use certificates to access API ML. This can be the case in sites that use credentials such as passwords and multifactor authentication, which might be valid only for a short period of time. Certificates can be valid for much longer.
Some users prefer to use certificates to access API ML. This can be the case in sites that use credentials such as passwords and multifactor authentication, which might be valid only for a short period of time. Certificates can be valid for much longer.

## How token management works

Expand All @@ -20,7 +20,7 @@ Zowe CLI also supports standard token implementations such as Java Web Tokens (J

## Logging in

To request a token and log in to API ML:
Follow these steps to request a token and log in to API ML:

1. Issue the following command to log in to API ML:

Expand All @@ -42,8 +42,7 @@ To request a token and log in to API ML:

:::note

Where the token is saved depends on whether you have an existing base profile and where that profile is located. To learn about the precedence Zowe CLI follows with profile configurations, see [How configuration files and profiles work together](../user-guide/cli-using-understand-profiles-configs.md#how-configuration-files-and-profiles-work-together).

Where the token is saved depends on whether you have an existing base profile and where that profile is located. To learn about the precedence Zowe CLI follows with profile configurations, see [How configuration files and profiles work together](./cli-using-understand-profiles-configs.md#how-configuration-files-and-profiles-work-together).
:::

3. Provide a base path and base profile on commands to connect to API ML.
Expand All @@ -68,7 +67,7 @@ To request a token and log in to API ML:

Log out to prompt the API ML token to expire and remove it from your base profile.

To log out of the API ML:
Use the following logout prompt:

```
zowe auth logout apiml
Expand All @@ -93,7 +92,7 @@ Ensure that you *do not* provide username, password, host, or port directly on t

### Specifying a base path with Zowe V2 profiles

To specify a base path with Zowe V2 profiles:
Use the following steps to specify a base path with Zowe V2 profiles:

1. Note the complete path for a z/OSMF instance registered to API ML.

Expand All @@ -119,7 +118,7 @@ To specify a base path with Zowe V2 profiles:

### Specifying a base path with Zowe V1 profiles

To specify a base path with Zowe V1 profiles:
Use the following steps to specify a base path with Zowe V1 profiles:

1. Note the complete path for a z/OSMF instance registered to API ML.

Expand Down
2 changes: 1 addition & 1 deletion docs/user-guide/generate-certificates.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,7 +226,7 @@ After you configure the `zowe.yaml`, use the following procedure to generate a J

`zwe init certificate -c <path-to-your-zowe-configuration-yaml> --update-config`

When the command is run, a customized JCL member name is created in the `CUST.JCLLIB` data set. The PDS name is defined in the `zowe.setup.dataset.jcllib` property. In the following example output, the PDS meember `USER.ZWEV2.CUST.JCLLIB(ZW101431)` is created that contains the security manager commands, and then submitted as a job ID: `ZWEKRING(JOB03054)`.
When the command is run, a customized JCL member name is created in the `CUST.JCLLIB` data set. The PDS name is defined in the `zowe.setup.dataset.jcllib` property. In the following example output, the PDS member `USER.ZWEV2.CUST.JCLLIB(ZW101431)` is created that contains the security manager commands, and then submitted as a job ID: `ZWEKRING(JOB03054)`.

The following command output shows the generation of a JCERACFKS certificate using the default values. Note that some detailed output messages have been omitted.

Expand Down
Loading