Re: [Dev] Issued at time (iat) incorrect in JWT created via WSO2 API Manager 2.5

[Nadeesha Gamage]

Thanks Fazlan

On Wed, Nov 14, 2018 at 4:59 PM Fazlan Nazeem  wrote:

> Hi Nadeesha,
>
> This issue was identified previously and an issue has been created to
> track this[1]
>
> [1] https://github.com/wso2/carbon-apimgt/issues/5788
>
> On Wed, Nov 14, 2018 at 4:58 PM Nadeesha Gamage  wrote:
>
>> Hi Ben,
>> It seems to be the case, Thanks for the quick turnaround.
>>
>> Nadeesha
>>
>> On Wed, Nov 14, 2018 at 4:52 PM Cooper, Ben 
>> wrote:
>>
>>> Comparing iat to exp, it looks like millseconds have been incorrectly
>>> included in the iat field, which should be expressed in seconds.  I think
>>> this field should be right-shifted 3-digits.  Looks like a bug to me.
>>>
>>>
>>>
>>>
>>>
>>> *Ben Cooper Senior Solution Architect BAE Systems Applied Intelligence*
>>>
>>> *_*
>>> *T*:  +44 (0) 3301 580420 |  *M:* +44 (0) 7717 496615 |  *E: *
>>> ben.coo...@baesystems.com
>>>
>>> BAE Systems Applied Intelligence, Surrey Research Park, Guildford,
>>> Surrey. GU2 7RQ.
>>>
>>> www.baesystems.com/businessdefence
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From:* Dev [mailto:dev-boun...@wso2.org] *On Behalf Of *Nadeesha Gamage
>>> *Sent:* 14 November 2018 11:17
>>> *To:* apim-gr...@wso2.com; dev
>>> *Subject:* [Dev] Issued at time (iat) incorrect in JWT created via WSO2
>>> API Manager 2.5
>>>
>>>
>>>
>>> *ATTENTION.* This message originates from outside BAE Systems.
>>>
>>> $subject,
>>>
>>> Please find the screenshot below of a token that I generated just now.
>>> Is there a reason for this or is this an issue?
>>>
>>>
>>>
>>> [image: image.png]
>>>
>>>
>>>
>>> --
>>>
>>> Nadeesha Gamage
>>>
>>> Senior Lead Solutions Engineer
>>> T : +94 77 394 5706
>>>
>>> B : https://nadeesha678.wordpress.com/
>>>
>>> BAE Systems will collect and process information about you that may be
>>> subject to data protection laws. For more information about how we use and
>>> disclose your personal information, how we protect your information, our
>>> legal basis to use your information, your rights and who you can contact,
>>> please refer to the relevant sections of our Privacy note at
>>> www.baesystems.com/en/cybersecurity/privacy
>>>
>>>
>>> Please consider the environment before printing this email. This message
>>> should be regarded as confidential. If you have received this email in
>>> error please notify the sender and destroy it immediately. Statements of
>>> intent shall only become binding when confirmed in hard copy by an
>>> authorised signatory. The contents of this email may relate to dealings
>>> with other companies under the control of BAE Systems PLC, details of which
>>> can be found at http://www.baesystems.com/Businesses/index.htm.
>>>
>>
>>
>> --
>> Nadeesha Gamage
>> Senior Lead Solutions Engineer
>> T : +94 77 394 5706
>> B : https://nadeesha678.wordpress.com/
>>
> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>>
>
> --
> Thanks & Regards,
>
> *Fazlan Nazeem*
> Senior Software Engineer
> WSO2 Inc
> Mobile : +94772338839
> fazl...@wso2.com
>
-- 
Nadeesha Gamage
Senior Lead Solutions Engineer
T : +94 77 394 5706
B : https://nadeesha678.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issued at time (iat) incorrect in JWT created via WSO2 API Manager 2.5

[Fazlan Nazeem]

Hi Nadeesha,

This issue was identified previously and an issue has been created to track
this[1]

[1] https://github.com/wso2/carbon-apimgt/issues/5788

On Wed, Nov 14, 2018 at 4:58 PM Nadeesha Gamage  wrote:

