#1545 [RFE] Introduce a new option to parametrize how krb5 principals are created
Closed: Invalid None Opened 6 years ago by jhrozek.

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.


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

Fields changed

selected: => Not need

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

milestone: SSSD 1.10 beta => SSSD 1.11 beta

Fields changed

mark: => 0

Fields changed

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

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

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

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

review: 0 => 1
sensitive: => 0

Fields changed

blockedby: => 2887

Fields changed

blockedby: 2887 =>

Fields changed

resolution: => wontfix
status: new => closed

Metadata Update from @jhrozek:
- Issue marked as depending on: #2887
- Issue set to the milestone: SSSD Patches welcome

2 years ago

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

2 years ago

Login to comment on this ticket.

Metadata