Re: [Dev] Authentication issue in accessing analytics JS API in DAS

2015-10-26 Thread Nayomi Dayarathne 
Hi Malith,

The solution that has given in the document[1] is working(only when the
client is inside the DAS server). Thanks for the help.

Hi DAS team,

The purpose of providing an API is not satisfying by the given solution in
the document[1]. Therefore, given the current state, a client cannot access
the JS API in DAS due to authentication issue and it is not resolved
yet.Reported a JIRA[2] on this.

[1] https://docs.wso2.com/display/DAS300/Analytics+JavaScript+%28JS%29+API
[2] https://wso2.org/jira/browse/DAS-305


Regards,

Nayomi Dayarathne

*Software Engineer-QA*
Mobile : +94 (0) 775246619 <+94+(0)+775246619>

*nay...@wso2.com *

On Mon, Oct 26, 2015 at 11:01 AM, Malith Dhanushka  wrote:

> 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 
> 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>
>>
>> *nay...@wso2.com *
>>
>> On Fri, Oct 23, 2015 at 11:48 AM, Dunith Dhanushka 
>> 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
>>> /repository/deployment/server/webapps/analytics/WEB-INF/
>>> web.xml fileand put * to allowed origins list.
>>>
>>> 3. Invokde http://:/analytics-client/index.html
>>>
>>>
>>>
>>> [1] https://docs.python.org/2/library/simplehttpserver.html
>>>
>>> On Fri, Oct 23, 2015 at 11:28 AM, Nayomi Dayarathne 
>>> wrote:
>>>
 Kind reminder.

 Nayomi Dayarathne

 *Software Engineer-QA*
 Mobile : +94 (0) 775246619 <+94+(0)+775246619>

 *nay...@wso2.com *

 On Wed, Oct 21, 2015 at 6:52 PM, Nayomi Dayarathne 
 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
> . (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
> . (Reason: CORS
> request failed).*
>
> We have tried this scenario locally.And CORS settings has also added
> to the
> /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>
>
> *nay...@wso2.com *
>


>>>
>>>
>>> --
>>> Regards,
>>>
>>> Dunith Dhanushka,
>>> Senior Software Engineer
>>> WSO2 Inc,
>>>
>>> Mobile - +94 71 8615744
>>> Blog - dunithd.wordpress.com 
>>> Twitter - @dunithd 
>>>
>>
>>
>
>
> --
> Malith Dhanushka
> Senior Software Engineer - Data Technologies
> *WSO2, Inc. : wso2.com *
> *Mobile*  : +94 716 506 693
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Authentication issue in accessing analytics JS API in DAS

2015-10-25 Thread Nayomi Dayarathne 
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>

*nay...@wso2.com *

On Fri, Oct 23, 2015 at 11:48 AM, Dunith Dhanushka  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 /repository/deployment/server/webapps/analytics/WEB-INF/
> web.xml fileand put * to allowed origins list.
>
> 3. Invokde http://:/analytics-client/index.html
>
>
>
> [1] https://docs.python.org/2/library/simplehttpserver.html
>
> On Fri, Oct 23, 2015 at 11:28 AM, Nayomi Dayarathne 
> wrote:
>
>> Kind reminder.
>>
>> Nayomi Dayarathne
>>
>> *Software Engineer-QA*
>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>
>> *nay...@wso2.com *
>>
>> On Wed, Oct 21, 2015 at 6:52 PM, Nayomi Dayarathne 
>> 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
>>> . (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
>>> . (Reason: CORS
>>> request failed).*
>>>
>>> We have tried this scenario locally.And CORS settings has also added to
>>> the
>>> /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>
>>>
>>> *nay...@wso2.com *
>>>
>>
>>
>
>
> --
> Regards,
>
> Dunith Dhanushka,
> Senior Software Engineer
> WSO2 Inc,
>
> Mobile - +94 71 8615744
> Blog - dunithd.wordpress.com 
> Twitter - @dunithd 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Authentication issue in accessing analytics JS API in DAS

2015-10-25 Thread Malith Dhanushka 
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  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>
>
> *nay...@wso2.com *
>
> On Fri, Oct 23, 2015 at 11:48 AM, Dunith Dhanushka 
> 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
>> /repository/deployment/server/webapps/analytics/WEB-INF/web.xml
>>  fileand put * to allowed origins list.
>>
>> 3. Invokde http://:/analytics-client/index.html
>>
>>
>>
>> [1] https://docs.python.org/2/library/simplehttpserver.html
>>
>> On Fri, Oct 23, 2015 at 11:28 AM, Nayomi Dayarathne 
>> wrote:
>>
>>> Kind reminder.
>>>
>>> Nayomi Dayarathne
>>>
>>> *Software Engineer-QA*
>>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>>
>>> *nay...@wso2.com *
>>>
>>> On Wed, Oct 21, 2015 at 6:52 PM, Nayomi Dayarathne 
>>> 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
 . (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
 . (Reason: CORS
 request failed).*

 We have tried this scenario locally.And CORS settings has also added to
 the
 /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>

 *nay...@wso2.com *

>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Dunith Dhanushka,
>> Senior Software Engineer
>> WSO2 Inc,
>>
>> Mobile - +94 71 8615744
>> Blog - dunithd.wordpress.com 
>> Twitter - @dunithd 
>>
>
>


-- 
Malith Dhanushka
Senior Software Engineer - Data Technologies
*WSO2, Inc. : wso2.com *
*Mobile*  : +94 716 506 693
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Authentication issue in accessing analytics JS API in DAS

2015-10-23 Thread Dunith Dhanushka 
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 /repository/deployment/server/webapps/analytics/WEB-INF/
web.xml fileand put * to allowed origins list.

3. Invokde http://:/analytics-client/index.html



[1] https://docs.python.org/2/library/simplehttpserver.html

On Fri, Oct 23, 2015 at 11:28 AM, Nayomi Dayarathne  wrote:

> Kind reminder.
>
> Nayomi Dayarathne
>
> *Software Engineer-QA*
> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>
> *nay...@wso2.com *
>
> On Wed, Oct 21, 2015 at 6:52 PM, Nayomi Dayarathne 
> 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
>> . (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
>> . (Reason: CORS
>> request failed).*
>>
>> We have tried this scenario locally.And CORS settings has also added to
>> the
>> /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>
>>
>> *nay...@wso2.com *
>>
>
>


-- 
Regards,

Dunith Dhanushka,
Senior Software Engineer
WSO2 Inc,

Mobile - +94 71 8615744
Blog - dunithd.wordpress.com 
Twitter - @dunithd 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev