-
Notifications
You must be signed in to change notification settings - Fork 145
Delegated passticket API #4925
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.
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
Open
Joe-Winchester
wants to merge
9
commits into
docs-staging
Choose a base branch
from
joewinchester/address-issue-4920
base: docs-staging
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Delegated passticket API #4925
Changes from 4 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
fff495f
Delegated passticket API
Joe-Winchester 8ec850d
Updates following PR review
Joe-Winchester f218a66
Fixed space indent from 4 to 2
Joe-Winchester 0df2edb
Fix formatting in YAML
Martin-Zeithaml 8df9323
initial language refactoring
janan07 13a9a73
language refactor and restructure
janan07 4291f0a
fix overview steps
janan07 a6e5ccb
Update delegatePassticket configuration format
Martin-Zeithaml fa1da9e
Corrected PassTicket configuration instructions
Martin-Zeithaml File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
100 changes: 100 additions & 0 deletions
100
docs/user-guide/api-mediation/configuration-delegated-passticket.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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 | ||
| ``` | ||
|
|
||
| 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 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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). | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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
Should be
@taban03 Could you verify this? Thanks.
There was a problem hiding this comment.
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