Help Center
Help Center
Getting Started and Quick Guides
Users
Administrators
🧩Area: Administrators
🎓 Administrator Onboarding
SecuMails
Outlook Add-In (Classic Outlook)
Outlook Add-In (new Outlook)
FTAPI Gateway
Trust Networks
SecuRooms
SecuRooms Drive
SecuForms
Server Settings
General Server Settings
Templates
Miscellaneous
❓ User Management: Why can't certain users log in?❓ License Management: Understanding SecuMail and SecuRooms Licenses❓ License Management: Understanding and Managing Trial Licenses❓ Reports: The user report for an overview of all accounts❓ Security: Premium Virus Scanner (G DATA) and MIME Type Check❓ Security: What is Double-Authenticated Registration (DAR)?❓ Security: How does two-factor authentication (2FA) work at FTAPI?❓ Storage Quota: How group settings affect storage consumption❓ SSO: Why does the user have to log in again daily despite Single Sign-On?❓ System: Is the WebUI of the cloud instance protected by an SSL certificate?❓ System: How do I get informed about maintenance work and availability?📋 Unlocking users in the FTAPI platform❓ What to do in case of "Insecure Connection" / Expired SSL Certificate?❓ Security notifications: What does "@non_existing_user" mean in the message?
Download Center
Changelog

❓ SSO: Why does the user have to log in again daily despite Single Sign-On?

This article explains why a daily re-login might be required when using Single Sign-On (SSO) and which steps are necessary to reduce the login frequency.

Why does the user have to log in again daily?

The configured validity period of the SAML authentication token influences the frequency with which a user must log in to the server again. By default, the FTAPI server only accepts tokens for a specific period, usually 24 hours (1440 minutes). After this time has elapsed, re-authentication is required.

Cause: Conflict of the token validity period (token lifetime)

A common reason for the necessity of a daily re-login is that the token lifetime in your Identity Provider (IdP), such as Microsoft Azure AD, is set too short. If your IdP defines a longer token lifetime than the FTAPI server accepts, the smaller value is applied in each case. The FTAPI server then rejects the token because it falls below the maximum validity period configured on the server side.

Solution: Adjusting the token lifetime

To reduce the login frequency, the token lifetime in your Identity Provider (IdP) should primarily be adjusted accordingly.

After you have adjusted the token lifetime in your Identity Provider (e.g., Microsoft Azure AD), please inform us of the new, desired value for the validity period via a support ticket. Our support team will make the corresponding adjustment to your FTAPI server for you.

Important: Increasing the token lifetime can affect security. Check whether adjusting the IdP settings represents a safer alternative.

Related articles

📋 SSO: Adjusting token lifetime on the ADFS server via PowerShell and console

Was this article helpful?

English
Powered by Product Fruits