Description of problem:

When setting useFullyQualifiedNames to TRUE in a domain configuration, you should be able to use the fully qualified names when modifying or deleting users and groups.  One could argue that you should have to use fully qualified names.  Specifically because there could be the same userid or group name that exists in two different domains.

User and group addition, modifications and deletions do not work using fully qualified names.  

If you add a user using @LOCAL:
    sss_useradd -u 1000 -h /home/user1000 -s /bin/bash user1000@LOCAL
You end up with:
    user1000@LOCAL@LOCAL:x:1000:1000:user1000@LOCAL:/home/user1000:/bin/bash

If you add a user with @LOCAL
   sss_useradd -u 1000 -h /home/user1000 -s /bin/bash user1000

Subsequent modification and/or deletions usign fully qualified names fail.
   
Version-Release number of selected component (if applicable):
sssd-debuginfo-0.4.1-1.fc11.i586
sssd-0.4.1-1.fc11.i586

How reproducible:
always

Steps to Reproduce:
1. 
2.
3.
  
Actual results:


Expected results:


Additional info:

sssd.conf tested:

[services]
description =  Local Service Configuration
activeServices = nss, pam
reconnection_retries = 3

[services/nss]
description = NSS Responder Configuration
filterGroups = root
filterUsers = root
debug-level = 4

[services/dp]
description = Data Provider Configuration
debug-level = 4

[services/pam]
description = PAM Responder Configuration

[services/monitor]
description = Service Monitor Configuration

[domains]
description = Domains served by SSSD
domains = LOCAL

[domains/LOCAL]
description = LOCAL Users domain
enumerate = 3
minId = 1000
maxId = 1010
legacy = FALSE
magicPrivateGroups = TRUE
useFullyQualifiedNames = TRUE
provider = local