Red Hat Bugzilla – Bug 1468997
During the configuration of the smb backend credential verification doesn't work
Last modified: 2018-05-03 04:01:38 EDT
Description of problem:
1. Windows ADS
a) Install a Windows Active Directory Server (Windows 2012 here)
b) Create a printer on the Windows 2012 server (e.g. Virtual PDF Printer with
c) Share the printer over the network
2. Install Fedora
a) Install a Fedora distribution
b) Install samba, samba-krb5-printing and cups
c) Join the machine to AD (net ads join)
d) Setup winbind with authconfig
e) Configure CUPS
* Stop cups with:
systemctl stop cups.service; systemctl stop cups.socket; \
systemctl stop cups.path
* Edit '/etc/cups/cupsd.conf' and change 'DefaultAuthType Basic' to
Make sure you have:
* Start cups again with 'systemctl start cups.service'
* Start system-printer-config as root
* Click on 'Add' to add a printer
- Select 'Windows Printer via SAMBA'
- Add the smb url: win-dc02.earth.milkyway.site/FreePDF
- Make sure in Authentication that 'Prompt user if authentication is
requried' is selected
* Click on "Verify"
There should be a pop up asking for credentials to authenticate against Windows.
Instead of using Windows, you can use a Samba AD.
Either install rawhide (f27) or use the packages from https://copr.fedorainfracloud.org/coprs/asn/samba_ad_dc/
You need to install the package 'samba-dc' and then provision the DC with samba-tool.
This is described here:
If it is up and working, create a printer:
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.