Hi Nayomi, I have tested this scenario and identified there is a limitation where authentication header is not getting passed in cross domain context. Updated documentation accordingly.[1]
[1] https://docs.wso2.com/display/DAS300/Analytics+JavaScript+%28JS%29+API Thanks, Malith On Mon, Oct 26, 2015 at 10:32 AM, Nayomi Dayarathne <[email protected]> wrote: > Hi Anjana, > > > We could not complete JS API testings due to unavailability of a working > reference to it.The solution dunith gave also didn't work and we did try > testings with malith as well. > > Information has given in documents also not completed.Hence has reported > following doc JIRA [1],[2]. > > [1]https://wso2.org/jira/browse/DOCUMENTATION-2605 > [2]https://wso2.org/jira/browse/DOCUMENTATION-2614 > > Please do advice on this. > > > > Nayomi Dayarathne > > *Software Engineer-QA* > Mobile : +94 (0) 775246619 <+94+(0)+775246619> > > *[email protected] <[email protected]>* > > On Fri, Oct 23, 2015 at 11:48 AM, Dunith Dhanushka <[email protected]> > wrote: > >> Hi Nayomi, >> >> Can you try following steps after adding * to cors.allowed.origins? >> >> 1. Upload analytics-client folder to a web server. You can simply use a >> Python server for this purpose [1]. >> >> 2. Edit >> <DAS_HOME>/repository/deployment/server/webapps/analytics/WEB-INF/web.xml >> fileand put * to allowed origins list. >> >> 3. Invokde http://<hostName>:<port>/analytics-client/index.html >> >> >> >> [1] https://docs.python.org/2/library/simplehttpserver.html >> >> On Fri, Oct 23, 2015 at 11:28 AM, Nayomi Dayarathne <[email protected]> >> wrote: >> >>> Kind reminder. >>> >>> Nayomi Dayarathne >>> >>> *Software Engineer-QA* >>> Mobile : +94 (0) 775246619 <+94+(0)+775246619> >>> >>> *[email protected] <[email protected]>* >>> >>> On Wed, Oct 21, 2015 at 6:52 PM, Nayomi Dayarathne <[email protected]> >>> wrote: >>> >>>> Hi Gimantha, >>>> >>>> >>>> As the per the current JS API implementation, it was not allowed to >>>> access Analytics JS API of DAS due to authentication issue and got the >>>> following authentication warnings when we debug the java script we have >>>> written using fire bug. >>>> >>>> *This site makes use of a SHA-1 Certificate; it's recommended you use >>>> certificates with signature algorithms that use hash functions stronger >>>> than SHA-1.* >>>> *Cross-Origin Request Blocked: The Same Origin Policy disallows reading >>>> the remote resource at https://localhost:9443/portal/apis/analytics?type=9 >>>> <https://localhost:9443/portal/apis/analytics?type=9>. (Reason: CORS header >>>> 'Access-Control-Allow-Origin' missing).* >>>> *Cross-Origin Request Blocked: The Same Origin Policy disallows reading >>>> the remote resource at https://localhost:9443/portal/apis/analytics?type=9 >>>> <https://localhost:9443/portal/apis/analytics?type=9>. (Reason: CORS >>>> request failed).* >>>> >>>> We have tried this scenario locally.And CORS settings has also added to >>>> the >>>> <DAS_HOME>/repository/deployment/server/webapps/analytics/WEB-INF/ >>>> web.xml file >>>> >>>> I have attached the relevant client files that we used to try this >>>> scenario, here with. >>>> >>>> Could you please provide the necessary and correct information to >>>> perform this properly? >>>> >>>> Regards, >>>> >>>> >>>> Nayomi Dayarathne >>>> >>>> *Software Engineer-QA* >>>> Mobile : +94 (0) 775246619 <+94+(0)+775246619> >>>> >>>> *[email protected] <[email protected]>* >>>> >>> >>> >> >> >> -- >> Regards, >> >> Dunith Dhanushka, >> Senior Software Engineer >> WSO2 Inc, >> >> Mobile - +94 71 8615744 >> Blog - dunithd.wordpress.com <http://blog.dunith.com> >> Twitter - @dunithd <http://twitter.com/dunithd> >> > > -- Malith Dhanushka Senior Software Engineer - Data Technologies *WSO2, Inc. : wso2.com <http://wso2.com/>* *Mobile* : +94 716 506 693
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
