An issue was discovered in Mattermost Server before 3.0.2. The purposes of a session ID and a Session Token were mishandled.