> Hi Ben,
> It seems to be the case, Thanks for the quick turnaround.
>
> Nadeesha
>
> On Wed, Nov 14, 2018 at 4:52 PM Cooper, Ben 
> wrote:
>
>> Comparing iat to exp, it looks like millseconds have been incorrectly
>> included in the iat field, which should be expressed in seconds.  I think
>> this field should be right-shifted 3-digits.  Looks like a bug to me.
>>
>>
>>
>>
>>
>> *Ben Cooper Senior Solution Architect BAE Systems Applied Intelligence*
>>
>> *_*
>> *T*:  +44 (0) 3301 580420 |  *M:* +44 (0) 7717 496615 |  *E: *
>> ben.coo...@baesystems.com
>>
>> BAE Systems Applied Intelligence, Surrey Research Park, Guildford,
>> Surrey. GU2 7RQ.
>>
>> www.baesystems.com/businessdefence
>>
>>
>>
>>
>>
>>
>>
>> *From:* Dev [mailto:dev-boun...@wso2.org] *On Behalf Of *Nadeesha Gamage
>> *Sent:* 14 November 2018 11:17
>> *To:* apim-gr...@wso2.com; dev
>> *Subject:* [Dev] Issued at time (iat) incorrect in JWT created via WSO2
>> API Manager 2.5
>>
>>
>>
>> *ATTENTION.* This message originates from outside BAE Systems.
>>
>> $subject,
>>
>> Please find the screenshot below of a token that I generated just now. Is
>> there a reason for this or is this an issue?
>>
>>
>>
>> [image: image.png]
>>
>>
>>
>> --
>>
>> Nadeesha Gamage
>>
>> Senior Lead Solutions Engineer
>> T : +94 77 394 5706
>>
>> B : https://nadeesha678.wordpress.com/
>>
>> BAE Systems will collect and process information about you that may be
>> subject to data protection laws. For more information about how we use and
>> disclose your personal information, how we protect your information, our
>> legal basis to use your information, your rights and who you can contact,
>> please refer to the relevant sections of our Privacy note at
>> www.baesystems.com/en/cybersecurity/privacy
>>
>>
>> Please consider the environment before printing this email. This message
>> should be regarded as confidential. If you have received this email in
>> error please notify the sender and destroy it immediately. Statements of
>> intent shall only become binding when confirmed in hard copy by an
>> authorised signatory. The contents of this email may relate to dealings
>> with other companies under the control of BAE Systems PLC, details of which
>> can be found at http://www.baesystems.com/Businesses/index.htm.
>>
>
>
> --
> Nadeesha Gamage
> Senior Lead Solutions Engineer
> T : +94 77 394 5706
> B : https://nadeesha678.wordpress.com/
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Thanks & Regards,

*Fazlan Nazeem*
Senior Software Engineer
WSO2 Inc
Mobile : +94772338839
fazl...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] siddhi-io-http access token expired solution

[Sriskandarajah Suhothayan]

you have to use "carbon-messages" and get it done, dont introduce another
dependency

On Wed, Nov 14, 2018 at 11:09 AM Thushanthan Amalanathan <
thushant...@wso2.com> wrote:

> Hi all,
> Currently, I am working on Stream Processor Siddi-io-http access token
> expired related project. In http-sink, we are passing the access token in
> the header for accessing API. Sometimes we got an authentication failure
> error because of the access token expired.
> I wrote a method for renewing access token by using refresh token. I wrote
> this method using Apache http-response library. but in siddi-io-http they
> use "carbon messages" method for getting request and response.
> do I continue with Apache http-response or do I need to change the way as
> "carbon-messages" for getting http request and response?
>
> Appreciate your comments.
>
> --
> *Thanks and Regards,*
>
> Thushanthan Amalanathan
> Associate Software Engineer
> WSO2, Inc.
> lean . enterprise . middleware
>
> Mobile : +94752239868
>
>
>

-- 
*S. Suhothayan* | Director | WSO2 Inc. 
(m) (+94) 779 756 757 | (e) s...@wso2.com | (t) @suhothayan

GET INTEGRATION AGILE
Integration Agility for Digitally Driven Business
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev