We have an SP initiated SSO setup for our product which combines Shibboleth SP3 and PingFed IDP. Everything works fine. We are using Shibboleth v3.0.2. Now there is a change in requirement, we need to a show massage to User before redirecting to IPD login page and after successful authentication before redirecting to originating product URL. 
As per Shibboleth SP3 documentation at <a href="https://wiki.shibboleth.net/confluence/display/SP3/ConfigurationFileSummary" target="_top" rel="nofollow" link="external">https://wiki.shibboleth.net/confluence/display/SP3/ConfigurationFileSummary</a>. It seems that customizing <b>bindingTemplate.html</b> and <b>postTemplate.html</b> can solve my problem. However, it needed to change SAML artifact binding to use <b>POST</b> rather than a <b>redirect</b>. As per documentation found at <a href="https://wiki.shibboleth.net/confluence/display/SP3/SSO" target="_top" rel="nofollow" link="external">https://wiki.shibboleth.net/confluence/display/SP3/SSO</a>, <b>postArtifact="true"</b> can change the behaviour. However, doing these changes in shibboleth2.xml, there is no change in behaviour. Still, SP is doing a redirect to IDP and bindingTemplate.html & postTemplate.html not coming in picture. This is my shibboleth2.xml-
<pre>
<SPConfig xmlns="urn:mace:shibboleth:3.0:native:sp:config"
    xmlns:conf="urn:mace:shibboleth:3.0:native:sp:config"
        clockSkew="180">
    <OutOfProcess tranLogFormat="%u|%s|%IDP|%i|%ac|%t|%attr|%n|%b|%E|%S|%SS|%L|%UA|%a" />
    <ApplicationDefaults entityID="PLM-QA-TYPE"
        REMOTE_USER="uid eppn subject-id pairwise-id persistent-id"
        cipherSuites="DEFAULT:!EXP:!LOW:!aNULL:!eNULL:!DES:!IDEA:!SEED:!RC4:!3DES:!kRSA:!SSLv2:!SSLv3:!TLSv1:!TLSv1.1">
        <Sessions lifetime="28800" timeout="3600" relayState="ss:mem"
                  checkAddress="false" handlerSSL="false" cookieProps="http" postTemplate="postTemplate.html">
                        <SSO entityID="https://entityid.com" postArtifact="true" template="bindingTemplate.html"   
                 discoveryProtocol="SAMLDS" discoveryURL="https://ds.example.org/DS/WAYF" > 
              SAML2
            </SSO> 
            <Logout>SAML2 Local</Logout>
            <LogoutInitiator type="Admin" Location="/Logout/Admin" acl="127.0.0.1 ::1" />
            <Handler type="MetadataGenerator" Location="/Metadata" signing="false"/>
            <Handler type="Status" Location="/Status" acl="127.0.0.1 ::1"/>
            <Handler type="Session" Location="/Session" showAttributeValues="false"/>
            <Handler type="DiscoveryFeed" Location="/DiscoFeed"/>
        </Sessions>
        <Errors supportContact="root@localhost"
            helpLocation="/about.html"
            styleSheet="/shibboleth-sp/main.css"/>
                <MetadataProvider type="XML" validate="true" path="idp-metadata.xml"/>
        <AttributeExtractor type="XML" validate="true" reloadChanges="false" path="attribute-map.xml"/>
        <AttributeFilter type="XML" validate="true" path="attribute-policy.xml"/>
        <CredentialResolver type="File" use="signing"
            key="sp-signing-key.pem" certificate="sp-signing-cert.pem"/>
        <CredentialResolver type="File" use="encryption"
            key="sp-encrypt-key.pem" certificate="sp-encrypt-cert.pem"/>
    </ApplicationDefaults>
    <SecurityPolicyProvider type="XML" validate="true" path="security-policy.xml"/>
    <ProtocolProvider type="XML" validate="true" reloadChanges="false" path="protocols.xml"/>
</SPConfig>
</pre>
Here, I added <b>postTemplate="postTemplate.html"</b> and <b>postArtifact="true" template="bindingTemplate.html"</b> over existing configuration.

Can someone help me to identify, what wrong I am doing?

Thanks in advance.

        
        
        
<br/><hr align="left" width="300" />
Sent from the <a href="https://shibboleth.1660669.n2.nabble.com/Shibboleth-Users-f1660767.html">Shibboleth - Users mailing list archive</a> at Nabble.com.<br/>