Re: [Dev] Giving the different Access tokens in API manager 2.5.0 when try to generate new tokens before expired the access token.

2018-07-03 Thread Prasanna Dangalla 
Hi All,

Please find the fix for this.[1]

[1] - https://github.com/wso2/carbon-apimgt/pull/5529

Thanks
Prasanna

On Wed, Jul 4, 2018 at 9:45 AM Prasanna Dangalla  wrote:

> Hi Rajith,
> On Wed, Jul 4, 2018 at 4:56 AM Rajith Roshan  wrote:
>
>> I guess we have to call the getIdentityOauthTokenIssuer method in line
>> [1], instead of " getOAuthTokenGenerator" method.
>>
> I'll check this.
> Thanks
> Prasanna
>
>>
>> [1] -
>> https://github.com/wso2/carbon-apimgt/blob/6.x/components/apimgt/org.wso2.carbon.apimgt.keymgt/src/main/java/org/wso2/carbon/apimgt/keymgt/issuers/APIMTokenIssuer.java#L112
>>
>> On Tue, Jul 3, 2018 at 5:55 AM Nuwan Dias  wrote:
>>
>>> [Adding Prasanna].
>>>
>>> I don't think this behavior is intentional. Therefore we will have to
>>> fix this.
>>>
>>> On Tue, Jul 3, 2018 at 5:44 PM Omindu Rathnaweera 
>>> wrote:
>>>
 Hi Fazlan/Nalaka,

 This behavior is not there in the IS 5.6.0 release candidate. I did a
 small test by reverting the APIMTokenIssuer to the default one and the
 issue got resolved. Better to check the APIMTokenIssuer.

 On Mon, Jul 2, 2018 at 7:48 PM Fazlan Nazeem  wrote:

> This seems to be true.
>
> @IS team,  What is the reason to expire the token before the expiry
> time and without a revocation request?
>
> On Mon, Jul 2, 2018 at 2:31 PM Nalaka Senarathna 
> wrote:
>
>> In the latest release of API manager if we try to generate new access
>> tokens before it expired using "password grant type " output is different
>> access tokens with the same refresh token. when checking the database it
>> shows the state is "EXPIRED" of the previous access token.
>>
>> In earlier releases, if the access token is not expired output was
>> the same access token when trying to generate using the password grant 
>> type.
>>
>> Is that change made by intentionally In new release?
>>
>> regards.
>> --
>> *Nalaka Senarathna*
>> *Associate Software Engineer | WSO2*
>>
>> *Email : nala...@wso2.com *
>> *Mobile : +94714118474*
>> *web :  https://wso2.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
>

 Regards,
 Omindu
 --
 Omindu Rathnaweera
 Senior Software Engineer, WSO2 Inc.
 Mobile: +94 771 197 211
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev

>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Director - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>> Rajith Roshan
>> Senior Software Engineer, WSO2 Inc.
>> Mobile: +94-717-064-214
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Giving the different Access tokens in API manager 2.5.0 when try to generate new tokens before expired the access token.

2018-07-03 Thread Prasanna Dangalla 
Hi Rajith,
On Wed, Jul 4, 2018 at 4:56 AM Rajith Roshan  wrote:

> I guess we have to call the getIdentityOauthTokenIssuer method in line
> [1], instead of " getOAuthTokenGenerator" method.
>
I'll check this.
Thanks
Prasanna

