Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Kerberos provider is not properly views-aware #3552

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

The Kerberos provider is not properly views-aware #3552

sssd-bot opened this issue May 2, 2020 · 0 comments
Assignees
Labels
Bugzilla Closed: Fixed Issue was closed as fixed.

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2510


Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1168735

Description of problem:
The Kerberos provider does not handle views properly. This can result in
strange behaviour, like the ccache being created with the original UID instead
of the overriden one.

Version-Release number of selected component (if applicable):
sssd-1.12.2-28.el7

How reproducible:
always

Steps to Reproduce:
1. Assign an UID override on the server side
2. Log in to the client. Run "id" to make sure the ID is as expected
3. run klist

Actual results:
An error message, complaining that ccache is not present in the keyring for the
specified UID

Expected results:
The ccache should be printed correctly.

Additional info:

Comments


Comment from jhrozek at 2014-11-27 18:11:33

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
owner: somebody => sbose
patch: 0 => 1
review: True => 0
selected: =>
testsupdated: => 0


Comment from jhrozek at 2014-12-02 11:50:16

This was a bug in the views feature. I think it's OK to bypass the triage and put the ticket into 1.12 directly:
- b708821
- 2bf1cbf
- 61d2ccf

milestone: NEEDS_TRIAGE => SSSD 1.12.3
resolution: => fixed
status: new => closed


Comment from jhrozek at 2017-02-24 14:38:44

Metadata Update from @jhrozek:

  • Issue assigned to sbose
  • Issue set to the milestone: SSSD 1.12.3
@sssd-bot sssd-bot added Bugzilla Closed: Fixed Issue was closed as fixed. labels May 2, 2020
@sssd-bot sssd-bot closed this as completed May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bugzilla Closed: Fixed Issue was closed as fixed.
Projects
None yet
Development

No branches or pull requests

2 participants