[CF1] ZTIA troubleshooting guide final step #26207
Open
+93
−45
Conversation
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
deadlypants1973
requested review from
a team,
nikitacano and
ranbel
as code owners
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
lgmugnier
reviewed
Nov 4, 2025
| ### 3. Confirm user existence on the server | ||
|
|
||
| To verify the existence of the end user on the server, run the `id <USERNAME>` command on the server to verify that the end user's username exists. If the username does not exist, you must add the user to the server. | ||
| To verify the existence of the UNIX user on the server, run the `id <USERNAME>` command on the server to verify that the UNIX username exists. If the username does not exist, you must add the user to the server. |
There was a problem hiding this comment.
We should call it UNIX user because people can also SSH in to Windows machines
There was a problem hiding this comment.
although, I guess that would also be another process, so then my recommendation is just to make it clear that these are instructions for a unix server
lgmugnier
reviewed
Nov 4, 2025
|
|
||
| {props.sshMode ? ( | ||
| <> | ||
| <p>On October 30, 2025, at approximately 3:45 PM UTC, Alice attempted to SSH into 10.116.0.3 (target hostname: prod-db-01) using Access for Infrastructure. The SSH client returned <code>Permission denied (publickey)</code> despite her email being included in the Access policy.</p> |
There was a problem hiding this comment.
The most likely error is "Permission denied (none)"
lgmugnier
reviewed
Nov 4, 2025
| ### 3. Confirm user existence on the server | ||
|
|
||
| To verify the existence of the end user on the server, run the `id <USERNAME>` command on the server to verify that the end user's username exists. If the username does not exist, you must add the user to the server. | ||
| To verify the existence of the UNIX user on the server, run the `id <USERNAME>` command on the server to verify that the UNIX username exists. If the username does not exist, you must add the user to the server. |
There was a problem hiding this comment.
Suggested change
| To verify the existence of the UNIX user on the server, run the `id <USERNAME>` command on the server to verify that the UNIX username exists. If the username does not exist, you must add the user to the server. | |
| To verify the existence of a user on a UNIX server, run the `id <USERNAME>` command on the server to verify that the username exists. If the username does not exist, you must add the user to the server. |
deadlypants1973
commented
Nov 4, 2025
|
|
||
| {props.sshMode ? ( | ||
| <> | ||
| <p>On October 30, 2025, at approximately 3:45 PM UTC, Alice attempted to SSH into 10.116.0.3 (target hostname: prod-db-01) using Access for Infrastructure. The SSH client returned <code>Permission denied (publickey)</code> despite her email being included in the Access policy.</p> |
There was a problem hiding this comment.
Suggested change
| <p>On October 30, 2025, at approximately 3:45 PM UTC, Alice attempted to SSH into 10.116.0.3 (target hostname: prod-db-01) using Access for Infrastructure. The SSH client returned <code>Permission denied (publickey)</code> despite her email being included in the Access policy.</p> | |
| <p>On October 30, 2025, at approximately 3:45 PM UTC, Alice attempted to SSH into 10.116.0.3 (target hostname: prod-db-01) using Access for Infrastructure. The SSH client returned <code>Permission denied (none)</code> despite her email being included in the Access policy.</p> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Summary
PCX-19900
Screenshots (optional)
Documentation checklist