I added a note to the SSSD docs at https://discourse.ubuntu.com/t/sssd-
and-active-directory/27888 which will be live in ubuntu.com/server/docs
shortly. I almost changed my mind, since the bug will eventually be
fixed and then it won't be needed in the docs anymore. I'll remove the
note again once
I also just added an entry to the 22.04 release notes at
https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668
** Changed in: serverguide
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I added a task to, in the meantime, update the server guide with the
available workarounds for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934997
Title:
Authentication fails after upgrading
These releases have the fix:
$ git tag --contains 81d67a592315740d13e48b9a29e29baa8cc35638
2.7.0
2.7.1
** Tags added: server-todo
** Also affects: serverguide
Importance: Undecided
Status: New
** Changed in: serverguide
Status: New => Confirmed
** Changed in: serverguide
https://github.com/SSSD/sssd/pull/6051/files seems to be the new PR to
address this, and it's closed. Have to check if it was merged into one
of the stable release branches, or even better, if it's part of a
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Still waiting on upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934997
Title:
Authentication fails after upgrading sssd to 2.2.3-3ubuntu0.6
To manage notifications about this bug go to:
** Changed in: sssd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934997
Title:
Authentication fails after upgrading sssd to 2.2.3-3ubuntu0.6
To manage notifications
** Bug watch added: github.com/SSSD/sssd/issues #5716
https://github.com/SSSD/sssd/issues/5716
** Also affects: sssd via
https://github.com/SSSD/sssd/issues/5716
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs,
OK, after spending a few hours investigating this bug I think I can
write a summary of my findings now.
First, thanks everybody who have commented on the bug.
It took me a while to set up a local Samba AD DC with GPO enabled in a
VM, and then a container which joins the AD using SSSD (realm +
** Bug watch added: Red Hat Bugzilla #1839805
https://bugzilla.redhat.com/show_bug.cgi?id=1839805
** Also affects: sssd (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1839805
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934997
Title:
Authentication fails after upgrading sssd to 2.2.3-3ubuntu0.6
To manage notifications about this bug
I just got hit by this. While 'ad_gpo_access_control = permissive' lets
users log in again, it is not ideal.
It appears that Samba AD does not create GptTmpl.inf except for policies
which actually set something in "Security Settings". Hence a policy with
nothing no security settings will not have
Hello,
I have the same issues on a fleet on Ubuntu 20.04 machines joined to a
Univention Corporate Server domain. UCS uses Samba4 as a background.
Is there any security concern about the 'ad_gpo_access_control =
permissive' or 'access_provider = permit' in sssd.conf?
Thank you for looking into
We found issues too and work around it by using 'access_provider =
permit' instead of 'access_provider = ad'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934997
Title:
Authentication fails after
Thank you for your report and sorry for the issue caused by this SRU.
In focal GPO are enforced by default. But the original version of SSSD
was not fully implementing the MS spec and GPO where actually not
enforced. This was the case for the default domain policy which defines
in particular the
** Changed in: sssd (Ubuntu)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934997
Title:
Authentication
16 matches
Mail list logo
