More in this section
Forums / Bugs & Issues / Backend URL redirect not working after Sitefinity Upgrade

Backend URL redirect not working after Sitefinity Upgrade

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
1 posts, 0 answered
  1. Chaitanya
    Chaitanya avatar
    22 posts
    Registered:
    14 Oct 2013
    11 Sep 2017
    Link to this post

    Hello,

    We have a load balanced environment.(Without Sitefinity Load Balancing Module, using Azure Load Balancer) We have two web servers (say a.azure.com and b.azure.com) and a production URL(say www.xyz.com). When we hit the backend URL, it used to redirect to another host name(say admin.xyz.com). 

    We upgraded our site to Sitefinity 10.1(Previously it was was Sitefinity 8.2) and backend URL redirect stopped working. All the URLs are working on its own, just redirect is not working.

    Only place where admin URL is mentioned in the configuration are web.config and securityConfig.config. securityConfig.config is as it is without change after upgrade(Except version details). Though there is change in web.config entry due to changes in security implementation in Sitefinity 10. Changes are as below. Can anyone suggest how to have redirect for backend again?

    Old:

    <system.identityModel>
      <identityConfiguration>
        <securityTokenHandlers>
          <add type="Telerik.Sitefinity.Security.Claims.SWT.SWTSecurityTokenHandler, Telerik.Sitefinity" />
        </securityTokenHandlers>
        <audienceUris mode="Never" />
        <issuerNameRegistry type="Telerik.Sitefinity.Security.Claims.CustomIssuerNameRegistry, Telerik.Sitefinity">
          <trustedIssuers />
        </issuerNameRegistry>
        <issuerTokenResolver type="Telerik.Sitefinity.Security.Claims.SWT.WrapIssuerTokenResolver, Telerik.Sitefinity" />
        <certificateValidation certificateValidationMode="None" />
      </identityConfiguration>
    </system.identityModel>
    <system.identityModel.services>
      <federationConfiguration>
        <wsFederation passiveRedirectEnabled="true" issuer="http://localhost" realm="https://admin.xyz.com" requireHttps="true" />
        <cookieHandler requireSsl="false" />
      </federationConfiguration>
    </system.identityModel.services>

     

    New:

    <microsoft.identityModel>
      <service>
        <claimsAuthenticationManager type="Telerik.Sitefinity.Security.Claims.SFClaimsAuthenticationManager, Telerik.Sitefinity" />
        <securityTokenHandlers>
          <add type="Telerik.Sitefinity.Security.Claims.SWT.SWTSecurityTokenHandler, Telerik.Sitefinity" />
        </securityTokenHandlers>
        <audienceUris mode="Never" />
        <federatedAuthentication>
          <wsFederation passiveRedirectEnabled="true" issuer="http://localhost" realm="https://admin.xyz.com" requireHttps="true" />
          <cookieHandler requireSsl="false" />
        </federatedAuthentication>
        <issuerNameRegistry type="Telerik.Sitefinity.Security.Claims.CustomIssuerNameRegistry, Telerik.Sitefinity">
          <trustedIssuers />
        </issuerNameRegistry>
        <issuerTokenResolver type="Telerik.Sitefinity.Security.Claims.SWT.WrapIssuerTokenResolver, Telerik.Sitefinity" />
      </service>
    </microsoft.identityModel>
1 posts, 0 answered