Customize QMS to run within an iFrame (Optional)

By default, QMS is disabled from running within an iframe because it is a common security complaint. However the QMS client can be configured to run inside an iframe if required. In order to do so, complete the following steps:

For QMS versions 12.0 or newer:

The QMS client must be configured to run under SSL, otherwise Chromium based browsers will not accept cross-site cookies from the QMS client when running inside an iframe. See SSL Configuration for details on how to configure the client for SSL.
Open the appSettings.json file for editing (found in the QMS Client IIS directory, which is normally C:\Inetpub\wwwroot\QMS\appSettings.json).
Find the "CookieSettings" node and change the requireSSL attribute to true and sameSite to None e.g.
```
"CookieSettings": {
"httpOnly": "true",
"requireSSL": "true",
"sameSite": "None"
}
```
Find the Content-Security-Policy node and set the directive to name trusted frame ancestors 'self' and other trusted origin(s). e.g.
```
"ContentSecurityPolicy": "frame-ancestors 'self' https://ancestorhost:5500"
```

For QMS versions older than 12.0:

The QMS client must be configured to run under SSL, otherwise Chromium based browsers will not accept cross-site cookies from the QMS client when running inside an iframe. See SSL Configuration for details on how to configure the client for SSL.
Open the web.config file for editing (found in the QMS Client IIS directory, which is normally C:\Inetpub\wwwroot\QMS\Web.Config)
Find the httpCookies node and change the requireSSL attribute to true and sameSite to None. e.g.
```
<httpCookies httpOnlyCookies="true" requireSSL="true" sameSite="None" />
```
Find the cookieHandler node and change the requireSSL attribute to true. e.g.
```
<cookieHandler requireSsl="true" name="QMSAuth" hideFromScript="true" />
```
Find the Content-Security-Policy node and set the value to empty. e.g.
```
<add name="Content-Security-Policy" value="" />
```