Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
Members Portal
Members Portal
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Feneas
  • infrastructure
  • Members PortalMembers Portal
  • Issues
  • #8

Closed
Open
Opened Apr 14, 2019 by zauberstuhl@zauberstuhlOwner
  • Report abuse
  • New issue
Report abuse New issue

Do not store entire user in sessions

Everytime we change something we have to refresh all sessions e.g.:

  user.DeleteAllSessionsExcept(sessionToken)
  user.RefreshCache(sessionToken)

We should only store if a user authenticated and then do live queries. The result would be more load on the ldap server but we wouldn't run into data inconsistent if we forget to refresh the cache once.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
to do
Assign labels
  • View project labels
Reference: feneas/infrastructure/members-portal#8