This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Ports and protocols
The network ports that a Citrix SecurSpaces™ deployment exposes, for firewall rules and network security review.
Externally exposed ports
These are the only ports that need to reach the cluster from your network.
| Port | Protocol | Purpose |
|---|---|---|
| 443 | HTTPS | The SecurSpaces console, the API, and workspace applications served through the proxy host name |
| 80 | HTTP | Redirects to HTTPS |
| Your choice, commonly 22 | TCP, carrying SSH | Remote development over SSH. Forwarded by the ingress controller to the workspace API. |
TLS is terminated at the ingress controller. The permitted TLS versions and cipher suites are therefore set by your ingress configuration, not by SecurSpaces.
SSH port forwarding
SecurSpaces does not fix the external SSH port. You choose it when you configure TCP forwarding on the ingress
controller, and the ingress forwards it to port 2222 on the workspace API.
| Side | Port |
|---|---|
| External | Whatever you configure on the ingress controller. Commonly 22. |
| Internal, on the workspace API | 2222 |
Important:
Port
2222is hardcoded in the workspace API. Do not change it.
For the configuration steps, see Enable SSH access to workspaces.
Internal service ports
SecurSpaces services communicate over additional ports inside the cluster, including gRPC and HTTP ports on the central, coordinator, monitor, workspace, and proxy services. These are cluster-internal. They do not need to be reachable from outside the cluster, and you can restrict them with Kubernetes Network Policies.
For how SecurSpaces uses network policies to control workspace traffic, see Network policies.
Related information
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.