'held for authetication'

[Jen Roidt]

> Jen,
>
> On May 14, 2012, at 7:57 AM, Jen Roidt <jenr at cooperfarms.com> wrote:
> >> ...
> >> I don't know the cause of this issue, but here is the command line
> >> workaround:
> >>
> >> lp -i jobid -H resume
> >>
> >> where jobid is the numeric job number of the held job.
> >>
> >> Helge
> >>
> >
> > thank you Helge. I have to admit I was skeptical about this answer as we've had to put a username & Password in on the gui screen to release it but this seems to work as well.
>
> When releasing from the command-line you don't normally need to authenticate because we can pull your credentials from the connection (i.e. you are logged in as user "jen" with UID 501).
>
> When going from the web interface there is no passing of your login status or UID, so we have to revert to re-authentication.
>
> __________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>

That makes sense - now if we can just get these jobs to not be stuck there waiting for authentication in the first place, our users would be much happier.