Verified that the user resolution using both name and name@domain works in 220.127.116.11
I user the username and it correctly found out the user in AD. The created user in the Access Control has name@domain in there. Then I tried it again with the name@domain and it worked too.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.