#1634 Extract the UPN from the pac
Closed: wontfix 2 years ago by pbrezina. Opened 10 years ago by simo.

We currently 'build' a UPN from samaccountname + domain for AD trust users in the ipa subdomain code. But we shouldn't as the UPN may be arbitrarily different in AD.
We should extract the UPN from the PAC and pass it down to the code that create the user in the database.

To test this go to the AD MMC and create a user named joe, but manually set the upn to be bob@domain.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10 beta

Fields changed

rhbz: => todo

It is also might be related to #1603

Fields changed

selected: => Want

Fields changed

priority: major => critical

Fields changed

owner: somebody => sbose

Fields changed

status: new => assigned

Fields changed

review: => 0

Fields changed

patch: 0 => 1

As discussed on the SSSD weekly meeting, we don't see a real world use case. The patch will be archived on the sssd-devel list in case we need to resurrect it.

milestone: SSSD 1.10 beta => SSSD Deferred

Metadata Update from @simo:
- Issue assigned to sbose
- Issue set to the milestone: SSSD Patches welcome

5 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

2 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2676

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.