Hi Team,
As part of mandatory best practices from our Windows team, we have to make the below settings to our Data Masking servers in Dev and then prod. Please review the settings and suggest if these can cause any impact to the FDM (Fast Data Masker) that we are using. Also, please help us understand if there is any tool/link where we can check such information in future? Thank you.
Execute: à In this server Default website(inetpub) and TDoDWeb site are in C drive please move it and map it in IIS manager to F: drive. Actual Value: 'VDIR "Default Web Site/" (physicalPath:%SystemDrive%\inetpub\wwwroot) VDIR "TDoDWeb/" (physicalPath:C:\Grid-Tools\TDoD\TDOD_WebUI)' ; Policy Value: 'physicalpath:(\%systemdrive\%|c:)'
Execute: à Change identity of application pool to Application pool identity instead of Network services
Execute: à Mode of Forms Authentication should be set to use cookies
5.2.1 Configure ?forms authentication? to set to use require SSL
Execute: à check the Require SSL checkbox in Forms authentication
Execute: à Change Anonymous user identity to use Application pool identity instead of any specific user id (default is IUSR)
Execute: à Disable this in registry with the script provided in the doc
Execute: à Enable this in registry with the script provided in the doc
Execute: à Disable this in registry with the script provided in the doc
Execute: à Deny TRACE verb in IIS manager
Execute: à Registry change with the script provided in the doc
TDM Portal 4.9.X
Component : CA Test Data Manager
NA
I am glad to say I was able to answer your question today on the WebEx.
Below is a recap of what we talked about today.
1) Fast Data Masker(FDM) and Test Data Maker do not use windows IIS out of the box.
2) The Test Data Maker Product does not expect or require IIS to be installed on its servers.
3) the changes you have provided are all for the Windows IIS web server.
4) if this Web server is installed and these changes are made this will not impact The TDM product.
5) Having the IIS web server installed MAY lead to a port conflict but this can be corrected with an simple configuration change either for IIS or the TDM produce.
As the questions for this case have been provided I will plan to close this case at COB on Wednesday should I not hear back from you on this issue.