389-ds-base

#180 RFE: synchronise userPrincipalName attribute
Closed: wontfix by mreynolds. Opened by rmeggins.

Closed: wontfix
Reopen Issue

https://bugzilla.redhat.com/show_bug.cgi?id=746643

In RHDS 8.2 (and 9.0 AFAIK), winsync does not copy across the userPrincipalName
attribute from AD to RHDS.  This is unfortunate because there is no easy way
when using pam_passthru to distinguish between users from multiple different AD
domains and then pass these off to PAM.  Including the userPrincipalName as a
synchronised attribute is a low cost way to bring a globally unique attribute
per user into RHDS when synchronising with multiple AD domains.

batch update moving tickets to future

set default ticket origin to Community

Added initial screened field value.

Metadata Update from @rmeggins:
- Issue set to the milestone: FUTURE

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None (was: Needs Review)
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

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

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/180

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.
Metadata
None
None
None
None
Normal
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.