Skip to content

Commit fe2a4ac

Browse files
committed
Updated auth providers question to be more specific about which providers are supported
1 parent 3fb9871 commit fe2a4ac

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/pages/docs/octopus-cloud/frequently-asked-questions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ Octopus Deploy is not a covered entity under HIPAA. We do not process personally
9999
The security and privacy of our customers' personal, company, and intellectual property data are top priorities at Octopus. We're dedicated to maintaining and continuously improving our security and compliance programs, which we publish on our [Trust Center](https://octopus.com/company/trust).
100100

101101
### Which authentication providers are supported?
102-
Octopus Cloud supports the most common [authentication providers](/docs/security/authentication/auth-provider-compatibility#login-support) out of the box.
102+
Octopus Cloud supports these [authentication providers](/docs/security/authentication/auth-provider-compatibility#login-support) for login. We have narrower provider support for [external groups and roles](/docs/security/authentication/auth-provider-compatibility#external-groups-and-roles).
103103

104104
### What level of encryption is used between an Octopus Server and a Tentacle?
105105
All communication between the Tentacle and Octopus is performed over a secure TLS connection. We recommend TLS1.2+. We configure the [trust relationship](/docs/security/octopus-tentacle-communication) between Octopus Server and a Tentacle using public-key cryptography. The server and Tentacle establish the trust relationship using [X.509 self-signed certificates](/docs/security/octopus-tentacle-communication#Octopus-Tentaclecommunication-Octopuscertificates) generated upon installation and using 2048-bit private keys.

0 commit comments

Comments
 (0)