Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums
  • Feature tour
    Feature tour

Content

You are here:
  1. Forums
  2. General discussion

Expiration of SSO (single sign-on) login with Google

Added by Robert Kossatz over 3 years ago

Good morning community.

We are using SSO with Google on openproject. Usually, we have to log in again every morning, so I assume that a SSO login is valid for 24 hours. But yesterday I had to log in to openproject 4 or 5 times throughout the working day. Has something changed or does anyone know how we can keep SSO logins active for a longer time?

Best regards,
Robert


Replies (2)

RE: Expiration of SSO (single sign-on) login with Google - Added by Max Mutzge over 3 years ago

Hi Robert,

Have you checked the setting "session expires" here, yet?

Kind regards

RE: Expiration of SSO (single sign-on) login with Google - Added by Robert Kossatz over 3 years ago

Thank you Matthias. We managed to fix it. Case closed :-)

  • (1 - 2/2)
Loading...