#1466 Proxy: Cannot retrieve an user after a group he is a member of was retrieved
Closed: Fixed None Opened 7 years ago by jhrozek.

I found this issue while testing one of the patches on the list.

The reproducer is simple. First retrieve a group that contains at least one user. Then try to get one of the members.

The proxy provider would fail:

[sssd[be[proxy]]] [be_get_account_info] (0x0100): Got request for [4097][1][name=username]
[sssd[be[proxy]]] [get_pw_name] (0x0400): Searching user by name (username)
[sssd[be[proxy]]] [handle_getpw_result] (0x0400): User found: (username, 1234, 1234)
[sssd[be[proxy]]] [handle_getpw_result] (0x0400): User found: (username, 1234, 1234)
[sssd[be[proxy]]] [sysdb_search_user_by_name] (0x0400): No such entry
[sssd[be[proxy]]] [sysdb_search_user_by_uid] (0x0400): No such entry
[sssd[be[proxy]]] [sysdb_error_to_errno] (0x0020): LDB returned unexpected error: [No such attribute]
[sssd[be[proxy]]] [sysdb_add_user] (0x0400): Error: 14 (Bad address)
[sssd[be[proxy]]] [sysdb_store_user] (0x0400): Error: 14 (Bad address)
[sssd[be[proxy]]] [save_user] (0x0040): Could not add user to cache
[sssd[be[proxy]]] [get_pw_name] (0x0040): proxy -> getpwnam_r failed for 'username' <14>: Bad address
[sssd[be[proxy]]] [acctinfo_callback] (0x0100): Request processed. Returned 3,14,Internal Error (Cannot make/remove an entry for the specified session)

The likely suspect is the ghost users conversion.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.0 RC2
rhbz: => 0

Fields changed

owner: somebody => okos
proposed_priority: => Undefined
status: new => assigned

fixed by 3a59cbd & 315f3be

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to okos
- Issue set to the milestone: SSSD 1.9.0 RC1

2 years ago

Login to comment on this ticket.

Metadata