sending username to uniFLOW

[paul young]

Thank you Helge.

By the looks of your reply my answer is to bring this to the attention of the developers to stop sending jobs as the DBA but use current user instead.

I dont think they will be willing to do this without a manager giving a business case first. At least it is not to do with the settings I have applied when setting up the printers.

Regards

Paul

> paul young wrote:
>
> > Hi All,
> >
> > A slightly odd request I gather as google has no idea what I am trying to
> > do.
> >
> > We have cups 1.2.7 running and the company have now purchased two Canon
> > IR5000 printers.
> >
> > In order to keep the powers that be happy they would like me to enable PIN
> > control for each print sent to uniFLOW (Holding queue for canon printers).
> >
> > When printing from Windows you send a job to the print queue within
> > uniFLOW, the user can then walk up to any printer set up within uniFLOW
> > type in there PIN number and the print is sent to them.
> >
> > I have managed to configure cups to send jobs to uniFLOW but this is where
> > I hit problems. Every job sent from cups is sent as the system account
> > AISDBA. If left to me that would be fine, create an account within uniFLOW
> > for AISDBA and the users use the PIN for this account, but the managers
> > would like to point the finger at individuals that send jobs to the
> > printers if anything goes wrong.
> >
> > The company use an Ingres based application sat on the Solaris 10 server,
> > each user has individual logins for the application, what I would like to
> > know is:
> >
> > Is there a way to use these logins to send prints via cups?
> >
> > Any info on this would be great, if you need further details from me
> > please let me know, I realise the above is a little sparse.
> >
> > Regards
> >
> > Paul
>
> Every job submitted by CUPS has a job attribute
> job-originating-user-name
> which is - in a native UNIX environment - the login name of the user
> submitting the job to CUPS e.g. by the lp or lpr command.
> You need to do two things:
> 1) make sure that print jobs generated by applications are submitted under
> this same user name,
> 2) disable the use of the "-U" option of the lp or lpr command to prevent
> users to cheat which users they are.
>
> Helge
>