Solution: Error accessing Schema Generator over HTTPS in 15.4

  • 30 March 2023
  • 0 replies
  • 25 views

Userlevel 7
Badge +10

A customer recently reported an XML/JSON error while trying to access the Schema Generator and Export Template Wizard modules in the web browser version of Alliance (15.4).  After investigating the issue, it was determined that the HTTPS binding was missing from the Web_WCFServices_SSL.config.  This issue will be resolved in 15.4 SU5.

Screenshot of issue:

In the meantime, this issue can be resolved by adding the binding to Bin\Web_WCFServices_SSL.config:

  <service name="Astea.EO.SchemaGenerator.SchemaGeneratorService" behaviorConfiguration="CustomServiceBehavior">
<endpoint address="dotnetssl" binding="basicHttpBinding" bindingConfiguration="SSL" name="simpleSSL" contract="Astea.AO.Interfaces.Contracts.ISchemaGeneratorService" />
<endpoint address="dotnet" binding="basicHttpBinding" bindingConfiguration="NoSSL" name="simple" contract="Astea.AO.Interfaces.Contracts.ISchemaGeneratorService" />
<endpoint address="" binding="webHttpBinding" bindingConfiguration="" name="web" contract="Astea.AO.Interfaces.Contracts.ISchemaGeneratorService" />
<endpoint address="" binding="webHttpBinding" bindingConfiguration="webSSL" name="webSSL" contract="Astea.AO.Interfaces.Contracts.ISchemaGeneratorService" />
<endpoint address="mex" binding="mexHttpBinding" bindingConfiguration="" name="mex" contract="IMetadataExchange" />
</service>

Added entry: 

    <endpoint address="" binding="webHttpBinding" bindingConfiguration="webSSL" name="webSSL" contract="Astea.AO.Interfaces.Contracts.ISchemaGeneratorService" />

After the change is made, an IIS reset is required.


0 replies

Be the first to reply!

Reply