Michael,
What do I need to do to include the "username" parameter in the WWW-Authenticate
header value?
Thanks,
-Rick
On 8/28/15, 1:42 PM, Michael Sweet wrote:
Rick,
There is no way to change this behavior, short of including the "username"
parameter in the WWW-Authenticate header value (which tells the client what the default
username is...)
Since Printer Sharing is the primary use case of authenticated printing, it
*does* make sense to pre-populate with your local user name since that is
typically a network user account. But feel free to argue otherwise in a bug
report... :)
https://bugreport.apple.com
On Aug 28, 2015, at 12:47 PM, Rick Cochran <[email protected]> wrote:
We have noticed the following:
1) When a user prints, and OS X prompts them for their ID and password, OS X
pre-populates the "Name:" field with the user's login ID from their
workstation, thus causing them to believe they should be entering their workstation
password.
2) Not only does OS X pre-populate the "Name:" field with the wrong thing the
first time they print - it does it every subsequent time also.
This is very confusing to our users. It is odd that OS X would pre-populate an
ID in a prompt for an external service.
Is there any way to change this behavior? We do not consider "checking" the
"Remember this password" box to be a universally appropriate solution.
Thanks,
-Rick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Printing mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/printing/msweet%40apple.com
This email sent to [email protected]
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Printing mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/printing/archive%40mail-archive.com
This email sent to [email protected]
