Things I recommend to go through after the deployment process, BEFORE using Adaptive Authentication in a productive environment: I will not go through all provisioning and basic configuration steps, as this is well documented in Citrix Product documentation and you’re getting a step by step wizard during the provisioning process, where all the things are well explained.įollowing, just a few notes during the setup.
#Citrix redirector windows
You can go by Citrix Cloud Connector (Only Windows based is supported, Connector appliance is not supported atm) or Azure VNet peering.
A public SSL certificate which matches your chosen adaptive auth redirect FQDN.Citrix is recommending to access the HA instance-consoles using FQDN, so you have to create another two DNS records, for example and where you have to bind certificates on each instance.During the setup wizard, Citrix Cloud is creating a public IP, where you have to create the DNS records for.A public domain which is owned by you or a customer and where you are able to create public DNS records.
#Citrix redirector plus
Active Subscription to DaaS Premium / DaaS Premium Plus or SPA Advanced.If you want to start with Adaptive Authentication, make sure the following requirements are present: Let’s reveal some insights about the technical configuration (and limits 🙂 ) and some cost perspectives.
The authentication flow is working with http 302 redirect to the hosted ADC, after the authentication is successful, the user get back to the Cloud Workspace URL. It’s not possible to setup the service for productive usage without any practical ADC know-how. Adaptive Authentication ADC restricted advanced Licenseįirst of all, configuring Adaptive Authentication is definitely easier if you’re having experiences and worked with ADC features before.
0 kommentar(er)
