Authentication: Support UserPortal Logins with "username@domain.com"
Allow users to login to the User Portal with username@domain.com when joined to an Active Directory Domain
Currently the users must login with their AD username only, using their email address does not work.
Dan
shared this idea
10 comments
-
Alpay Akyol
commented
do you know that does cyberoam can do same thing ?
we have big issue about long usernames (name.surname) , so that we have to cut them or use alternative ones which makes non standard solutions.
if we could use user@domain.x it would be better. -
Martin Damgaard
commented
Hello D:
Your solution does indeed work for the single purpose of giving access to the user portal.
But there is other issues and thing that can not be integrated this way. So it is still not a one-stop solution. -
D
commented
you can mark this as fixed;
http://www.360ict.nl/blog/enabling-upn-userdomain-com-in-sophos-utm/It would be nice though if we could have multiple authentication options and fallback. So use UPN and if that fails, try username authentication.
-
tjbbe
commented
Let me choose which attribute to use to find a user. Defaults to samaccount, but not limited to upn,email or other. A federative solution would delegate the choosen attribute to the federate portal.(even better)
-
Dennis
commented
So, i found what was wrong. I tested with the test button on the authentication server tab and that test button does not seem to work like expected (i logged it with sophos support). It is working now, i blogged the whole story here;
http://www.360ict.nl/blog/enabling-upn-userdomain-com-in-sophos-utm/ -
Dennis
commented
We have a big implementation for RemoteAccess VPN logins, for ~850 users and this would greatly increase the usability and ease of use for the end users. I also created a Forum post to see if there are workarounds;
http://www.astaro.org/gateway-products/general-discussion/45394-remoteaccess-ad-upn-login.html#post220987 -
Mads Poulsen
commented
I see this as a problem, when running mail security for several seperate AD domains, and one AD domain contains username "John", and "John" is also a user at another AD domain.
"John" in the domain highest in the Auth. servers list, logs in fine. He's happy. untill...
The scary thing is that if "john" in the lower listed server enter his username and password, he gets logged in to the other "john" 's user portal and can access the quarantine, smtp log, etc etc..!!!! :( :( No!, Baaad spamfilter.. 1 hour in the shame box. :)
-
Just to clarify this feature so users can allocate their points correctly. You can currently login to the userportal against AD auth, using "username". I reworded the feature to indicate what the submitter has asked for, which is username@domain.com support for the login name.
-
dan.ballwegGmail
commented
no. It will not work if you type the @domain. It will only work if you only type the username.
-
Bob Alfson
commented
Dan, isn't this how it works now?
