#2200 sssd_be aborts a request if it doesn't match any configured idmap domain
Closed: Fixed None Opened 8 years ago by jhrozek.

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

Description of problem:
Internal error in domain log for large id numbers

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Join sssd to the AD Server via realmd tool.
2. I see the message in domain logs with starting up sssd. Don't have the exact
reproducer right now.

Jakub, since you were able to access my system and submit patches, do you also
have a reproducer?

Actual results:
(Thu Jan 16 14:52:06 2014) [sssd[be[sssdad.com]]] [be_get_account_info]
(0x0100): Got request for [4097][1][idnumber=4294967295]
(Thu Jan 16 14:52:06 2014) [sssd[be[sssdad.com]]] [be_req_set_domain] (0x0400):
Changing request domain from [sssdad.com] to [sssdad.com]
(Thu Jan 16 14:52:06 2014) [sssd[be[sssdad.com]]] [ad_account_can_shortcut]
(0x0080): Mapping ID [4294967295] to SID failed: [IDMAP domain not found]
(Thu Jan 16 14:52:06 2014) [sssd[be[sssdad.com]]] [acctinfo_callback] (0x0100):
Request processed. Returned 3,5,Internal Error (Memory buffer error)

Expected results:

Additional info:

Fields changed

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

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

Additional patch:
- master: 6095e82
- sssd-1-11: 3a091bd

Fields changed

changelog: => N/A just a bugfix

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.11.4

5 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/3242

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.