Difference between revisions of "Papercut"
Jrobertson (talk | contribs) |
|||
Line 28: | Line 28: | ||
Download the metadata from here enter the FQDN for your IIS Server followed by /Shibboleth.sso/Metadata (For iis.domain.vm the URL would be iis.domain.vm/Shibboleth.sso/Metadata) and then [https://wiki.studentnet.net/index.php?title=XML_file_upload| upload the XML file] | Download the metadata from here enter the FQDN for your IIS Server followed by /Shibboleth.sso/Metadata (For iis.domain.vm the URL would be iis.domain.vm/Shibboleth.sso/Metadata) and then [https://wiki.studentnet.net/index.php?title=XML_file_upload| upload the XML file] | ||
+ | |||
+ | |||
+ | [[Category:Single Sign On]] |
Revision as of 03:40, 5 August 2019
PaperCut is a print and copy output management software
Setup
Background
There are a number of places where PaperCut authenticates users, which occurs before the document is printed, at the time of printing and after printing. Before printing:
- Administrate PaperCut or view reports through the admin web interface
- End users visit the user web interface to submit web print jobs, view statistics and top up their account for example.
- Identify the owner of a print job, whether they print from a managed, shared or self managed BYOD device
At the time of printing:
- Authenticate the user at the release station, through methods like username and password, card swipe, two factor authentication with card and pin or even biometric options.
Add accountability to the document forever:
Optionally apply a watermark / digital signature to all pages, which adds an encrypted HMAC signature to the page which can be traced back to the user who printed the document. When authenticating users, PaperCut interfaces directly with directory services like Active Directory or LDAP. Additionally, you can also configure single sign-on on the admin web interface and user web interface, where PaperCut will rely on an external SAML service for authentication.
IIS Configuration (Shibboleth)
If you have not already done so install IIS onto either the PaperCut Application Server or a different server. If you install IIS onto the PaperCut Application Server make sure you have not configured PaperCut MF to use port 80 or 443 and make sure you don’t tell IIS to use any of the standard PaperCut ports (9191, 9192, 9193).
You will need to make sure that you have ISAPI Extensions and ISAPI Filters installed on IIS which can both be found under Add Server Roles > Web Server (IIS) > Web Server > App Development
Cloudwork Configuration
Download the metadata from here enter the FQDN for your IIS Server followed by /Shibboleth.sso/Metadata (For iis.domain.vm the URL would be iis.domain.vm/Shibboleth.sso/Metadata) and then upload the XML file