{'fraction_non_alphanumeric': 0.030141843971631204, 'fraction_numerical': 0.0070921985815602835, 'mean_word_length': 4.880208333333333, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Web OAuth-based SSO Systems Security

In the present digital world, users have to access multiple applications for carrying out their day-to-day business activities. As the amount of apps increase, the number of credentials (e.g. username/password) for each user increases and thereby the possibility of losing or forgetting them also increases. Single Sign-On (SSO) can be used to solve many problems related to web user authentication. OAuth-based SSO Systems are widely deployed by big tech companies such as Facebook and Google. In this paper we provide an in-depth review analysis of OAuth-based SSO systems security issues. In fact, previous efforts have been aimed either at finding errors in specific implementations, or at finding security problems within the specification itself. The main paper contribution is twofold: (1) describe in detail the OAuth 2.0 authorization flows and summarize the differences between the flows of each scenario that affect the security of the OAuth 2.0 protocol, and (2) examine the security problems related to the OAuth 2.0 specification and its implementation in the Web environment.