{'fraction_non_alphanumeric': 0.022900763358778626, 'fraction_numerical': 0.0, 'mean_word_length': 5.526970954356846, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Time-out Management in Multi-domain Single Sign-On A Paper Highlighting Integration Issues in Single Sign

Single Sign-On (SSO) enables a single set of user credentials to be used for authentication and authorization across multiple computing applications or domains, whether they are web-based, enterprise applications, centrally located or geographically dispersed. Depending on the security requirements of specific applications within the SSO system, different applications may require diverse SSO authentication time-out periods (the period of which a user is still considered authenticated to the system). Furthermore, each web-based application participating in an SSO system manages its' own session/application state information. Such state is typically not shared across domain boundaries and is usually associated with a specific user. A user may be authenticated to one or more domains that participate in the multi-domain SSO system, but in the course of navigating between the multiple domains, the underlying state information specific to a given user may become orphaned, leaving an SSO authenticated user with lost associated state. This work identifies several issues in authentication time-out management and session/application state time-out management specific to multi-domain SSO systems, and introduces the concept of a policy controller to manage application token and session state lifetime in a multi-domain SSO environment. A policy controller is described and several example authentication and session state time-out policies are illustrated.