Application Bridging for Federated Access Beyond web (ABFAB) Usability and User Interface Considerations
draft-ietf-abfab-usability-ui-considerations-04

Document Type Expired Internet-Draft (abfab WG)
Last updated 2016-09-22 (latest revision 2016-03-21)
Replaces draft-smith-abfab-usability-ui-considerations
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-abfab-usability-ui-considerations-04.txt

Abstract

The real world use of ABFAB-based technologies requires that any identity that is to be used for authentication has to be configured on the ABFAB-enabled client device. Achieving this requires software on that device (either built into the operating system or a standalone utility) that will interact with the user, managing their identity information and identity-to-service mappings. All designers of software to fulfil this role will face the same set of challenges. This document aims to document these challenges with the aim of producing well-thought out UIs with some degree of consistency between implementations.

Authors

Rhys Smith (smith@cardiff.ac.uk)
Mark Donnelly (mark@painless-security.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)