Authentication is done by the application or IIS web server at the wrapper layer (endpoints) to get access to the Corticon Endpoint(s). Once you have been granted permission into the Corticon Endpoint, the endpoint calls into Corticon Server to execute a Decision Service.

If you want to enable HTTPS communications, your Corticon Studio clients must also be configured to allow secure HTTPS communications with the Corticon Server .NET. Enabling the Corticon Studio to publish to a secure Corticon Server .NET, Corticon Studio supports Transport Layer Security (TLS)-enabled communications to a Corticon Server. To enable TLS communication between the Server and the Client, you must obtain and install public key certificates for the Corticon Studio. The public certificate then needs to be imported to the Java keystore for the Corticon Studio. The typical technique for doing that is to first create a keystore by running the following command from a command prompt: 
keytool.exe -genkey -keystore my.keystore -storepass myPwd
Then, from the command prompt, run the following command to import the certificate: 
keytool.exe  -import -alias [server] -file [server].der -keystore my.keystore -storepass myPwd
Launch the Eclipse client from a command prompt using the following command: 
eclipse -vmargs -Djavax.net.ssl.trustStore="drive:\path\to\certificate\my.keystore" -Djavax.net.ssl.trustStorePassword=myPwd
Corticon Server .NET exposes several REST endpoints that can be leveraged to perform certain administrative tasks, execute a decision service, or perform batch processing.