>
> [1] -
> https://github.com/wso2/carbon-apimgt/blob/6.x/components/apimgt/org.wso2.carbon.apimgt.keymgt/src/main/java/org/wso2/carbon/apimgt/keymgt/issuers/APIMTokenIssuer.java#L112
>
> On Tue, Jul 3, 2018 at 5:55 AM Nuwan Dias  wrote:
>
>> [Adding Prasanna].
>>
>> I don't think this behavior is intentional. Therefore we will have to fix
>> this.
>>
>> On Tue, Jul 3, 2018 at 5:44 PM Omindu Rathnaweera 
>> wrote:
>>
>>> Hi Fazlan/Nalaka,
>>>
>>> This behavior is not there in the IS 5.6.0 release candidate. I did a
>>> small test by reverting the APIMTokenIssuer to the default one and the
>>> issue got resolved. Better to check the APIMTokenIssuer.
>>>
>>> On Mon, Jul 2, 2018 at 7:48 PM Fazlan Nazeem  wrote:
>>>
 This seems to be true.

 @IS team,  What is the reason to expire the token before the expiry
 time and without a revocation request?

 On Mon, Jul 2, 2018 at 2:31 PM Nalaka Senarathna 
 wrote:

> In the latest release of API manager if we try to generate new access
> tokens before it expired using "password grant type " output is different
> access tokens with the same refresh token. when checking the database it
> shows the state is "EXPIRED" of the previous access token.
>
> In earlier releases, if the access token is not expired output was the
> same access token when trying to generate using the password grant type.
>
> Is that change made by intentionally In new release?
>
> regards.
> --
> *Nalaka Senarathna*
> *Associate Software Engineer | WSO2*
>
> *Email : nala...@wso2.com *
> *Mobile : +94714118474*
> *web :  https://wso2.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

>>>
>>> Regards,
>>> Omindu
>>> --
>>> Omindu Rathnaweera
>>> Senior Software Engineer, WSO2 Inc.
>>> Mobile: +94 771 197 211
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Director - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> Rajith Roshan
> Senior Software Engineer, WSO2 Inc.
> Mobile: +94-717-064-214
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Giving the different Access tokens in API manager 2.5.0 when try to generate new tokens before expired the access token.

2018-07-03 Thread Isuru Haththotuwa 
Ideally there should be separate entries for JWT and OAuth2 token issuers
in the identity.xml configuration.

On Wed, Jul 4, 2018 at 4:56 AM, Rajith Roshan  wrote:

> I guess we have to call the getIdentityOauthTokenIssuer method in line
> [1], instead of " getOAuthTokenGenerator" method.
>
> [1] - https://github.com/wso2/carbon-apimgt/blob/6.x/
> components/apimgt/org.wso2.carbon.apimgt.keymgt/src/main/
> java/org/wso2/carbon/apimgt/keymgt/issuers/APIMTokenIssuer.java#L112
>
> On Tue, Jul 3, 2018 at 5:55 AM Nuwan Dias  wrote:
>
>> [Adding Prasanna].
>>
>> I don't think this behavior is intentional. Therefore we will have to fix
>> this.
>>
>> On Tue, Jul 3, 2018 at 5:44 PM Omindu Rathnaweera 
>> wrote:
>>
>>> Hi Fazlan/Nalaka,
>>>
>>> This behavior is not there in the IS 5.6.0 release candidate. I did a
>>> small test by reverting the APIMTokenIssuer to the default one and the
>>> issue got resolved. Better to check the APIMTokenIssuer.
>>>
>>> On Mon, Jul 2, 2018 at 7:48 PM Fazlan Nazeem  wrote:
>>>
 This seems to be true.

 @IS team,  What is the reason to expire the token before the expiry
 time and without a revocation request?

 On Mon, Jul 2, 2018 at 2:31 PM Nalaka Senarathna 
 wrote:

> In the latest release of API manager if we try to generate new access
> tokens before it expired using "password grant type " output is different
> access tokens with the same refresh token. when checking the database it
> shows the state is "EXPIRED" of the previous access token.
>
> In earlier releases, if the access token is not expired output was the
> same access token when trying to generate using the password grant type.
>
> Is that change made by intentionally In new release?
>
> regards.
> --
> *Nalaka Senarathna*
> *Associate Software Engineer | WSO2*
>
> *Email : nala...@wso2.com *
> *Mobile : +94714118474*
> *web :  https://wso2.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

