CODEWITHSUNDEEP
wcfconfigurationwcf-bindingtridion
Lucas
Lucas

Reputation: 337

How to configure Tridion core service on Tridion server?

When I access Tridion Core Service URL at: http://tridion_ip/webservices/CoreService2011.svc I get a Runtime error. I am accessing the URL directly from the CMS server.

Could not find a base address that matches scheme https for the endpoint

When I look in IIS, I can see that the /webservices/ directory shows the following Core Service files:

Should I see a web service page at that address? or is this expected beavior?

EDIT: Out security element reads as follows:

<wsHttpBinding>
 <binding name="CoreService_wsHttpBinding" transactionFlow="true" maxReceivedMessageSize="10485760">
  <readerQuotas maxStringContentLength="10485760" maxArrayLength="10485760" />

     <!--
      <security mode="Message">
    <message clientCredentialType="Windows" />
  </security>
     -->

  <!-- For LDAP authentication of message credentials, use the following settings: -->
  <security mode="TransportWithMessageCredential">
    <message clientCredentialType="UserName" />
  </security>

</binding>

Upvotes: 6

Views: 1591

Answers (2)

Andrey Marchuk
Andrey Marchuk

Reputation: 13483

Could you please post security part of your server config? The error you posted usually refers to mismatch between security mode and other security settings. Here's how default settings look like:

  <wsHttpBinding>
    <binding name="CoreService_wsHttpBinding" 
             transactionFlow="true" 
             maxReceivedMessageSize="10485760">
      <readerQuotas maxStringContentLength="10485760" 
                    maxArrayLength="10485760" />
      <security mode="Message">
        <message clientCredentialType="Windows" />
      </security>
    </binding>
  </wsHttpBinding>

Having TransportWithMessageCredential or Transport as security mode implies using HTTPS and will throw you exception like you have if access through HTTP

UPDATE That's indeed what I said. You have TransportWithMessageCredential that assumes you have HTTPs. If you plan to use HTTPs you should disable HTTP on your website but keep in mind that it will also require quite some configuration to make client work with HTTPs. You can always use Message security mode with HTTP. The part you have uncommented is only for LDAP with message security. You can perfectly use LDAP with transport security and use HTTP then.

Upvotes: 4

Shekhar Gigras
Shekhar Gigras

Reputation: 654

Check your webservice in IIS. This should be application and check your web.config where your service is installed.

may be you are facing multipile site hosting issue

put this line in webconfig, if it's already exists then replace with old line

<serviceHostingEnvironment aspNetCompatibilityEnabled="true" 
                           multipleSiteBindingsEnabled="true"/>

Upvotes: 5

Related Questions