2013-01-03 08:35 AM
It looks like I can't enable email notification for domain users. When I check the "notify on:" checkboxes on the Edit User dialogue, the Save button turns blue, but remains grayed out. Am I missing something or is this a bug? Oddly enough, it works just fine with local users.
Before and after screenshots below for your viewing pleasure
2013-01-03 09:23 AM
I see the same issue in my lab. Note that the username field is displayed with a red frame. My guess is that WFA tries to validate the input somehow and stumbles upon the \ character that separates domain and username. That's why it doesn't allow you to save it. Likely a bug.
2013-01-03 10:17 PM
Hello John and Hendrik,
The problem is the '\' character used in the username which is an invalid character for a username. You may try to login without providing the domain name and only use the username.
don't user MYDOM\user1 to login. instead only user : user1. You will be able to login successfully and enable the email notifications as well.
WFA is identifying 'MYDOM\user1' and 'user1' as separate users.
2013-01-04 12:35 AM
"WFA is identifying 'MYDOM\user1' and 'user1' as separate users."
This behavior makes your suggested workaround obsolete. The whole idea of using domain accounts is the fact to not maintain separate local users for WFA.
And I have to confirm this "bug". I'm unable to enable email notification on all my domain users - be it via "Users - Edit" for all users or "account Settings" of an individual user.
I highly recommend filing a BURT and get this fixed.
Kind regards, Niels
2013-01-04 12:56 AM
@ The whole idea of using domain accounts is the fact to not maintain separate local users for WFA.
My user 'user1' is not a local user. Its a domain user itself. I'm just saying not to provide the domain-name when trying to login. You'll be able to login and if you access the "users' page you'll see the column LDAP will be set to true for this user indicating its a Domain user and not a local user.
In the login page don't use: 'MYDOM\user1'. Just use 'user1' and provide password.
2013-01-04 01:09 AM
See the image below:
Both users (other than admin) are actually the same. When in the 2nd one I've provided 'Domain-name\username'. In the last one I've just used the username and still able to login. If you use this way, you won't face the problem mentioned in the original post.
There is a bug filed not to create users named in the 'Domian-Name\username way. '\' is an invalid character for a username in WFA.
2013-01-04 01:39 AM
what build are you using?
My WFA system:
If I omit the domain name, I get "The user name or password is incorrect". For me that indicates WFA cannot resolve an LDAP user in case you don't specify the domain.
2013-01-04 03:24 AM
I'm using a newer internal build but I believe that is not the problem. We tried to reproduce the problem and have found a case where it can happen. I think its in the User Logon user names you have created in your domain controller. You have created users with Logon names as: 'DOMAIN\user1' instead of only 'user1' . So looks like your username itself is 'DOMAIN\user1' instead of user1 and thats why when you are not providing DOMAIN\, its unable to find a username.
See below. Does your Logon usernames in your domain controller appear like this with 'DOMAIN\user'?
Create users in domain controller with Logon names like : 'user1' etc. and try.
If you create user Logon names like 'user1' then you'll be able to login to WFA server both as 'DOMAIN\user1' and only 'user1'.
2013-01-04 04:09 AM
I checked and all users are correctly configured.
Can you send me your LDAP settings of your WFA instance? I suspect the error may be buried there.
Could be the "Destinguished Name Attribute".
But I chose "distinguishedName" on purpose as it could easily be a single user name exists in two (or more) trusted domains and the LDAP server requires the domain attribute to resolve the user name to a single user.