>>>
>>> Regards,
>>> Omindu
>>> --
>>> Omindu Rathnaweera
>>> Senior Software Engineer, WSO2 Inc.
>>> Mobile: +94 771 197 211
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Director - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> Rajith Roshan
> Senior Software Engineer, WSO2 Inc.
> Mobile: +94-717-064-214
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Giving the different Access tokens in API manager 2.5.0 when try to generate new tokens before expired the access token.

2018-07-03 Thread Rajith Roshan 
I guess we have to call the getIdentityOauthTokenIssuer method in line [1],
instead of " getOAuthTokenGenerator" method.

[1] -
https://github.com/wso2/carbon-apimgt/blob/6.x/components/apimgt/org.wso2.carbon.apimgt.keymgt/src/main/java/org/wso2/carbon/apimgt/keymgt/issuers/APIMTokenIssuer.java#L112

On Tue, Jul 3, 2018 at 5:55 AM Nuwan Dias  wrote:

> [Adding Prasanna].
>
> I don't think this behavior is intentional. Therefore we will have to fix
> this.
>
> On Tue, Jul 3, 2018 at 5:44 PM Omindu Rathnaweera  wrote:
>
>> Hi Fazlan/Nalaka,
>>
>> This behavior is not there in the IS 5.6.0 release candidate. I did a
>> small test by reverting the APIMTokenIssuer to the default one and the
>> issue got resolved. Better to check the APIMTokenIssuer.
>>
>> On Mon, Jul 2, 2018 at 7:48 PM Fazlan Nazeem  wrote:
>>
>>> This seems to be true.
>>>
>>> @IS team,  What is the reason to expire the token before the expiry time
>>> and without a revocation request?
>>>
>>> On Mon, Jul 2, 2018 at 2:31 PM Nalaka Senarathna 
>>> wrote:
>>>
 In the latest release of API manager if we try to generate new access
 tokens before it expired using "password grant type " output is different
 access tokens with the same refresh token. when checking the database it
 shows the state is "EXPIRED" of the previous access token.

 In earlier releases, if the access token is not expired output was the
 same access token when trying to generate using the password grant type.

 Is that change made by intentionally In new release?

 regards.
 --
 *Nalaka Senarathna*
 *Associate Software Engineer | WSO2*

 *Email : nala...@wso2.com *
 *Mobile : +94714118474*
 *web :  https://wso2.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
>>>
>>
>> Regards,
>> Omindu
>> --
>> Omindu Rathnaweera
>> Senior Software Engineer, WSO2 Inc.
>> Mobile: +94 771 197 211
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> Nuwan Dias
>
> Director - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Rajith Roshan
Senior Software Engineer, WSO2 Inc.
Mobile: +94-7 17-064-214
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Giving the different Access tokens in API manager 2.5.0 when try to generate new tokens before expired the access token.

2018-07-03 Thread Nuwan Dias 
[Adding Prasanna].

I don't think this behavior is intentional. Therefore we will have to fix
this.

On Tue, Jul 3, 2018 at 5:44 PM Omindu Rathnaweera  wrote:

> Hi Fazlan/Nalaka,
>
> This behavior is not there in the IS 5.6.0 release candidate. I did a
> small test by reverting the APIMTokenIssuer to the default one and the
> issue got resolved. Better to check the APIMTokenIssuer.
>
> On Mon, Jul 2, 2018 at 7:48 PM Fazlan Nazeem  wrote:
>
>> This seems to be true.
>>
>> @IS team,  What is the reason to expire the token before the expiry time
>> and without a revocation request?
>>
>> On Mon, Jul 2, 2018 at 2:31 PM Nalaka Senarathna 
>> wrote:
>>
>>> In the latest release of API manager if we try to generate new access
>>> tokens before it expired using "password grant type " output is different
>>> access tokens with the same refresh token. when checking the database it
>>> shows the state is "EXPIRED" of the previous access token.
>>>
>>> In earlier releases, if the access token is not expired output was the
>>> same access token when trying to generate using the password grant type.
>>>
>>> Is that change made by intentionally In new release?
>>>
>>> regards.
>>> --
>>> *Nalaka Senarathna*
>>> *Associate Software Engineer | WSO2*
>>>
>>> *Email : nala...@wso2.com *
>>> *Mobile : +94714118474*
>>> *web :  https://wso2.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
>>
>
> Regards,
> Omindu
> --
> Omindu Rathnaweera
> Senior Software Engineer, WSO2 Inc.
> Mobile: +94 771 197 211
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
Nuwan Dias

