DOCS-960: Document ZTWA session ID correlation for recordings - #313
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughDocumentation-only update across three SRA Markdown files. Adds shared session ID correlation notes, records end-user identity in ChangesZTWA Session Correlation and Visibility Prerequisites
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
EldadH89
left a comment
There was a problem hiding this comment.
not addressing the main requirement, in order to get this to work (i.e. audit logs for ZTWA, with all benefits (session id correlation etc.)) the deployment MUST use the same cluser name and the same Access ID of the Gateway (which is running the SRA) , please make sure the relevant is highlighted in the deployment section of the ZTWA that for audit logs and session recording, this is the requirement
|
All comments addressed. |
Summary
sra_unique_identifier.Updated pages
Validation
Summary by CodeRabbit
Documentation
clusterNamematching, authentication, gateway certificate trust, and gateway registration status.