Repository navigation
Maintenance: Document the FQDN requirement for the real-time channel. - #933
Merged
Merged
Conversation
The legacy WebSocket authenticates from the session cookie of its handshake and only trusts it when the Origin header matches <http_type>://<fqdn> (lib/sessions/event/login.rb in zammad/zammad; see also the BREAKING_CHANGES.md entry "The legacy WebSocket login is authenticated from the session cookie and signshow no longer returns session_id"). An instance opened with an IP address or with a host name that differs from the FQDN setting therefore has no authenticated real-time channel, which shows up as ticket changes that cannot be saved. The webserver configuration page now states the requirement for server_name and ServerName, and the troubleshooting section names the symptom.
ArtifactsProduced during runtime |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The legacy WebSocket authenticates from the session cookie of its handshake and only trusts it when the Origin header matches <http_type>:// (lib/sessions/event/login.rb in zammad/zammad; see also the BREAKING_CHANGES.md entry "The legacy WebSocket login is authenticated from the session cookie and signshow no longer returns session_id").
An instance opened with an IP address or with a host name that differs from the FQDN setting therefore has no authenticated real-time channel, which shows up as ticket changes that cannot be saved. The webserver configuration page now states the requirement for server_name and ServerName, and the troubleshooting section names the symptom.