I'm trying to use Windows Azure Active Directory as a security store, but SSO scenario doesn't work for me, because I need to sign users in through our website, not through a WAAD sign-in page. SSO could work if, at least, a user name didn't need to be input in this horrible UserName@CompanyName.onmicrosoft.com format. Making users type this many characters for their user name during the login makes the whole application look unprofessional, to say the least. If there's a workaround for a user name issue, I would love to hear it, because I didn't find it anywhere.
I tried to work around WAAD SSO by checking the username and password entered in our login page against those of User object returned by Graph API (Now, I know it's an ugly implementation. So, please, feel free to suggest something better than that.). Graph API returns the correct user, but it's passwordProfile property is Null. So, the above workaround flies right out the window. I've seen the same question at http://stackoverflow.com/questions/16785231/azure-graph-api-password-attribute-of-user-object-is-always-null with no definitive answer. Any ideas on what's going here?