How to Configure Single Sign-on for Web Interface Using Version 10, 11, and 12x Plug-ins
Looking for:
Citrix receiver enable sso after installVirtualization - Configure Single Sign On (SSON) for Citrix Receiver
If the logging is not stopped this will increase disk utilization by log file. Also while debugging is enabled, expect an impact to performance. Receiver Logging - Authentication Manager Use the following settings to enable logging for authentication issues for example StoreFront, and so on. Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system.
Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it. Was this page helpful?
Our site does not support outdated browser or earlier versions. To use our site, please take one of the following actions:. Jump to content. Upvote if you also have this question or find it interesting. Learn more. Follow, to receive updates on this topic. Sign in to follow this Followers 0. By default, the DaaS is enabled in Workspace Configuration after you subscribe to the service.
However, the service requires that you deploy Citrix Cloud Connectors to allow Citrix Cloud to communicate with your on-premises environment. Deploy at least two Cloud Connectors to ensure high availability. The servers on which you install the Cloud Connector software must meet the following requirements:. If you already have the Resource Locations page loaded in your browser, refresh the page to display the registered FAS server.
A list of all FAS servers for all connected resource locations appears. To display FAS servers for a specific resource location, select the resource location from the drop-down list. Afterward, the Federated Authentication Service is active for all virtual app and desktop launches from Citrix Workspace. When subscribers sign in to their workspace and launch a virtual app or desktop in the same resource location as the FAS server, the app or desktop starts without prompting for credentials.
Subscribers are prompted for their AD credentials to access each application or desktop. The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation. The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
View PDF. This content has been machine translated dynamically. Give feedback here. Thank you for the feedback. Translation failed! The official version of this content is in English. Some of the Citrix documentation content is machine translated for your convenience only. This is not correct.
I forgot to mention that GPO are not needed in the case you create required registry keys manually. Very good article. Or in other words — to use http base url in Storefront? Thanks you for your article, very nice! Many thanks. Best Regards. Workspace app for HTML5 is a way to connect to resources without the need to install a client.
Does it work fine when connecting using Workspace app? I have seen this before and a reinstall of the VDA has resolved. I am able to pass through at first stage and gives me all app icons as expected.
Enumaration is perfect. But once I click on any app, it asks me to enter credentials server login prompt fires up. Could you advise what else I can check. This is really required for my project go live. Receiver for Client: Pass through works seamlessly on the same machine when accessing via Client similar to legacy PNAgent services site.
Can we do sso to netscaler gateway url from a domain joined machine using the logged in user credentials? I would like to do the same with netscaler gateway URL as Shen asked. Do you know the way to go? Notify me of follow-up comments by email. Notify me of new posts by email.
The SSO component is not required so a simple GUI or command line interface command can be used to install the client. Doing so partly reduces functionality: Non domain machines cannot authenticate to this Receiver for Web website Usrs can not log on using a set of credentials different than those they used to log on to their domain joined client device Keeping the above restrictions in mind, a decision must be made to bring true SSO experience at the expense of reduced authentication ability, or accept that a prompt will be given to users on first log on to Receiver for Web in favour of keeping maximum authentication abilities.
A command line install if preferred because you can automate Citrix Store configuration. The following command at minimum is required to install Receiver client: CitrixReceiver.
Comments
Post a Comment