[cups.bugs] [MOD] STR #3042: User should be per-connection

[Michael Sweet]

[STR Closed w/o Resolution]

Marking as a dupe of STR #2953.

Ultimately the user information *may be* stored in the opaque http_t data
structure, however this is not always the case since only HTTP Basic and
Digest authentication use it.  The cupsDoAuthentication API is used to
manage when a username and password are needed.  In addition, the current
cupsUser value (which is per-thread) is used for most of the convenience
functions, separate from the http_t structure.

So, in this context having a CUPS API that only sets the http_t
authentication information (of which the username is only a single piece
of information and not even used in all auth types) does not make sense.

What will likely happen is that the revised
cupsSetPasswordCallback/cupsDoAuthentication APIs will return both the
username and password to use. Users of the original versions will
automatically get the username via cupsUser/cupsSetUser.

Link: http://www.cups.org/str.php?L3042
Version:  -feature
Fix Version: None