Director - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Giving the different Access tokens in API manager 2.5.0 when try to generate new tokens before expired the access token.

2018-07-03 Thread Omindu Rathnaweera 
Hi Fazlan/Nalaka,

This behavior is not there in the IS 5.6.0 release candidate. I did a small
test by reverting the APIMTokenIssuer to the default one and the issue got
resolved. Better to check the APIMTokenIssuer.

On Mon, Jul 2, 2018 at 7:48 PM Fazlan Nazeem  wrote:

> This seems to be true.
>
> @IS team,  What is the reason to expire the token before the expiry time
> and without a revocation request?
>
> On Mon, Jul 2, 2018 at 2:31 PM Nalaka Senarathna  wrote:
>
>> In the latest release of API manager if we try to generate new access
>> tokens before it expired using "password grant type " output is different
>> access tokens with the same refresh token. when checking the database it
>> shows the state is "EXPIRED" of the previous access token.
>>
>> In earlier releases, if the access token is not expired output was the
>> same access token when trying to generate using the password grant type.
>>
>> Is that change made by intentionally In new release?
>>
>> regards.
>> --
>> *Nalaka Senarathna*
>> *Associate Software Engineer | WSO2*
>>
>> *Email : nala...@wso2.com *
>> *Mobile : +94714118474*
>> *web :  https://wso2.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
>

Regards,
Omindu
-- 
Omindu Rathnaweera
Senior Software Engineer, WSO2 Inc.
Mobile: +94 771 197 211
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to add transport headers to JWT

2018-07-03 Thread gayan gunawardana 
Hi Bhathiya,

On Tue, Jul 3, 2018 at 1:58 PM, Bhathiya Jayasekara 
wrote:

> Hi Gay an,
>
> The JWT is generated and signed by the KM and gateway can't modify it. And
> the transport headers are not sent to KM by the GW either. Therefore there
> is no way to add HTTP headers to the JWT. However, you can send the headers
> as headers themselves to the backend.
>
Thanks a lot for clarification.

>
> Thanks,
> Bhathiya
>
> On Tue, Jul 3, 2018 at 12:12 PM gayan gunawardana 
> wrote:
>
>> Hi APIM team,
>>
>> Is there a way to put transport headers coming from incoming request into
>> JWT [1] generated for backend service ?
>>
>> [1] https://docs.wso2.com/display/AM220/Passing+Enduser+
>> Attributes+to+the+Backend+Using+JWT
>>
>> Thanks,
>> Gayan
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Associate Technical Lead,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>



-- 
Gayan
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Stream Processor] Issue in creating custom widgets in Stream Processor

2018-07-03 Thread Niveathika Rajendran 
@Damith Wickramasinghe  It's not that we are missing any
steps, the documentation is disjoint and unclear.

@Rukshani Weerasinha  Shall we revamp the documentation
under "Creating custom widgets", especially under SP4.2.0 space, since the
improvements[1] done for 4.2.0 release, will make the example redundant.

[1] [SP] [Solutions] Data provider configurations in solution widgets

Best Regards,
*Niveathika Rajendran,*
*Software Engineer.*
*Mobile : +94 077 903 7536*





On Tue, Jul 3, 2018 at 2:55 PM Damith Wickramasinghe 
wrote:

