You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Windows Authentication:

To enable Windows Authentication in your project, please go to Info>Project>Redundancy and select the checkbox “Windows Authentication”.

 

When using Windows Authentication, project user management is disabled and is controlled by Windows. The Windows user that is logged into the computer will be the one used by the project. 

When you are using client instances, the server computer is the one that will validate the user for the client. Also, the Windows user that is logged into the client computer needs to exist on the server computer and be in the same domain group.

After the user validation, the user’s Windows group will determine which project Security Permission will be used. It will search in the project Security Permission for the same Windows Group name. If it finds the exact same name, the Security Permission will be used in the project for the logged in User. If any names match, the Permission Guest will be used.

It is important to verify which port is being used in the project for the Windows Authentication. By default, clients will use the 3102 port. However, this can be changed in the command line or URL when starting a client display. 

Example of the TSmarClient URL using Windows Authentication:

http://127.0.0.1/fs-2016.2/TSmartClient.application?port1=3102&wa=true



LDAP Server

To enable the LDAP Server in FactoryStudio, please go to Info>Project>Settings. Then, type the LDAP server's name in the AD/LDAP Server field.

For the integration of the LDAP Server, any extra customization in the project is needed except for the LDAP Server name in the Info>Project>Settings.

The project Client.LogOn() method in the LOGON page will work properly after enabling the LDAP Server.

When this method is called, it will check the project for an Engineering user. If none are found, it will check for a runtime user. If no runtime users are found, it will check for a LDAP user if the LDAP Server is configured. The first user that is found and validated will be the user that is logged into the project. 

After the user validation, the user’s Windows group will determine which project Security Permission will be used. It will search in the project Security Permission for the same Windows Group name. If it finds the exact same name, the Security Permission will be used in the project for the logged in User. If any names match, the guest permission will be used.

  • No labels