Re: [Dev] [DEV] [IS] Clarification for the issue with OAuth1

2015-09-22 Thread Tharindu Edirisinghe 
[Adding Maduranga]

Hi Kavitha,

There have been changes done for OAuth related database tables to fix [1]
and some related issues. I am adding Maduranga of IS Team for checking this
scenario.

@Maduranga,

Can you please go through [2] and try out the same scenario with IS 5.1.0
and check what is the issue with this.

[1] https://wso2.org/jira/browse/IDENTITY-3132
[2]
http://tharindue.blogspot.com/2015/04/three-legged-oauth-10a-playground_23.html

Thank you,
TharinduE

On Tue, Sep 22, 2015 at 1:59 PM, Kavitha Subramaniyam 
wrote:

> Hi team,
>
> I have been checked OAuth-1.0a scenario in IS-5.1.0-Alpha, it has provided
> oauth token but not authorized user.
> I have followed below steps:
> - registered playground1.0a app and configured OAuth version 1.0a in IS
> - deployed playground1.0a.war webapp in tomcat
> - run the app and give OAuth Consumer Key, Consumer Secret and the Scope
> and got the request token back
> when I check the table details(used h2) for now, it shows like: PFA
> reqtok.jpeg
>
> with relevant request_token and request_token_secret, when I try to
> authorize request token, it not get authorized by IS and I got the output
> in the URL like this
> "
> https://localhost:9443/oauth/authorize-token?oauth_token=ZDyZ7htJm2UHwr1P8eGRfsIeujka
> ".
> When I check the tables after this, table IDN_OAUTH1A_REQUEST_TOKEN not
> updated AUTHORIZED=true and AUTH_user; and there were no rows added to
> table IDN_OAUTH1A_ACCESS_TOKEN. Further IS log shows: PFA log.jpeg
>
> Appreciate if anyone can clarify this issue.
>
>
> --
> Kavitha.S
> *Software Engineer -QA*
> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
> kavi...@wso2.com 
>



-- 

Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [IS] Clarification for the issue with OAuth1

2015-09-22 Thread Kavitha Subramaniyam 
Hi Maduranga,

Since this issue was identified few days back, already a jira has raised on
[1] and please follow the same to track.

[1] https://wso2.org/jira/browse/IDENTITY-3613


Thanks & Kind regards,


On Wed, Sep 23, 2015 at 9:18 AM, Maduranga Siriwardena 
wrote:

> Hi Kavitha,
>
> Seems to be there is an issue. [1] is created to track the issue.
>
> Thanks,
> Maduranga.
>
> [1] https://wso2.org/jira/browse/IDENTITY-3615
>
> On Wed, Sep 23, 2015 at 8:21 AM, Tharindu Edirisinghe 
> wrote:
>
>> [Adding Maduranga]
>>
>> Hi Kavitha,
>>
>> There have been changes done for OAuth related database tables to fix [1]
>> and some related issues. I am adding Maduranga of IS Team for checking this
>> scenario.
>>
>> @Maduranga,
>>
>> Can you please go through [2] and try out the same scenario with IS 5.1.0
>> and check what is the issue with this.
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-3132
>> [2]
>> http://tharindue.blogspot.com/2015/04/three-legged-oauth-10a-playground_23.html
>>
>> Thank you,
>> TharinduE
>>
>> On Tue, Sep 22, 2015 at 1:59 PM, Kavitha Subramaniyam 
>> wrote:
>>
>>> Hi team,
>>>
>>> I have been checked OAuth-1.0a scenario in IS-5.1.0-Alpha, it has
>>> provided oauth token but not authorized user.
>>> I have followed below steps:
>>> - registered playground1.0a app and configured OAuth version 1.0a in IS
>>> - deployed playground1.0a.war webapp in tomcat
>>> - run the app and give OAuth Consumer Key, Consumer Secret and the Scope
>>> and got the request token back
>>> when I check the table details(used h2) for now, it shows like: PFA
>>> reqtok.jpeg
>>>
>>> with relevant request_token and request_token_secret, when I try to
>>> authorize request token, it not get authorized by IS and I got the output
>>> in the URL like this
>>> "
>>> https://localhost:9443/oauth/authorize-token?oauth_token=ZDyZ7htJm2UHwr1P8eGRfsIeujka
>>> ".
>>> When I check the tables after this, table IDN_OAUTH1A_REQUEST_TOKEN not
>>> updated AUTHORIZED=true and AUTH_user; and there were no rows added to
>>> table IDN_OAUTH1A_ACCESS_TOKEN. Further IS log shows: PFA log.jpeg
>>>
>>> Appreciate if anyone can clarify this issue.
>>>
>>>
>>> --
>>> Kavitha.S
>>> *Software Engineer -QA*
>>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>>> kavi...@wso2.com 
>>>
>>
>>
>>
>> --
>>
>> Tharindu Edirisinghe
>> Software Engineer | WSO2 Inc
>> Identity Server Team
>> Blog : tharindue.blogspot.com
>> mobile : +94 775 181586
>>
>>
>>
>
>
> --
> Maduranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
> email: madura...@wso2.com
> mobile: +94718990591
>



