Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This guide describes how to exercise sms permissionsset up the anonymous access to the VvtProcessSMSService. Set up can be performed by the system administrator. If you are using the cloud version, please contact the Creatio support team to complete the set up.

Follow the steps to set up anonymous access to the VvtProcessSMSService:

  1. Create a file ‘VvtProcessSMSService.svc’ in the ..\Terrasoft.WebApp\ServiceModel folder and add the following string to the file:

<% @ServiceHost Service = "Terrasoft.Configuration.VvtProcessSMSServiceNamespace.VvtProcessSMSService" Debug = "true" Language = "C#" %>

2. Add the following record to the <services> section in ..\Terrasoft.WebApp\ServiceModel\http\services.config and ..\Terrasoft.WebApp\ServiceModel\https\services.config files:

<services>

...

    <service name="Terrasoft.Configuration.VvtProcessSMSServiceNamespace.VvtProcessSMSService">

        <endpoint name="VvtProcessSMSServiceEndPoint"

            address=""

            binding="webHttpBinding"

            behaviorConfiguration="RestServiceBehavior"

            bindingNamespace="http://Terrasoft.WebApp.ServiceModel"

            contract="Terrasoft.Configuration.VvtProcessSMSServiceNamespace.VvtProcessSMSService" />

    </service>

</services>

3. Add the <location> element to the <configuration> section in ..\Terrasoft.WebApp\Web.config file:

<configuration>

    ...

    <location path="ServiceModel/VvtProcessSMSService.svc">

        <system.web>

            <authorization>

                <allow users="*" />

            </authorization>

        </system.web>

    </location>

    ...

</configuration>

 4. Add the <key> element to the ..\Terrasoft.WebApp\Web.config file in the <appSettings> section:

<configuration>

    ...

    <appSettings>

        ...

        <add key="AllowedLocations" value="[previous values];ServiceModel/VvtProcessSMSService.svc" />

        ...

    </appSettings>

    ...

</configuration>

 5. Reload application in IIS.