I have a RDWeb environment that I'm deploying to clients. In this scenario I don't need them to input the domain every time.
So I made the adjustment to
var strDomainName = <mydomain>;
Users are able to login to the portal just fine using just their username and password, but now SSO is broken. It does not pass the credentials on to the RDP and I'm prompted to login with full credentials.
I have seen the other post that recommend trying this.
The solution we employed was to tweak the underlying web files to better handle the domain. We only have one domain so this was fixed, what I did was edit the renderscripts.js file (which includes the JS procedure which occurs after the login dialog 'submit') to check to see if the user has entered a domain (checking whether a backslash exists) and if not physically edit the edit box contents with the new domain. In the renderscripts.js file look for the function onLoginFormSubmit(), where it probes the username edit box simply insert the domain. The code extract below includes a peice from the original file which shows you where it should be placed together with the new code (separated by blank lines). In this instance the domain is called CHARLYMONKEY. if ( objForm != null ) { strDomainUserName = objForm.elements("DomainUserName").value; // add default domain... if ( strDomainUserName.indexOf("\\") == -1 ) { strDomainUserName = "CHARLYMONKEY\\" + strDomainUserName; objForm.elements("DomainUserName").value = strDomainUserName; } strPassword = objForm.elements("UserPass").value; strWorkspaceId = objForm.elements("WorkSpaceID").value; It is messier that an RDP setting but we had to edit the web access site anyway for corporate branding, this was simply the next level. I hope that is of help, obviously if anything goes wrong with the login the modified value of the edit is written back to the edit box (this is essential) so the user can see if somehow they've entered the domain or something but with the wrong kind of slash. Please note that if you also tweak your main screen to check for RDC 7.0 and if not force users to download and install it the single sign-on works fantastically. I haven't done this yet but am hoping the RDC ActiveX control can be probed by JavaScript so that proper version checking can take place. kind regards, Ross
But in the end this did not work. Still prompts me to login.
Any thoughts?
Thanks