We will make an alias for a public DNS name later that will resolve to the IP of the NAM LAG proxy).
#ACCESS MANAGEMENT CONSOLE XENAPP 6.5 WINDOWS#
I believe the setting is in the Web Interface Admin GUI and it's in the section: Manage Secure Client Access.Īssuming your NAM and CSG are in your DMZ you can put a line that basically says to use the gateway only if the IP network is say: .x (whatever your IP network for your DMZ is)Ĭitrix Web Interface DNS name: (this is the actual hostname of the Windows server.
One thing to note: We have our Web Interface server set to ONLY route through the CSG if it's been accessed externally (there's really no need to use the CSG if you're on your private LAN, IMO). NAM IDP/LAG-located in your DMZ and maybe also another cluster on your private LANįirst things first: Get it working all by itself (that way if you have problems you can blame Citrix).Citrix Secure Gateway (CSG) that's located in your DMZ on Windows 2003.Web Interface is set to use eDir authentication, not Windows auth. Citrix Web Interface server on IIS/Windows 2003-located on your private LAN.App servers have Novell Client installed on them, and are in AD domain that's synced via IDM 3.5.x from eDirectory so that userid/passwords match. Citrix Server farm that hosts your Applications via ICA-located on your private LAN.
#ACCESS MANAGEMENT CONSOLE XENAPP 6.5 CODE#
(there were some issues with Citrix web code that caused problems if you launched the web interface from a web browser via an HREF as it had java cross-site scripting issues). This document also assumes you are using the Citrix Web Interface v 4.6 with the latest patches from Citrix. This setup assumes you wish to perform SSO from NAM into the Citrix Web Interface, and that you do not wish to use the NAM SSL VPN to get access to the Citrix App servers. This is a first draft to give a basic information of how you can integrate Novell Access Manager (NAM) 3.x with Citrix XenApp (aka: Citrix).
0 kommentar(er)