> @Niveathika if we are missing any step in the doc , please create a doc
> jira .
>
> Thanks,
> Damith
>
> On Tue, Jul 3, 2018 at 9:12 AM, Niveathika Rajendran 
> wrote:
>
>> Hi Thisaru,
>>
>> From the logs, it seems you have updated HelloWorld.jsx file as in Step
>> 4. Here, we are importing "ExtendedWiget.jsx" file created in Step 3,
>> adding that to the src folder should resolve this issue.
>>
>> Best Regards,
>> *Niveathika Rajendran,*
>> *Software Engineer.*
>> *Mobile : +94 077 903 7536*
>>
>>
>>
>>
>>
>> On Tue, Jul 3, 2018 at 2:30 PM Thisaru Guruge  wrote:
>>
>>> Hi,
>>>
>>> I am trying to create a custom widget in SP dashboard and I followed the
>>> example shown in the documentation on creating custom widgets
>>> 
>>>
>>> I followed exactly same and getting following error when tried to build
>>> the widget:
>>>
>>> ERROR in ./HelloWorld.jsx
>>>
>>> Module not found: Error: Can't resolve './ExtendedWidget' in
>>> '/Users/Thisaru/Projects/IS_Analytics_Migation/carbon-dashboards/samples/widgets/HelloWorld/src'
>>>
>>>  @ ./HelloWorld.jsx 9:23-50
>>>
>>> npm ERR! code ELIFECYCLE
>>>
>>> npm ERR! errno 2
>>>
>>> npm ERR! hello-world-widget@1.0.0 build: `webpack -p`
>>>
>>> npm ERR! Exit status 2
>>>
>>> npm ERR!
>>>
>>> npm ERR! Failed at the hello-world-widget@1.0.0 build script.
>>>
>>> npm ERR! This is probably not a problem with npm. There is likely
>>> additional logging output above.
>>>
>>> Can anyone help me on this ?
>>>
>>> --
>>> Thanks and Best Regards
>>> Thisaru Guruge
>>> Software Engineer
>>> WSO2 Inc.: http://www.wso2.com
>>>
>>> Mobile: +94 71 720 9720
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> 
> lean.enterprise.middleware
>
> mobile: *+94728671315*
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IAM: org.apache.rahas.TrustException while executing SSO with WS-Trust scenario

2018-07-03 Thread Achini Jayasena 
+ dev@wso2.org


*Thanks & Best Regards!*

*Achini Jayasena*
*Software Engineer - QA | WSO2*

Email: achi...@wso2.com
Mobile: +943 882 897

