Even if that works still we will need to do the change to the documentation, since if we follow the official documented method for enabling SSO it does not work for tenant users.
On 29 October 2014 20:39, Nuwan Dias <[email protected]> wrote: > What if you define the SP as a 'SaaS Application', doesn't it work? It > used to work with 1.7.0 and IS 5.0.0 AFAIR. > > On Wed, Oct 29, 2014 at 1:51 AM, Yasassri Ratnayake <[email protected]> > wrote: > >> Hi All, >> >> When enabling SSO for Publisher and Store. A new config element should be >> added to identity.xml file in the IS Node in-order for tenant users to >> login, If the element is not included the following error will be shown in >> the API-M console. >> >> ERROR - jaggery_acs:jag SAML response signature is verification failed. >> >> This is reported at [1], please do the needful to fix this. >> >> [1] - https://wso2.org/jira/browse/DOCUMENTATION-1219 >> >> With Regards, >> -- >> Yasassri Ratnayake >> Software Engineer - QA >> WSO2 Inc ; http://wso2.com >> lean.enterprise.middleware >> *Mobile : +94715933168 <%2B94715933168>* >> *Blog : http://yasassriratnayake.blogspot.com/ >> <http://yasassriratnayake.blogspot.com/>* >> > > > > -- > Nuwan Dias > > Associate Tech Lead - WSO2, Inc. http://wso2.com > email : [email protected] > Phone : +94 777 775 729 > -- Regards, Uvindra Mobile: 777733962
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
