Several Nodes were the session of the clients will be created.The NX Clients will be connected to the T.S, in this model you aren’t able to connect to the nodes directly (there are other ways of configuring NoMachine to allow this but not in cluster mode.).

Two terminal servers acting as a cluster (One Primary and one Secondary).

NoMachine Terminal Server (cluster and multinode environment)īasically your remote desktop client will be «NX CLIENT» that can be installed in both, Linux or Windows. In this document I leave the configuration of the product, administration commands and knowledge I’ve acquired in order to make it work. A month ago I was required to setup NoMachine (the paid version of FreeNX) also known as «!M or NX». For example the user profile may come from Active Directory with phone number sourced from another app and written back to Active Directory.There are some products as x2go and FreeNX (which isn’t longer available) that were designed to provide Remote Desktops to users. When the application is used as a profile master it is possible to define specific attributes to be sourced from another location and written back to the app. Allows Okta to use custom attributes you have configured in the application that were not included in the basic app schema. Import the user attribute schema from the application and reflect it in the Okta app user profile. Simplifies onboarding an app for Okta provisioning where the app already has groups configured. Link Okta groups to existing groups in the application. Groups can then be managed in Okta and changes are reflected in the application. Push existing Okta groups and their memberships to the application. This feature is not required for all federated applications as user authentication takes place in Okta, however some apps still require a password. Push either the users Okta password or a randomly generated password to the app. The application can be defined as the source of truth for a full user profile or as the source of truth for specific attributes on a user profile. Accounts can be reactivated if the app is reassigned to a user in Okta. Future attribute changes made to the Okta user profile will automatically overwrite the corresponding attribute value in the app.ĭeactivates a user's account in the app when it is unassigned in Okta or their Okta account is deactivated.

Okta updates a user's attributes in the app when the app is assigned. Creates or links a user in the application when assigning the app to a user in Okta.

Nomachine server authorization