[image: http://wso2.com/signature] 

On Mon, Jul 2, 2018 at 7:36 PM, Achini Jayasena  wrote:

> Hi All,
>
> Could you help to solve following issue.
>
> *Scenario:* SSO with WS-Trust
> *Reference:* https://docs.wso2.com/display/IS550/WS-Trust
> *Issue Description:* Executing sts-clien.sh file (file location:
> IS-SAMPLES/modules/samples/sts/sts-client) create following exception
> *Issue: *
>
> achini@achini-ThinkPad-X1-Carbon-5th:~/IS/is-samples/
> modules/samples/sts/sts-client$ export CLASSPATH=$CLASSPATH:../lib/*:
> target/*
> achini@achini-ThinkPad-X1-Carbon-5th:~/IS/is-samples/
> modules/samples/sts/sts-client$ $JAVA_HOME/bin/java
> org.wso2.carbon.identity.samples.sts.Client $@
> log4j:WARN No appenders could be found for logger
> (org.apache.axis2.deployment.FileSystemConfigurator).
> log4j:WARN Please initialize the log4j system properly.
>  xmlns:xs="http://www.w3.org/2001/XMLSchema; ID="urn:uuid:
> 2971E96344F259222F1530539326505" IssueInstant="2018-07-02T13:48:46.497Z"
> Version="2.0">https://localhost xmlns:ds="http://www.w3.org/2000/09/xmldsig#;>
> 
> http://www.w3.org/
> 2001/10/xml-exc-c14n#" />
> http://www.w3.org/2000/09/xmldsig#rsa-sha1;
> />
> 
> 
> http://www.w3.org/2000/09/xmldsig#enveloped-
> signature" />
>  Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#;> xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#; PrefixList="xs"
> />
> 
> http://www.w3.org/2000/09/xmldsig#sha1; />
> MJkaDjwfnE9CERG2E/Qhcjr+ig4=
> 
> 
> 
> HX2GsquRrgmoLjPbjSKJUGn938VpsgfzjkyzkWDSkW/M6+UbjsuJYnC+
> ZjeXwX10a/sE/kFe5J9z
> js451ikBqs8cxxAemZ/wR+1HQINXB9L7feYtx8IF/xjEe/
> vJ9Oms4p0IqHhxSoktlv6RNd2v1m9t
> m6vrTYH+Srj++GVuX+gSK4GY/04DLMenv4Se8UyOK2qfU5RWQrYa/
> Le+1lsN51yFIxTUpNzNn4/+
> /W7gM6Wa8M0cIc3eVVWIBvyPe9q9PctAG2f0s7d3TSAvDRqKGi58CpuPG11r1
> 0aF39Knk31WemzX
> a49583MLJx+l+zxU4V0+74TSV+lROYX6tkHoyQ==
> 
> MIIDSTCCAjGgAwIBAgIEAoLQ/
> TANBgkqhkiG9w0BAQsFADBVMQswCQYDVQQGEwJVUzELMAkGA1UE
> CBMCQ0ExFjAUBgNVBAcTDU1vdW50YWluIFZpZXcxDTALBgNVBAoTBFdTTzIx
> EjAQBgNVBAMTCWxv
> Y2FsaG9zdDAeFw0xNzA3MTkwNjUyNTFaFw0yNzA3MTcwNjUyNTFaMFUxCzAJ
> BgNVBAYTAlVTMQsw
> CQYDVQQIEwJDQTEWMBQGA1UEBxMNTW91bnRhaW4gVmlldzENMAsGA1UEChME
> V1NPMjESMBAGA1UE
> AxMJbG9jYWxob3N0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
> luZFdW1ynitztkWL
> C6xKegbRWxky+5P0p4ShYEOkHs30QI2VCuR6Qo4Bz5rTgLBrky03W1GAVrZxuvKRGj9V9+
> PmjdGt
> au4CTXu9pLLcqnruaczoSdvBYA3lS9a7zgFU0+s6kMl2EhB+
> rk7gXluEep7lIOenzfl2f6IoTKa2
> fVgVd3YKiSGsyL4tztS70vmmX121qm0sTJdKWP4HxXyqK9neolXI9fYyHOYI
> LVNZ69z/73OOVhkh
> /mvTmWZLM7GM6sApmyLX6OXUp8z0pkY+vT/9+zRxxQs7GurC4/C1nK3rI/
> 0ySUgGEafO1atNjYml
> FN+M3tZX6nEcA6g94IavyQIDAQABoyEwHzAdBgNVHQ4EFgQUtS8kIYxQ8UVvVrZ
> Sdgyide9OHxUw
> DQYJKoZIhvcNAQELBQADggEBABfk5mqsVUrpFCYTZZhOxTRRpGXqoW1G05bO
> xHxs42Paxw8rAJ06
> Pty9jqM1CgRPpqvZa2lPQBQqZrHkdDE06q4NG0DqMH8NT+
> tNkXBe9YTre3EJCSfsvswtLVDZ7GDv
> THKojJjQvdVCzRj6XH5Truwefb4BJz9APtnlyJIvjHk1hdozqyOniVZd0QOx
> LAbcdt946chNdQvC
> m6aUOputp8Xogr0KBnEy3U8es2cAfNZaEkPU8Va5bU6Xjny8zGQnXCXxPKp7
> sMpgO93nPBt/liX1
> qfyXM7xEotWoxmm6HZx8oWQ8U5aiXjZ5RKDWCCq4ZuXl6wVsUz1iE61suO5y
> Wi8= Signature>admin Method="urn:oasis:names:tc:SAML:2.0:cm:bearer" 
> /> NotBefore="2018-07-02T13:48:46.497Z" NotOnOrAfter="2018-07-02T13:
> 53:46.497Z">https://localhost:
> 10443/services/echo Conditions>http://wso2.org/claims/emailaddress; NameFormat="http://wso2.org/
> claims/emailaddress">http://www.w3.org/
> 2001/XMLSchema-instance" xsi:type="xs:string">ad...@wso2.com AttributeValue>http://wso2.org/claims/givenname; NameFormat="http://wso2.org/
> claims/givenname">http://www.w3.org/
> 2001/XMLSchema-instance" xsi:type="xs:string">admin saml2:AttributeValue> AuthnInstant="2018-07-02T13:48:46.504Z"> AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:
> classes:Password AuthnStatement>
> Renewing 2.0
> org.apache.rahas.TrustException: Error in renewing token from : "
> https://localhost:9443/services/wso2carbon-sts;
> at org.apache.rahas.client.STSClient.renewToken(STSClient.java:386)
> at org.wso2.carbon.identity.samples.sts.Client.run(Client.java:153)
> at org.wso2.carbon.identity.samples.sts.Client.main(Client.java:94)
> Caused by: org.apache.axis2.AxisFault: java.lang.NullPointerException
> at org.apache.axis2.util.Utils.getInboundFaultFromMessageCont
> ext(Utils.java:531)
> at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(
> OutInAxisOperation.java:375)
> at org.apache.axis2.description.OutInAxisOperationClient.send(
> OutInAxisOperation.java:421)
> at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(
> OutInAxisOperation.java:229)
> at org.apache.axis2.client.OperationClient.execute(
> OperationClient.java:165)
> at org.apache.axis2.client.ServiceClient.sendReceive(
> ServiceClient.java:555)
> at org.apache.rahas.client.STSClient.renewToken(STSClient.java:378)
>
>
> *Thanks & Best Regards!*
>
>

Re: [Dev] [Stream Processor] Issue in creating custom widgets in Stream Processor

2018-07-03 Thread Damith Wickramasinghe 
@Niveathika if we are missing any step in the doc , please create a doc
jira .

Thanks,
Damith

On Tue, Jul 3, 2018 at 9:12 AM, Niveathika Rajendran 
wrote:

> Hi Thisaru,
>
> From the logs, it seems you have updated HelloWorld.jsx file as in Step 4.
> Here, we are importing "ExtendedWiget.jsx" file created in Step 3, adding
> that to the src folder should resolve this issue.
>
> Best Regards,
> *Niveathika Rajendran,*
> *Software Engineer.*
> *Mobile : +94 077 903 7536*
>
>
>
>
>
> On Tue, Jul 3, 2018 at 2:30 PM Thisaru Guruge  wrote:
>
>> Hi,
>>
>> I am trying to create a custom widget in SP dashboard and I followed the
>> example shown in the documentation on creating custom widgets
>> 
>>
>> I followed exactly same and getting following error when tried to build
>> the widget:
>>
>> ERROR in ./HelloWorld.jsx
>>
>> Module not found: Error: Can't resolve './ExtendedWidget' in
>> '/Users/Thisaru/Projects/IS_Analytics_Migation/carbon-
>> dashboards/samples/widgets/HelloWorld/src'
>>
>>  @ ./HelloWorld.jsx 9:23-50
>>
>> npm ERR! code ELIFECYCLE
>>
>> npm ERR! errno 2
>>
>> npm ERR! hello-world-widget@1.0.0 build: `webpack -p`
>>
>> npm ERR! Exit status 2
>>
>> npm ERR!
>>
>> npm ERR! Failed at the hello-world-widget@1.0.0 build script.
>>
>> npm ERR! This is probably not a problem with npm. There is likely
>> additional logging output above.
>>
>> Can anyone help me on this ?
>>
>> --
>> Thanks and Best Regards
>> Thisaru Guruge
>> Software Engineer
>> WSO2 Inc.: http://www.wso2.com
>>
>> Mobile: +94 71 720 9720
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Senior Software Engineer
WSO2 Inc.; http://wso2.com

lean.enterprise.middleware

mobile: *+94728671315*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Stream Processor] Issue in creating custom widgets in Stream Processor

2018-07-03 Thread Niveathika Rajendran 
Hi Thisaru,

>From the logs, it seems you have updated HelloWorld.jsx file as in Step 4.
Here, we are importing "ExtendedWiget.jsx" file created in Step 3, adding
that to the src folder should resolve this issue.

Best Regards,
*Niveathika Rajendran,*
*Software Engineer.*
*Mobile : +94 077 903 7536*





On Tue, Jul 3, 2018 at 2:30 PM Thisaru Guruge  wrote:

> Hi,
>
> I am trying to create a custom widget in SP dashboard and I followed the
> example shown in the documentation on creating custom widgets
> 
>
> I followed exactly same and getting following error when tried to build
> the widget:
>
> ERROR in ./HelloWorld.jsx
>
> Module not found: Error: Can't resolve './ExtendedWidget' in
> '/Users/Thisaru/Projects/IS_Analytics_Migation/carbon-dashboards/samples/widgets/HelloWorld/src'
>
>  @ ./HelloWorld.jsx 9:23-50
>
> npm ERR! code ELIFECYCLE
>
> npm ERR! errno 2
>
> npm ERR! hello-world-widget@1.0.0 build: `webpack -p`
>
> npm ERR! Exit status 2
>
> npm ERR!
>
> npm ERR! Failed at the hello-world-widget@1.0.0 build script.
>
> npm ERR! This is probably not a problem with npm. There is likely
> additional logging output above.
>
> Can anyone help me on this ?
>
> --
> Thanks and Best Regards
> Thisaru Guruge
> Software Engineer
> WSO2 Inc.: http://www.wso2.com
>
> Mobile: +94 71 720 9720
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Stream Processor] Issue in creating custom widgets in Stream Processor

2018-07-03 Thread Thisaru Guruge 
Hi,

I am trying to create a custom widget in SP dashboard and I followed the
example shown in the documentation on creating custom widgets


I followed exactly same and getting following error when tried to build the
widget:

ERROR in ./HelloWorld.jsx

Module not found: Error: Can't resolve './ExtendedWidget' in
'/Users/Thisaru/Projects/IS_Analytics_Migation/carbon-dashboards/samples/widgets/HelloWorld/src'

 @ ./HelloWorld.jsx 9:23-50

npm ERR! code ELIFECYCLE

npm ERR! errno 2

npm ERR! hello-world-widget@1.0.0 build: `webpack -p`

npm ERR! Exit status 2

npm ERR!

npm ERR! Failed at the hello-world-widget@1.0.0 build script.

npm ERR! This is probably not a problem with npm. There is likely
additional logging output above.

Can anyone help me on this ?

-- 
Thanks and Best Regards
Thisaru Guruge
Software Engineer
WSO2 Inc.: http://www.wso2.com

Mobile: +94 71 720 9720
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to add transport headers to JWT

2018-07-03 Thread Bhathiya Jayasekara 
Hi Gay an,

The JWT is generated and signed by the KM and gateway can't modify it. And
the transport headers are not sent to KM by the GW either. Therefore there
is no way to add HTTP headers to the JWT. However, you can send the headers
as headers themselves to the backend.

Thanks,
Bhathiya

On Tue, Jul 3, 2018 at 12:12 PM gayan gunawardana 
wrote:

> Hi APIM team,
>
> Is there a way to put transport headers coming from incoming request into
> JWT [1] generated for backend service ?
>
> [1]
> https://docs.wso2.com/display/AM220/Passing+Enduser+Attributes+to+the+Backend+Using+JWT
>
> Thanks,
> Gayan
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
*Bhathiya Jayasekara*
*Associate Technical Lead,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev