Comment 5 for bug 1468422

If we are going this way I think we should modify authenticate.init to support *optional* specifying of username vs barcode (in a new type param, perhaps?) so that an interface that should only ever be accepting one of the two (say, the staff client only wanting usernames) doesn't get tripped up by the backend trying to guess and getting it wrong. If you haven't specified which on the init call then attempt auto-detect. Then we can change the complete call to make that information optional there as well or ignore it and always use what the init call actually used (stored in memcache?).