-- 
Kavitha.S
*Software Engineer -QA*
Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
kavi...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [IS] Clarification for the issue with OAuth1

2015-09-22 Thread Maduranga Siriwardena 
Hi Kavitha,

Seems to be there is an issue. [1] is created to track the issue.

Thanks,
Maduranga.

[1] https://wso2.org/jira/browse/IDENTITY-3615

On Wed, Sep 23, 2015 at 8:21 AM, Tharindu Edirisinghe 
wrote:

> [Adding Maduranga]
>
> Hi Kavitha,
>
> There have been changes done for OAuth related database tables to fix [1]
> and some related issues. I am adding Maduranga of IS Team for checking this
> scenario.
>
> @Maduranga,
>
> Can you please go through [2] and try out the same scenario with IS 5.1.0
> and check what is the issue with this.
>
> [1] https://wso2.org/jira/browse/IDENTITY-3132
> [2]
> http://tharindue.blogspot.com/2015/04/three-legged-oauth-10a-playground_23.html
>
> Thank you,
> TharinduE
>
> On Tue, Sep 22, 2015 at 1:59 PM, Kavitha Subramaniyam 
> wrote:
>
>> Hi team,
>>
>> I have been checked OAuth-1.0a scenario in IS-5.1.0-Alpha, it has
>> provided oauth token but not authorized user.
>> I have followed below steps:
>> - registered playground1.0a app and configured OAuth version 1.0a in IS
>> - deployed playground1.0a.war webapp in tomcat
>> - run the app and give OAuth Consumer Key, Consumer Secret and the Scope
>> and got the request token back
>> when I check the table details(used h2) for now, it shows like: PFA
>> reqtok.jpeg
>>
>> with relevant request_token and request_token_secret, when I try to
>> authorize request token, it not get authorized by IS and I got the output
>> in the URL like this
>> "
>> https://localhost:9443/oauth/authorize-token?oauth_token=ZDyZ7htJm2UHwr1P8eGRfsIeujka
>> ".
>> When I check the tables after this, table IDN_OAUTH1A_REQUEST_TOKEN not
>> updated AUTHORIZED=true and AUTH_user; and there were no rows added to
>> table IDN_OAUTH1A_ACCESS_TOKEN. Further IS log shows: PFA log.jpeg
>>
>> Appreciate if anyone can clarify this issue.
>>
>>
>> --
>> Kavitha.S
>> *Software Engineer -QA*
>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>> kavi...@wso2.com 
>>
>
>
>
> --
>
> Tharindu Edirisinghe
> Software Engineer | WSO2 Inc
> Identity Server Team
> Blog : tharindue.blogspot.com
> mobile : +94 775 181586
>
>
>


-- 
Maduranga Siriwardena
Software Engineer
WSO2 Inc.

email: madura...@wso2.com
mobile: +94718990591
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev