Working on a non-secure server site - HxGN SDx - Update 64 - Administration & Configuration

Hexagon recommends using a secure HTTPS server. We do not recommended using a non-secure HTTP server. By default, new sites use a secure HTTPS server.

You can create a non-secure HTTP server site as follows:

1. In Server Manager > New Site Wizard set the Use HTTPS option to False.

2. In Smart API Manager > Settings, check the Require SSL option to Not Required.

After your sites are created, you must edit the HTTP server site's web.config file to get the Web Client to work.

• Locate the site web.config file, and replace the Smart API Manager (SAM) URL https entry with http. For example:

<intergraph.webApi>

<security>

<oauth issuer="http://swi-testsite01.ingrnet.com/sam/oauth" requiredscopes="ingr.api"

<cors allowedOrigins="http://swi-samsite01.ingrnet.com/sam" "allowedMethods="*" allowedHeaders="*" exposedHeaders="" allowCredentials="true" preflightMaxAge="600"/>

• You must perform an IISRESET in order for any changes to take effect.

• You can edit an existing site to use HTTP in Server Manager by setting the RequireHttps site setting to False in the server Site Settings Node properties, and update the web.config file as stated.

• You must add the HTTP site as the log on and log off Redirect URI in Smart API Manager.