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

[RFE] Introduce a new option to parametrize how krb5 principals are created #2587

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

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

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

  • Created at 2012-09-26 23:19:35 by jhrozek
  • Closed as Invalid
  • Assigned to nobody

Users sometimes run into the situation where the user principal attribute in LDAP is populated, but points to a different realm than the user wants to utilize, typically a lab vs. production mismatch.

We should introduce a new option that would allow us to override the principal attribute and parametrize it, perhaps with similar expansions that are allowed in the ccname template.

Usually the user would just use user@SOMEOTHERREALM.COM anyway.

Comments


Comment from dpal at 2012-09-27 15:26:19

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10 beta
priority: major => minor
rhbz: => todo
summary: Introduce a new option to parametrize how krb5 principals are created => [RFE] Introduce a new option to parametrize how krb5 principals are created
type: defect => enhancement


Comment from dpal at 2012-12-20 23:33:42

Fields changed

selected: => Not need


Comment from dpal at 2013-01-02 15:32:09

Moving tickets that are not a priority for SSSD 1.10 into the next release.

milestone: SSSD 1.10 beta => SSSD 1.11 beta


Comment from dpal at 2014-09-26 18:49:56

Fields changed

mark: => 0


Comment from jhrozek at 2015-02-10 17:06:21

Fields changed

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: minor => trivial
review: => 0


Comment from jhrozek at 2015-02-12 20:36:05

Mass-moving tickets not planned for any immediate release and re-setting priority.

milestone: SSSD 1.13 backlog => SSSD Deferred
priority: trivial => major


Comment from jhrozek at 2016-11-17 11:29:35

This was not needed for four years, I suggest we just close the ticket.

review: 0 => 1
sensitive: => 0


Comment from jhrozek at 2016-11-17 11:30:41

Fields changed

blockedby: => 2887


Comment from jhrozek at 2016-11-17 11:31:02

Fields changed

blockedby: 2887 =>


Comment from jhrozek at 2016-11-25 09:45:36

Fields changed

resolution: => wontfix
status: new => closed


Comment from jhrozek at 2017-02-24 15:03:17

Metadata Update from @jhrozek:


Comment from jhrozek at 2017-03-03 11:57:42

Metadata Update from @jhrozek:

  • Custom field design_review reset
  • Custom field mark reset
  • Custom field patch reset
  • Custom field review adjusted to on (was: 1)
  • Custom field sensitive reset
  • Custom field testsupdated reset
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant