[cups.general] LDAP Browsing & "Bad Printer URI"

[Adam Tauno Williams]

On Wed, 2012-06-13 at 23:46 -0400, Michael Sweet wrote:
> Adam,
> On Jun 13, 2012, at 8:13 AM, Adam Tauno Williams wrote:
> > I've added the CUPS schema to my LDAP DSA and created a cupsPrinter
> > object.  Then I pointed my CUPS server to BrowseRemoteProtocol ldap and
> > other related directives
> > I appears to discover the printer but in the error log I see 
> > Bad printer URI in browse data: ipp://lpd01996.dynamic.mormail.com/ipp
> > - and the printer queue is not available.  How is that a bad URI?  Do
> > URIs in LDAP objects need to be encoded in any special form
> The current LDAP support in 1.5.x and earlier expects printer URIs 
> of the form "ipp://servername/printers/name" or "ipp://servername/classes/name".

Ah, so it is really just for discovering queues on other CUPS servers,
not for sharing printer information to CUPS servers.

> CUPS 1.6 removes support for LDAP using the non-standard CUPS schema - 
> future versions will re-add this to the new printing APIs so that we 
> can discover compatible (shared or otherwise) printers using the 
> standard LDAP Printer schema...

Ok
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <https://lists.cups.org/pipermail/cups/attachments/20120615/a1d826cd/attachment.bin>