Updated the ticket! On Mon, Oct 23, 2017 at 3:38 PM, Thanuja Jayasinghe <[email protected]> wrote:
> Hi Chamara, > > SAML service provider UI uses the same admin service to add sp > configurations. So theoretically this should work. > > So can you please attach the SOAP request used to create the SAML2 service > provider? > > Thanks, > Thanuja > > On Sun, Oct 22, 2017 at 10:19 PM, Chamara Ariyarathne <[email protected]> > wrote: > >> Of course, the test was done with a WUM updated pack >> >> On Sun, Oct 22, 2017 at 10:17 PM, Hasintha Indrajee <[email protected]> >> wrote: >> >>> Did you observe this in a WUM updated pack ? If not can you please try >>> with a WUM updated pack as well ? >>> >>> On Sat, Oct 21, 2017 at 8:18 PM, Chamara Ariyarathne <[email protected]> >>> wrote: >>> >>>> >>>> >>>> On Sat, Oct 21, 2017 at 7:03 PM, Farasath Ahamed <[email protected]> >>>> wrote: >>>> >>>>> I suspect a caching issue here. >>>>> Was this a single node setup or a multi node cluster? >>>>> >>>> >>>> Reproduced in Single node. >>>> >>>>> >>>>> 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? >>>>> >>>> >>>> Sure. >>>> >>>>> >>>>> >>>>> 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 <077%20278%206766>* >>>>>> >>>>> >>>>> >>>>> -- >>>>> 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> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Chamara Ariyarathne* >>>> WSO2 Inc; http://www.wso2.com/ >>>> Mobile; *+94772786766 <077%20278%206766>* >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Hasintha Indrajee >>> WSO2, Inc. >>> Mobile:+94 771892453 <077%20189%202453> >>> >>> >> >> >> -- >> *Chamara Ariyarathne* >> WSO2 Inc; http://www.wso2.com/ >> Mobile; *+94772786766 <+94%2077%20278%206766>* >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Thanuja Lakmal* > Associate Technical Lead > WSO2 Inc. http://wso2.com/ > *lean.enterprise.middleware* > Mobile: +94715979891 > -- *Chamara Ariyarathne* WSO2 Inc; http://www.wso2.com/ Mobile; *+94772786766*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
