GUACAMOLE-2039: Explain that other auth methods are possible in docker #269
Conversation
This file contains 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 is already on the way via the changes for GUACAMOLE-374, in particular #261 (which generalizes the documentation to cover Docker configuration alongside traditional native configuration). |
|
Closing per above. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Explicitly explain that other authentication methods, even such that are not explicitly documented as supported under Docker, are also possible to use, such as OpenID connect.
Technically, this doesn't add any new information since the "Configuring Guacamole when using Docker" section already explains using environment properties, but it does make this information easier to find.