Soma,
On Apr 9, 2014, at 12:13 AM, Soma Meiyappan <Soma.Meiyappan at conexant.com> wrote:
> Mike/Pete,
>> May I know how PWG solves supporting IPP destinations (and other HTTP destinations) that need authentication when used as a destination in FaxOut/Scan2 defined workflows?
It is currently undefined at the protocol level (meaning that it is up to each implementation to do something about it), just as how to deal with authentication of document URIs is at present.
This is pending work in the IDS workgroup. CUPS has the "auth-info" and "auth-info-required" attributes, as well as a job-state-reasons keyword and IPP operation as extensions to IPP for dealing with authentication for a printer's output device (usually another computer/server that is sharing a print queue), but there are practical limitations to the approach.
> Are authentication information for URIs under destination-uri-ready (implicitly) managed by the MFD as it appears that the specification does not provide any destination specific attributes in the destination-uri collection to provide authentication credentials? Or should authentication information be provided in the URI as it is done for some http URI allows like http://user:passwd@mystoragedrive.com/folder? If so, I would wonder about IPP destinations and ipp/ipps URIs.
>
Embedding user credentials in HTTP and IPP URIs is not recommended, and in fact the current HTTP and IPP URI scheme definitions forbid it.
(FWIW, CUPS also supports this kind of authentication for the output device URI, but we've had to go through a lot of hoops over the years to hide the information from prying eyes. Definitely not recommended!)
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20140409/782a5fcd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4881 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20140409/782a5fcd/attachment.p7s>