-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Closed
Labels
Feature:Security/AuthenticationPlatform Security - AuthenticationPlatform Security - AuthenticationTeam:SecurityPlatform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//Platform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experience
Description
Original comment by @pickypg:
!LINK REDACTED
A look at the cookies for the initial proxied request (running via npm start) via a look at the login page's redirect:
!LINK REDACTED
They all seem to follow the same pattern. The login page itself gets the same cookie without the empty, secure sid.
@lukasolson guessed that I had used Kibana + X-Pack without SSL in the past, which is 100% correct. This lead to an insecure sid cookie, which seems to cause trouble when SSL suddenly gets turned on.
Manually deleting the cookie resolved the issue (as did private browsing).
Metadata
Metadata
Assignees
Labels
Feature:Security/AuthenticationPlatform Security - AuthenticationPlatform Security - AuthenticationTeam:SecurityPlatform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//Platform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experience