|
+8.1.1 General Usability Considerations |
8.1.1 General Usability ConsiderationsFederated identity systems should: Minimize user burden (e.g., frustration, learning curve)
Minimize the number of user actions required.
Allow users to quickly and easily select among multiple subscriber accounts with a single IdP. For example, an account chooser [ACCOUNT-CHOOSER] allows users to select from a list of subscriber accounts that they have accessed in the recent past rather than start the federation process by selecting their IdP from a list of potential IdPs.
Balance minimizing user burden with the need to provide sufficient information to enable users to make informed decisions.
Minimize the use of unfamiliar technical jargon and details (e.g., users do not need to know the terms IdP and RP if the basic concepts are clearly explained, and users do not need to know the specific FAL value if its effects are clearly communicated). Strive for a consistent and integrated user experience across the IdP and RP, particularly when in a single security domain. Help users understand identity by providing resources, such as graphics, illustrations, frequently asked questions (FAQs), tutorials and examples. Resources should explain how users’ information is treated and how transacting parties (e.g., RPs, IdPs, proxies) relate to each other. Provide clear, honest, and meaningful communications to users (i.e., communications should be explicit and easy to understand). Provide users with online services that are independent of location and device. Make trust relationships explicit to users to facilitate informed trust decisions. Trust relationships are often dynamic and context-dependent. Users may be more likely to trust some IdPs and RPs with certain attributes or transactions more than others. For example, users may be more hesitant to use federated identity systems on websites that contain valuable personal information (e.g., financial or health). Depending on the perceived sensitivity of users’ personal information, some users may be less comfortable with commercial IdPs since people often have concerns about advertising and the data usage of such companies. Conversely, some may have more confidence in commercial IdPs than in government IdPs based on a general mistrust of government services or because they are more familiar with commercial offerings. Either way, it is critical to be clear to end users about the entities involved in a federation transaction and, ideally, provide options that support the broadest set of stakeholder perceptions possible. Follow the usability considerations specified in [SP800-63A] Sec. 8 for any user-facing information. Clearly communicate how and where to acquire technical assistance. For example, provide users with a link to an online self-service feature, chat sessions, or a phone number for help desk support. Avoid redirecting users back and forth between transacting parties (e.g., RPs, IdPs, and proxies) to receive technical assistance. Perform integrative and continuous usability evaluations with representative users and realistic tasks in an appropriate context to ensure the success of federated identity systems from the users’ perspectives.
1. Resumen
1.1 Referencias1.2 Requisitos identificados1.3 Regulaciones relacionadas2. Requisitos identificados
3. Regulaciones relacionadas
|