Post-onboarding tasks

Configure applications

Your next immediate task is to publish your first application. It is recommended that you test your setup by publishing at least one internal web application or one TCP/UDP application. Follow the detailed instructions in the Apps Configuration and Management.

Configure access policies

  • In the Secure Private Access admin console, navigate to Policies > Access Policies.

  • Create an access policy for your application, making sure to define the User conditions.

  • See the Access policies configuration and management for complete details.

Synchronize the configuration

After saving the changes (new applications or policies), the Secure Private Access component inside your on-premises Cloud Connectors must synchronize this new configuration from Citrix Cloud.

This process typically takes up to 10 minutes to complete.

How to verify: It is recommended to check if the new configuration has been applied by using the Policy Modeling tool (under Policies > Policy Modeling) to see if your new policies are active.

Access your applications (end users)

This section captures information about how end users access published applications on their devices.

Supported Devices:

  • Web/SaaS applications (via Google Chrome managed profile) are accessible from any desktop OS.

    On Linux, iOS, and Android devices, Web/SaaS applications are accessible via the Citrix Secure Access client.

  • TCP/UDP applications (via the Citrix Secure Access client) are supported on Windows, macOS, Linux, iOS, and Android.

Accessing Web and SaaS applications

There are three primary ways for users to access their web applications on desktop devices. All these methods will automatically launch the app in the Google Chrome managed profile.

This is the most seamless experience for the user.

  1. Launch the Google Chrome browser.

  2. If this is your first time, add a new browser profile using the corporate email address that is configured on the access policy. This creates a managed profile.

  3. In the managed profile, navigate to your NetScaler Gateway URL (the one configured for StoreFront in Step 2).

  4. Log in to your store.

  5. Click a Web or SaaS application icon to launch it.

The app launches in a new tab in the managed profile.

Method B: Using a non-managed web browser

Note:

This method requires a supported version of the Citrix Workspace app to be installed on the desktop device.

  1. Launch any browser of your preference (for example, non-managed Chrome, Edge, Firefox).

  2. Navigate to your NetScaler Gateway URL (the one configured for StoreFront in Step 2).

  3. Log in to your store.

  4. Click a Web or SaaS application icon to launch it.

  5. The browser displays a dialogue prompting you to open the Citrix Workspace App.

  6. Click Continue or Open.

  7. Citrix Workspace app takes over and launches the application in the Google Chrome managed profile. If a profile is not already created, a setup screen with your email address pre-populated appears for you to complete the profile.

Method C: Using Citrix Workspace app

  1. Launch the Citrix Workspace App on your device.

  2. If not already configured, add your store using the NetScaler Gateway URL (the one configured for StoreFront in Step 2).

  3. Log in to your store.

  4. You can see your list of enumerated applications.

  5. Click a Web or SaaS application icon to launch it. The application automatically opens in the managed Google Chrome profile.

Accessing TCP/UDP (client/server) applications

Accessing TCP/UDP applications requires the Citrix Secure Access client.

You must install Citrix Secure Access with the supported version on the endpoint device.

Connect the Secure Access Client

  1. Launch the Citrix Secure Access client.

  2. When prompted for a URL, enter the Secure Private Access Gateway URL (the FQDN configured in Step 2).

  3. Complete the login and authentication prompts.

  4. The client connects and then runs securely in the background.

Launch your published applications

You can now use your native client software directly if allowed by Secure Private Access policies. For example:

  • Open Microsoft Remote Desktop and connect to the internal host name of your RDP server.

  • Open an SSH client and connect to the internal IP of your Linux server.

Post-onboarding tasks