CUPS doesn't hold jobs using a password, preventing iOS clients from displaying the PIN needed to release them.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing Discussion 1453 and the attached error_log.txt, then trace CUPS handling of the job-password attribute. Confirm the behavior for password-protected jobs and verify that a short hold allows iOS clients to display the generated PIN before release.
Written by the indexing model from the issue text.
Description
Need to implement a short (10-30 second) hold for jobs using the job-password attribute for PIN/passcode/password printing, otherwise iOS clients won't show the PIN they generated.
Discussed in https://github.com/OpenPrinting/cups/discussions/1453
Originally posted by mdk6c December 10, 2025
We are trying to implement PIN release printing in CUPS for iOS devices.
We have added the following to the bottom of our PPD file, as per the documentation.
*cupsMandatory: "job-password job-password-encryption"
*cupsJobPassword: "1111"
Our printer is visible from iOS devices and the print options sheet shows "This printer requires a PIN to print" as expected.
However, when we tap "Print" to submit the print job, no PIN is ever presented to the user via the expected iOS PIN dialog (screenshot below).
I can see from the error_log that a job password is being generated and passed along to the filters.
Maybe this issue is on the iOS side, not CUPS. I'm sorry to report it as a bug. But we have found scant guidance or implementation examples for PIN printing in our research thus far.
- Dominant language
- C
- Stars
- 1.8k
- Forks
- 362
- Avg merge
- 1d 46m
- Merged PRs (30d)
- 10
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenPrinting/cups
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenPrinting/cups#1826 ·
Maintainers usually reply within 1 day
-
OAuth (bearer) quota check denies every user when the allowed-user list is emptyPossibly taken @RonitMehta08 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
OpenPrinting/cups#1795 · 1 comment ·
Maintainers usually reply within 1 day
-
cupsdGetPrivateAttrs: @ACL never grants access, and @OWNER is looked up as an operating-system group for non-ownersPossibly taken @user-Param claimed this 7 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
OpenPrinting/cups#1796 ·
Maintainers usually reply within 1 day
-
OAuth/OIDC token-validation gaps: nonce not enforced when absent, at_hash alg, inbound bearer not signature/aud/exp-validated + unverified email used for authzMay be free again @michaelrsweet claimed this 145 days ago, and no pull request is open. Openinvestigating
OpenPrinting/cups#1609 · 1 assignee ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 52/100
OpenPrinting/cups#1572 ·
Maintainers usually reply within 1 day
All issues in OpenPrinting/cups
Similar issues
-
`sha256()` returns a wrong hash when libsql-ffi is built with gcc 11 or laterPossibly taken @colinhacks claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tursodatabase/libsql#2333 ·
Maintainers usually reply within 11 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Backport to 3.0 advertises a suffix that does not existPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
389ds/389-ds-base#8152 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RetroAchievements/rcheevos#580 · 1 comment ·
Maintainers usually reply within 5 days
-
meta:feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mpv-player/mpv#18855 · 2 comments ·
Maintainers usually reply within 1 day