The exception is if multiple people use the same device. And each have their own unique AT&T account.

I don't know if AT&T put in technical limitations so a shared device = shared account access - but the exception is a possibility that would prevent such a solution.

Personally - I think if we assume non-shared devices, we're back in MS' "hey... only one person will ever use the computer, we don't need no protection on the device such as privately owned files".

[ Reply to This | Parent | # ]

• Good solution with one exception - Authored by: stegu on Thursday, July 04 2013 @ 12:34 PM EDT
• The exception is no problem - Authored by: bugstomper on Thursday, July 04 2013 @ 06:13 PM EDT

Or better yet, go with what's already there. Browsers these days have the ability to remember username/password combinations for Web sites. So code your login form using standard terminology so the browser can easily and correctly fill in the fields for the user. Fields now get automatically filled in, multiple accounts get handled automatically by letting the user select from the browser's pull-down completion list, and there's no possibility of someone else finding out what that user's filling in. Or if the information's filled in via a cookie or by correlation with a device ID, just ask for the password and provide a "Not $X? Click here to log in as a different user." link.

[ Reply to This | Parent | # ]