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

Compare with Current View Page History

« Previous Version 2 Next »

Windows Authentication:

To enable Windows Authentication in the project, please go to… Info>Project>Redundancy, and enable the check box “Windows Authentication”.

When using Windows Authentication the project User management is disabled, and this management is controlled by Windows. The Windows User that is logged in the computer will be the one used in the system.

When you are using Client instances, the Server computer is the one will validate the User for the Client. Then, the logged Windows User in 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 found exactly the same name then the Security Permission will be used in the project for the logged User. If any names match, the Permission Guest will be used.

It is important verify the port that is being used in the project for the Windows Authentication. The Clients will use by default the 3102 port. However this can be changed in the command line or URL when starting the Clients.

Example of  TSmarClient URL using Windows Authentication:

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


LDAP Server

To enable LDAP Server in FactoryStudio, please go to… Info>Project>Settings, and type the LDAP Server 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.

After enabling the LDAP Server the project Client.LogOn() method in LOGON page will work property. This method when called, firstly it checks for the project Engineering Users if not found , then it checks the project Runtime Users and  finally if there is a LDAP Server configured it checks for the LDAP Users. When the first User is found and validated the found User will be logged in the project.

As in the Windows Authentication, after the user validation, the user’s Windows group will determine which project Permission will be used. It will search in the project Security Permission for the same Windows Group name. If it found exactly the same name then the Security Permission will be used in the project for the logged User. If any names match, the Permission Guest will be used.

  • No labels