Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,329
    • Merge requests 1,329
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #292811
You need to sign in or sign up before continuing.
Closed
Open
Issue created Dec 10, 2020 by Melissa Ushakov@mushakov🌻Developer0 of 6 checklist items completed0/6 checklist items

Improve SAML Timeout Experience

Problem to solve

We implemented the 7-day timeout for SAML groups for GitLab.com which requires users to re-auth into their SAML provider. This requires users to click to trigger a SAML log-in to check if they still have access to their IdP. This isn't the best user experience.

image

Proposal

We should improve this experience by making a request out to the SAML provider when the 7-day limit has expired and not require a user click to do so. This is a common pattern used in other enterprise applications.

Availability & Testing

What risks does this change pose to our availability?

This is a low risk feature for GitLab.com availability

What additional test coverage or changes to tests will be needed?

  • Ensure that users that have not yet SSO'd should still see the Sign-in screen on GitLab.
  • Simulate timeout for an already SSO'd user to ensure the Sign-in screen on GitLab is not shown.
Edited Dec 23, 2020 by Sanad Liaquat
Assignee
Assign to
Time tracking