I suspect a caching issue here. Was this a single node setup or a multi node cluster?
Also when you try out next time. Can you simply view the SP config and click the update button (without ticking and unticking) and see it it works? On Friday, October 20, 2017, Chamara Ariyarathne <[email protected]> wrote: > Hi all, > > I'm using the IdentitySAMLSSOConfigService admin service to do the SAML2 > Web SSO Configuration and later using IdentityApplicationManagementService > admin service to add it to a service provider configuration. > > I am using this tag to Enable Response Signing. > <xsd1:doSignResponse>true</xsd1:doSignResponse> > > However when later checked with the travelocity webapp and the log > in fails. When I checked the SP configuration, I can see the checkbox is > ticked for Enable Response Signing in the UI. > > If I untick and tick again the checkbox and update the SP, then the > scenario passes. What that means is, the admin service cannot be used to > make the Enable Response Signing. > > This needs a fix. > > https://wso2.org/jira/browse/IDENTITY-6796 > > -- > *Chamara Ariyarathne* > WSO2 Inc; http://www.wso2.com/ > Mobile; *+94772786766* > -- Farasath Ahamed Software Engineer, WSO2 Inc.; http://wso2.com Mobile: +94777603866 Blog: blog.farazath.com Twitter: @farazath619 <https://twitter.com/farazath619> <http://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
