How to properly prepare an instance of a Citrix ICA client object to successfully connect to a farm with Citrix Access Gateway?

Question

I use the Citrix ICA client client API to programmatically connect to published applications. As a rule, this is as simple as subscribing to several events, submitting an object with an ICA file (via the LoadIcaFile method) and calling the Connect method.

However, if ICA clients are 12.1 or higher, this approach will immediately disable the event if CAG is used and the ICA file address field contains a critical token instead of the server IP address. The same approach works fine with an older client (10.x), or if the ICA file contains the address of the direct server (which, I believe, means that the CAG is not used)

If someone has managed to start software sessions in Citrix Access Gateway environments that successfully work with the ICA client 12.1 or higher, share how this was done.

NOTE. My understanding of the Citrix server side is very limited, from practice - I believe that I have encountered ICA files containing a critical address field coming from the web interface to farms using any of the following: citrix access gateway, citrix secure gateway, citrix NetScaler

Answer 1

it is unlikely to have any other solutions, so I consider my last comment as the answer:

ICA Client 13.1 connects just fine (for example, client 10.200)

Thus, problems with software connections with CAG are probably flaws (defects?) Of specific client versions, therefore, specific preparation of the ICA client object for working in the CAG environment is not required.