Skip to content
Open
Show file tree
Hide file tree
Changes from 4 commits
Commits
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
5 changes: 4 additions & 1 deletion docs/appendix/zowe-yaml-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -536,8 +536,11 @@ These configurations can be used under the `components.gateway` section:
- **apiml.security.oidc.identityMapperUser**
(Optional) If the userId is different from the default Zowe runtime userId (`ZWESVUSR`), specify the `identityMapperUser` userId to configure API ML access to the external user identity mapper.
- **apiml.security.oidc.userIdField**
Specifies the name of the field from the OIDC token with the value that is used for user mapping in SAF. Supports also nested objects via a dot-separated list. When the field contains multiple values, all values are used as distributed identifiers for mapping. Each value for mapping is evaluated sequentially and the first successfully mapped user is used. This parameter is used to specify, for example, a custom field with email or LDAP groups for user mapping. This parameter applies to Zowe version 3.4.0 and later versions.
Specifies the name of the field from the OIDC token with the value that is used for user mapping in SAF. Supports also nested objects via a dot-separated list. When the field contains multiple values, all values are used as distributed identifiers for mapping. Each value for mapping is evaluated sequentially and the first successfully mapped user is used. This parameter is used to specify, for example, a custom field with email or LDAP groups for user mapping. This parameter applies to Zowe version 3.4.0
and later versions.
**Default:** `sub`
- **apiml.security.delegatePassticket.enabled**
Specifies whether the API `POST` for endpoint `/gateway/api/v1/auth/delegate/passticket` is enabled. The default value is `false`. For more information, see [Configuring Delegated Passticket Generation](../user-guide/api-mediation/configuration-delegated-passticket.md).

:::note

Expand Down
3 changes: 2 additions & 1 deletion docs/user-guide/api-mediation/configuration-authorization.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,4 +7,5 @@ In Zowe's API Mediation Layer, system administrators can limit access to service

- [Limiting access to information or services in the API Catalog](./configuration-limiting-access-to-info-or-services-in-api-catalog.md)
- [Configuring SAF resource checking](./configuration-saf-resource-checking.md)
- [Configurint Health Endpoint Protection](./configuration-health-endpoint-protection.md)
- [Configuring Health Endpoint Protection](./configuration-health-endpoint-protection.md)
- [Configuring delegated passticket generation](./configuration-delegated-passticket.md)
100 changes: 100 additions & 0 deletions docs/user-guide/api-mediation/configuration-delegated-passticket.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,100 @@
# Configuring Delegated Passticket Generation

:::info Role: system administrator
:::

As a system administrator, you can enable the endpoint of the API Gateway that allows passticket generation for a delegated e-mail. This API allows the authenticated user to create a passticket for another user, so has the potential be be misused for privilege escalation or impersonation. For that reason the API authentication must be done with a client certificate for a userID who has `READ` access to the class `ZOWE.APIML.DELEGATE.PASSTICKET` and the endpoint must be enabled by setting `zowe.components.gateway.apiml.security.delegatePassticket` parameter to `true`.

Use the following procedure to enable the delegated passticket endpoint of the API Gateway:

1. Open the file `zowe.yaml`.
2. Configure the following property:

* `components.gateway.apiml.security.delegatedPassticket`
This property defines whether the endpoint `/gateway/api/v1/auth/delegate/passticket` is available

:::note
The default value of this parameter is `false`. To enable the endpoint set it to be `true`.
:::

**Example:**
```yaml
components:
gateway:
apiml:
security:
delegatePassticket: true
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this correct? From the PR, it looks like

 @ConditionalOnProperty(value = "apiml.security.delegatePassticket.enabled", havingValue = "true", matchIfMissing = false)

Should be

components:
  apiml:
    security:
      delegatePassticket:
        enabled: true

@taban03 Could you verify this? Thanks.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch @Martin-Zeithaml . Yes that should be like you suggested

```

The userID that makes the call to the API must have `READ` access to the class `ZOWE.APIML.DELEGATE.PASSTICKET`. For more information on how to configure this see [Configuring User permission call delegated passticket API](#configuring-user-permission-to-generate-delegated-passtickets)

## Configuring user permission to generate delegated passtickets

The delegated passticket API must be called with a client certificate. The z/OS user ID associated with the certificate must have `READ` permission for the `ZOWE.APIML.DELEGATE.PASSTICKET` class.

<details>

<summary>Click here for command details about configuring user access using RACF</summary>

In your ESM command line interface or other security environment, perform the following steps:

1. Define the resource class by running the command:

```racf
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we include the equivalent commands for TSS and ACF2 as well?

RDEFINE ZOWE APIML.DELEGATE.PASSTICKET UACC(NONE)
```

2. Permit the user associated with the client certificate `READ` access
```racf
PERMIT APIML.DELEGATE.PASSTICKET CLASS(ZOWE) ID(<userID>) ACCESS(READ)
SETROPTS RACLIST(ZOWE) REFRESH
```

- **`userID`**
The userID associated with the client certificate calling the API

3. (optional) To see the all permissions for users
```racf
RLIST ZOWE APIML.DELEGATE.PASSTICKET AUTHUSER
```

</details>

<details>

<summary>Click here for command details about configuring user access using ACF2</summary>

In your ESM command line interface or other security environment, perform the following step

1. Grant the userID `READ` access
```acf2
SET RESOURCE(RDA) $KEY(ZOWE) TYPE(RDA) APIML.DELEGATE.PASSTICKET UID(<userID>) SERVICE(READ) ALLOW
```

</details>

<details>

<summary>Click here for command details about configuring user access using Top Secret</summary>

In your ESM command line interface or other security environment, perform the following steps

</details>

## Calling the /auth/delegate/passticket API

To call the API `POST` `/gateway/api/v1/auth/delegate/passticket` the body should be `JSON`

```
{
"applId": "APPLID",
"emailId": "email@example.com"
}
```

-**`APPLID`**
The applicationID associated with the address space the passticket is being generated for. As an example, to create a passticket for z/OSMF this value will be `IZUDFLT`

-**`emailId`**
The e-mail ID of the user that is associated with the z/OS userID, see [ESM configuration](../../extend/extend-apiml/api-mediation-oidc-authentication.md#esm-configuration-prerequisites).

Loading