[Expired for sssd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: sssd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742752
Marking Incomplete pending an answer to comment 12.
** Changed in: sssd (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742752
Title:
system error(4)
I think not, that's normal for the first kinit if the client doesn't
know that the server requires preauth. It will just adapt and request it
again.
You may have to bump the logging level, although the manpage doesn't
mention this (search for ad_gpo_access_control in
I think not, that's normal for the first kinit if the client doesn't
know that the server requires preauth. It will just adapt and request it
again.
You may have to bump the logging level, although the manpage doesn't
mention this (search for ad_gpo_access_control in
I only see this line in /var/log/syslog for a recent login. Not sure if related.
[sssd[krb5_child[29420]]]: Preauthentication failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742752
Title:
With the new packages and in "permissive" mode, you should be getting
log messages about why a certain user would have been denied access.
These might land in /var/log/syslog, or perhaps an sssd specific logfile
in /var/log/sssd/*. Could you please check?
--
You received this bug notification
With the new packages and in "permissive" mode, you should be getting
log messages about why a certain user would have been denied access.
These might land in /var/log/syslog, or perhaps an sssd specific logfile
in /var/log/sssd/*. Could you please check?
--
You received this bug notification
Just in case it could help. When I used the old packages it worked again
but I had problems from time to time so I upgraded to the latest
packages and used the "ad_gpo_access_control = permissive" workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for switching it out of "incomplete". I'm sorry I couldn't get
back to it yet, but it's in my list.
** Changed in: sssd (Ubuntu)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member
Thanks for switching it out of "incomplete". I'm sorry I couldn't get
back to it yet, but it's in my list.
** Changed in: sssd (Ubuntu)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member
** Changed in: sssd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742752
Title:
system error(4) since latest update on xenial
To manage notifications
Should this bug report still marked as Incomplete?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742752
Title:
system error(4) since latest update on xenial
To manage notifications about this bug
Yes downgrade works.
I disabled "ad_gpo_access_control = permissive". Rebooted. Wasn't able
to login with a token.
Downgraded, rebooted. Was able to login with a token.
% dpkg -l | grep 1.13.4-1ubuntu1.9
ii libipa-hbac01.13.4-1ubuntu1.9
amd64
Thanks for these files.
If you downgrade sssd back to the 1.13.4-1ubuntu1.9 version, you can
then remove "ad_gpo_access_control = permissive" from sssd.conf and it
works? Can you confirm that?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Thanks for these files.
If you downgrade sssd back to the 1.13.4-1ubuntu1.9 version, you can
then remove "ad_gpo_access_control = permissive" from sssd.conf and it
works? Can you confirm that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1742752/+attachment/5035331/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742752
Title:
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1742752/+attachment/5035329/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742752
Title:
** Attachment added: "dpkg.log"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1742752/+attachment/5035332/+files/dpkg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742752
Title:
** Attachment added: "sssd.conf"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1742752/+attachment/5035330/+files/sssd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742752
Title:
Thanks for filing this bug in Ubuntu.
This last update didn't touch AD settings, so you might have been running an
even older version. Could you attach to this bug these log files please:
- /var/log/dpkg.log
- /var/log/apt/term.log
- /var/log/apt/history.log
Could you also please share your
Thanks for filing this bug in Ubuntu.
This last update didn't touch AD settings, so you might have been running an
even older version. Could you attach to this bug these log files please:
- /var/log/dpkg.log
- /var/log/apt/term.log
- /var/log/apt/history.log
Could you also please share your
21 matches
Mail list logo
