Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A accounts.eclipse.org
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Eclipse Foundation
  • IT
  • Websites
  • accounts.eclipse.org
  • Issues
  • #15

Closed
Open
Created Aug 30, 2017 by Christopher Guindon@cguindonOwner

[Bug 521624] Accounts should maintain the state of the ECLIPSESESSION

Bugzilla Link 521624
Status NEW
Importance P3 normal
Reported Aug 30, 2017 11:42 EDT
Modified Sep 15, 2021 01:06 EDT

Description

When accounts.eclipse.org was deployed, one of the requirements was to create an ECLIPSESESSION after a user logs-in to support our current infrastructure.

For example, the Bugzilla manager for committers validate your access based off your ECLIPSESESSION.

Accounts.eclipse.org also creates a local Drupal session which can expire after the ECLIPSESESSION.

Accounts.eclipse.org should be able to detect that the ECLIPSESESSION has expired for a currently logged-in user and create a new session or update the expiry date of the previous session.

The main issue is that the ECLIPSESESSION is only created when the user successfully enter information on our login form. As long, as the drupal session is valid, it won't try to re-validate the ECLIPSESESSION.

Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent