Please enable JavaScript to view this site.

Version:

Navigation: Interface > CrossLink > Configure a CrossLink

CORS Configuration for Studio Web and FM Integration

Prev Top Next More

The Integration into VertiGIS Studio Web and VertiGIS FM may require some additional configuration regarding CORS policy.

For the integration of VertiGIS Studio Web into a configured target application, the call to the Integrator is made using an HTTP POST form (for details on the call, see the chapter VertiGIS Studio Web).

In VertiGIS Studio Web, there are two ways to pass this POST request: with or without credentials (the CORS policy of the Integrator configuration and the VertiGIS Studio Web Designer must match).

With Credentials

If it is necessary to pass credentials (NTLM authentication), as is required, for example, in a Terminal Server environment, then the permitted domain must also be defined in the response header. If this is not done, VertiGIS Studio Web will return an error.

The Access-Control-Allow-Origin header is defined through the CORS Policy entry in the configuration. The AccessControlAllowOrigin attribute specifies the permitted domains.

After changing this setting, the VertiGIS Roo Webserver service must be restarted.

<CORSPolicy>
<AccessControlAllowOrigin>https://apps.vertigisstudio.com/</AccessControlAllowOrigin>
</CORSPolicy>

Multiple domains can be configured within AccessControlAllowOrigin, separated by semicolons.

The NtlmAuthentication configuration is not required because the CORS policy prevents anonymous authentication. (If AllowAnonymous is configured as false, this setting is ignored.)

Without Credentials

If only a single user works on the computer where GeoOffice Integrator 2021 is installed, it is not necessary to pass credentials (NTLM authentication). In this case, the web server treats the request as an anonymous request.

As a result, it is also not necessary to define an Allowed Origin in the response header. The value * is automatically added to the Access-Control-Allow-Origin header, which means that all domains are permitted as allowed origins.

Therefore, the file roo.integrator.configuration.xml does not need a CORS policy entry. Instead, it requires a setting that allows anonymous access (default: anonymous access is not permitted).

After changing these settings, the VertiGIS Roo Webserver service must be restarted.

<!--
<CORSPolicy>
<AccessControlAllowOrigin>https://apps.vertigisstudio.com/</AccessControlAllowOrigin>
</CORSPolicy>
-->

<NtlmAuthentication>
<AllowAnonymous>true</AllowAnonymous>
</NtlmAuthentication>

© 2026 VertiGIS North America Ltd. All Rights Reserved. | Privacy Center | Imprint
Documentation Version 2.1 (bd9d54e2)