cancel
Showing results for 
Search instead for 
Did you mean: 

HTML5 SSO

SOLVED
pfrey@lafim.de
Occasional Contributor

HTML5 SSO

Hi guys,

does anybody know how to configure HTML5 RDP Ressource Profiles with SSO?

When our users login with their azure ad credentials ([email protected]) the HTML5 profiles don't connect to the RDP Server. I tried the user variables <USER> and ourdomain\<USER> for the Bookmark but it won't connect.

If the user creates a custom connection with ourdomain\<USER> variable it works. But not with deployed profiles.

we are on 9.1R14

thanks.

1 ACCEPTED SOLUTION

Accepted Solutions
rdumitrescu
Contributor

Re: HTML5 SSO

You said that you are using Azure AD as auth. server.

The implementation is done using SAML? If SAML is used the PCS is not holding any info about the user password, and so the SSO cannot work. The only way is to enter to the bookmark a static password, but that is not a SSO setup.

View solution in original post

5 REPLIES 5
pfrey@lafim.de
Occasional Contributor

Re: HTML5 SSO

just figured something out. when I use "ourdomain\<username>" for username in the bookmark and a static password it works. as soon as I use <PASSWORD> as a variable vor Password it doesn't. so looks like the password variable is the problem.

pfrey@lafim.de
Occasional Contributor

Re: HTML5 SSO

could the problem just be that the password variable does not work with azure ad auth server? I could imagine that azure is not allowing pulse to read the password for security reasons.

rdumitrescu
Contributor

Re: HTML5 SSO

You said that you are using Azure AD as auth. server.

The implementation is done using SAML? If SAML is used the PCS is not holding any info about the user password, and so the SSO cannot work. The only way is to enter to the bookmark a static password, but that is not a SSO setup.

zanyterp
Moderator

Re: HTML5 SSO

how are you connecting to azure? as mentioned by @rdumitrescu, if you are using SAML, there is no password available for the SSO. you will need to add a secondary auth server that is into the PCS directly that allows the appliance to store the password. your policy would then be defined as DOMAIN\<username> and <PASSWORD[2]>
pfrey@lafim.de
Occasional Contributor

Re: HTML5 SSO

While this works, there is no real advantage for us. In this scenario the user has du type in the password twice while login in pcs as supposed to 1 time during login and another time for the html5 rdp session.

But the concept ist cool. Thanks.