Re: [Dev] Account association with 'userAttribute' usecase in SMSOTP and TOTP

2017-10-23 Thread Kanapriya Kuleswararajan 
Hi Malithi,

Please find the comments in line.

>
> I was using $subject to associate federated identity over google and
> facebook to the local user while configuring SMSOTP and TOTP as the second
> factor authentication mechanism.
>
> As I noted, for this to work I had to configure the federated claim, as
> the userAttribute in the authenticator configuration, from which the
> respective local user will be mapped.
> Ex:
> Added below in Google and Facebook case
> email
>
> 1. The first question is what will happen when multi-option authentication
> is configured as the first step?
> I tried with Google and Facebook configured as muti-option in the first
> step while having 'email' configured as the 'userAttribute'. That worked
> because in both, there is a federated claim as 'email'. But, what if some
> other authenticator is configured which will not have 'email' claim and
> mail address of the user is received over a different claim format ?
> As I see, the local claim (wso2 claim) should be configured in the
> authenticator configuration and during the authentication flow, local claim
> configured in the authenticator config should be picked, and the claim
> value should be resolved after transforming federated claims received to
> local dialect (wso2 dialect).
>
>  When multi-option configured as first step (Google and Facebook) , and
say, if the cliams (email) is different format in both authenticator , then
you can have separate config with authenticator name in authentication.xml
file as follow.

**
*mailaddress*
*mailaddress*
**

You can have similar config as above for Google authenticator as well.

2. Noted, that in each authenticator an additional parameter needs to be
> configured to denote 'userAttribute' mapping. Is this how (1) above is
> achieved ?
> However, the respective configurations in SMSOTP and TOTP with this regard
> are not consistent. Moreover, I feel transforming back to the local dialect
> and using that to retrieve the attribute to be mapped is the way to do.
> With that this becomes a redundant config.
>

For the userAttribute usecase, you can use the parameter name for TOTP,
SMSOTP as I mentioned in the above config with the prefix of the
authenticator name which is configured as second step. This leads the
configurations more consistent. All these things documented in [1].

[1] https://docs.wso2.com/display/ISCONNECTORS/Configuring+TOTP+
Authenticator#ConfiguringTOTPAuthenticator-ConfiguringtheserviceproviderC
onfiguringtheserviceprovider

>
> 3. For the mapping to happen the claim value resolved should always be the
> local username. Why not mapping can happen over another unique claim like
> email ?
> As I see, we can easily configure this for an ldap,  by configuring the
> 'UserNameSearchFilter' to search users over several attributes.
>
> Thanks,
> Malithi
> --
>
> *Malithi Edirisinghe*
> Associate Technical Lead
> WSO2 Inc.
>
> Mobile : +94 (0) 718176807
> malit...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Unit test for siddhi-io-jms

2017-10-23 Thread Sriskandarajah Suhothayan 
First, there should be a way of sending byte[] via JMS broker.
Then we can use the binary mapper to convert Siddhi events to byte[] and
send that to JMS broker via JMSPublisher.java.

Please let me know if this did not work.

On Tue, Oct 24, 2017 at 10:58 AM, Kalaiyarasi Ganeshalingam <
kalaiyar...@wso2.com> wrote:

> Hi all,
>  Currently I'm working on the unit testing for siddhi-io-jms.In the
> handleCarbonMessage(Object payload)[1] method, I tried to write the test
> case for payload instanceof Byte[] [2] condition.Can you give an idea to
> solve this issue?
> [1] https://github.com/wso2-extensions/siddhi-io-
> jms/blob/master/component/src/main/java/org/wso2/extension/
> siddhi/io/jms/sink/JMSPublisher.java#L65
> [2] https://github.com/wso2-extensions/siddhi-io-jms/blob/
> master/component/src/main/java/org/wso2/extension/siddhi/io/jms/sink/
> JMSPublisher.java#L76
>
> Regards,
> Kalaiyarasi Ganeshalingam
> Associate Software Engineer| WSO2
> WSO2 Inc : http://wso2.org
> 
> Tel:+94 076 6792895 <076%20679%202895>
> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
> Blogs : https://kalaiyarasig.blogspot.com/ 
>



-- 

*S. Suhothayan*
Associate Director / Architect
*WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Unit test for siddhi-io-jms

2017-10-23 Thread Kalaiyarasi Ganeshalingam 
Hi all,
 Currently I'm working on the unit testing for siddhi-io-jms.In the
handleCarbonMessage(Object payload)[1] method, I tried to write the test
case for payload instanceof Byte[] [2] condition.Can you give an idea to
solve this issue?
[1] https://github.com/wso2-extensions/siddhi-io-
jms/blob/master/component/src/main/java/org/wso2/extension/siddhi/io/jms/sink/JMSPublisher.java#L65
[2]
https://github.com/wso2-extensions/siddhi-io-jms/blob/master/component/src/main/java/org/wso2/extension/siddhi/io/jms/sink/JMSPublisher.java#L76

Regards,
Kalaiyarasi Ganeshalingam
Associate Software Engineer| WSO2
WSO2 Inc : http://wso2.org

Tel:+94 076 6792895
LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
Blogs : https://kalaiyarasig.blogspot.com/ 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How can I reset secret key of a federated identity when using TOTP

2017-10-23 Thread Kanapriya Kuleswararajan 
Hi Malithi,

If you wanted to re-scan the QR code then you have to deselect the Enable
TOTP claim in the dashboard, this will automatically remove the secret key
claim from the user profile.
BTW, for both local user and federated user this will work once you
de-select the Enable TOTP claim from the dashboard. Because for the
federated scenario, based on the use-cases have to create the user in the
local user store. If you are not setting any use case, then default (local)
use-case will get involved in the federation scenario. Please refer the
documentation [1] for more info.

[1]
https://docs.wso2.com/display/ISCONNECTORS/Configuring+TOTP+Authenticator

Thanks


Kanapriya Kuleswararajan
Software Engineer | WSO2
Mobile : - 0774894438
Mail : - kanapr...@wso2.com
LinkedIn : - https://www.linkedin.com/in/kanapriya-kules-94712685/


On Mon, Oct 23, 2017 at 11:51 PM, Malithi Edirisinghe 
wrote:

> Hi Team,
>
> I configured two step authentication with google federated authentication
> and TOTP for a service provider; i.e, first step is configured to use
> google as federated IdP, second step is TOTP.
> Both 'authenticationMandatory' and 'enrolUserInAuthenticationFlow' is set
> to true in TOTP authenticator configuration in
> application-authentication.xml file, such that TOTP is enforced and can
> enrol user while login.
>
> Now, when trying to access the SP, Google login page popped up for which
> user credentials were provided and authenticated. Then, in the next step,
> TOTP propose to enrol the user by scanning the QR code which was done. The
> federated user logged in successfully.
>
> Now, suppose I want to refresh the secret key of this account or clear it,
> such that the user needs to scan the QR code again. This could be done for
> a local user as the secret key was stored under 'http://wso2.org/claims/
> identity/secretkey' claim. But, for the user federated over google this
> could not be done. And I'm not sure where do we store the secret key for
> this account.
>
> Appreciate your input.
>
> Thanks,
> Malithi.
>
> --
>
> *Malithi Edirisinghe*
> Associate Technical Lead
> WSO2 Inc.
>
> Mobile : +94 (0) 718176807
> malit...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2-APIM Analytics Can we export raw data to excel or csv?

2017-10-23 Thread Sanjeewa Malalgoda 
Hi Vanji,
We dont have this capability of exporting them directly to CSVs. But we
have exported analytics tables to csv file with mysql command and generated
graphs etc when we do issue analysis. Following is one sample command.

SELECT * FROM IDN_OAUTH2_ACCESS_TOKEN_BAK INTO OUTFILE
'/var/lib/mysql-files/orders.csv' FIELDS TERMINATED BY ',' ENCLOSED BY '"'
LINES TERMINATED BY '\n';

If need we can automate this process and upload csvs to some file location
and analyze.

Thanks,
sanjeewa.

On Tue, Oct 24, 2017 at 5:52 AM, Vanjikumaran Sivajothy 
wrote:

> Hi team,
>
> In WSO2 APIM Analytics, is it possible to export the analytics data into
> CSV/Excel for given stats?
>
> Example
> Fetch API latency statistics into CVS file.
>
> Best regards,
> Vanji
>



-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

blog
:http://sanjeewamalalgoda.blogspot.com/

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

Re: [Dev] Signal to API Fault Summery Data in APIM Analytics

2017-10-23 Thread Tharindu Dharmarathna 
Hi Vanji,

Please see my comments inline.

On Tue, Oct 24, 2017 at 5:36 AM, Vanjikumaran Sivajothy 
wrote:

> Hi team,
>
> What are the positive signals that send to API Fault Summary Data from
> below fault occurrences?
>
> 1) Fault Happen in GW
>
This event tracked from fault events.

> 2) Failure response from Backend(4XX/5XX HTTP Error Code)
>
If Backend is sending this leads to the out sequence hand make that request
as response event.

> 3) Explicit Fault generation within GW
>
This event tracked from fault events.

>

>
> Best Regards,
> Vanji
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Tharindu Dharmarathna*Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] Warning log in server startup regarding the secondary userstore

2017-10-23 Thread Denuwanthi De Silva 
Hi Isura,

I don't have the specific file with me now as this was reported around
month ago.
But I directly used the UI as shown the screen shot to add the userstore.
And the userstore is a JDBC userstore on ORACLE.
Thanks,

On Mon, Oct 23, 2017 at 11:07 PM, Isura Karunaratne  wrote:

> Hi Denuwanthi,
>
> I tried to reproduce the issue [1], but I couldn't. Please upload the
> user-store config file used to create the secondary user store for further
> analysis?
>
>
> [1] https://wso2.org/jira/browse/IDENTITY-6449
>
> --
>
> *Isura Dilhara Karunaratne*
> Associate Technical Lead | WSO2
> Email: is...@wso2.com
> Mob : +94 772 254 810 <+94%2077%20225%204810>
> Blog : http://isurad.blogspot.com/
>
>
>
>


-- 
Denuwanthi De Silva
Senior Software Engineer;
WSO2 Inc.; http://wso2.com,
Email: denuwan...@wso2.com
Blog: https://denuwanthi.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Account association with 'userAttribute' usecase in SMSOTP and TOTP

2017-10-23 Thread Malithi Edirisinghe 
Hi All,

I was using $subject to associate federated identity over google and
facebook to the local user while configuring SMSOTP and TOTP as the second
factor authentication mechanism.

As I noted, for this to work I had to configure the federated claim, as the
userAttribute in the authenticator configuration, from which the respective
local user will be mapped.
Ex:
Added below in Google and Facebook case
email

1. The first question is what will happen when multi-option authentication
is configured as the first step?
I tried with Google and Facebook configured as muti-option in the first
step while having 'email' configured as the 'userAttribute'. That worked
because in both, there is a federated claim as 'email'. But, what if some
other authenticator is configured which will not have 'email' claim and
mail address of the user is received over a different claim format ?
As I see, the local claim (wso2 claim) should be configured in the
authenticator configuration and during the authentication flow, local claim
configured in the authenticator config should be picked, and the claim
value should be resolved after transforming federated claims received to
local dialect (wso2 dialect).

2. Noted, that in each authenticator an additional parameter needs to be
configured to denote 'userAttribute' mapping. Is this how (1) above is
achieved ?
However, the respective configurations in SMSOTP and TOTP with this regard
are not consistent. Moreover, I feel transforming back to the local dialect
and using that to retrieve the attribute to be mapped is the way to do.
With that this becomes a redundant config.

3. For the mapping to happen the claim value resolved should always be the
local username. Why not mapping can happen over another unique claim like
email ?
As I see, we can easily configure this for an ldap,  by configuring the
'UserNameSearchFilter' to search users over several attributes.

Thanks,
Malithi
-- 

*Malithi Edirisinghe*
Associate Technical Lead
WSO2 Inc.

Mobile : +94 (0) 718176807
malit...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2-APIM Analytics Can we export raw data to excel or csv?

2017-10-23 Thread Vanjikumaran Sivajothy 
Hi team,

In WSO2 APIM Analytics, is it possible to export the analytics data into
CSV/Excel for given stats?

Example
Fetch API latency statistics into CVS file.

Best regards,
Vanji
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Signal to API Fault Summery Data in APIM Analytics

2017-10-23 Thread Vanjikumaran Sivajothy 
Hi team,

What are the positive signals that send to API Fault Summary Data from
below fault occurrences?

1) Fault Happen in GW
2) Failure response from Backend(4XX/5XX HTTP Error Code)
3) Explicit Fault generation within GW

Best Regards,
Vanji
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Can we use placeholders for host name and port in IS connector configurations

2017-10-23 Thread Malithi Edirisinghe 
Hi Team,

I noted that we need to specifically configure server hostname and port
while configuring some IS connectors like SMSOTP and TOTP. Can't we use
placeholders instead?

Meanwhile *@IAMTeam*, if we are shipping connectors OOTB, I think we need
to have updated configs as well. Both, SMSOTP and TOTP are shipped with the
product but respective connector configurations are either outdated or not
to be found at all.

Thanks,
Malithi.

-- 

*Malithi Edirisinghe*
Associate Technical Lead
WSO2 Inc.

Mobile : +94 (0) 718176807
malit...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] How can I reset secret key of a federated identity when using TOTP

2017-10-23 Thread Malithi Edirisinghe 
Hi Team,

I configured two step authentication with google federated authentication
and TOTP for a service provider; i.e, first step is configured to use
google as federated IdP, second step is TOTP.
Both 'authenticationMandatory' and 'enrolUserInAuthenticationFlow' is set
to true in TOTP authenticator configuration in
application-authentication.xml file, such that TOTP is enforced and can
enrol user while login.

Now, when trying to access the SP, Google login page popped up for which
user credentials were provided and authenticated. Then, in the next step,
TOTP propose to enrol the user by scanning the QR code which was done. The
federated user logged in successfully.

Now, suppose I want to refresh the secret key of this account or clear it,
such that the user needs to scan the QR code again. This could be done for
a local user as the secret key was stored under '
http://wso2.org/claims/identity/secretkey' claim. But, for the user
federated over google this could not be done. And I'm not sure where do we
store the secret key for this account.

Appreciate your input.

Thanks,
Malithi.

-- 

*Malithi Edirisinghe*
Associate Technical Lead
WSO2 Inc.

Mobile : +94 (0) 718176807
malit...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Warning log in server startup regarding the secondary userstore

2017-10-23 Thread Isura Karunaratne 
Hi Denuwanthi,

I tried to reproduce the issue [1], but I couldn't. Please upload the
user-store config file used to create the secondary user store for further
analysis?


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

-- 

*Isura Dilhara Karunaratne*
Associate Technical Lead | WSO2
Email: is...@wso2.com
Mob : +94 772 254 810
Blog : http://isurad.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Removing duplicate implementation from new release rather than depreciating it.

2017-10-23 Thread Harsha Thirimanna 
On Mon, Oct 23, 2017 at 5:24 PM, Darshana Gunawardana 
wrote:

> Hi Harsha,
>
> If the endpoint definition, or internal SPIs going to be changed, we have
> to deprecate the existing implementation as the general rule.
>
> But in this case, we still have the same functionality exposed with
> different underlying implementation and this really don't have any SPIs
> associated with. So i'm +1 to remove the older implementation that we had
> in IS 5.3.0 and have only the new implementation with IS 5.4.0.
>

​Thanks Darshana/Sagara.

We will track this in [1] to remove this from next release.

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



>
> Thanks,
>
> On Mon, Oct 23, 2017 at 4:48 PM, Harsha Thirimanna 
> wrote:
>
>>
>> On Mon, Oct 23, 2017 at 4:42 PM, Sagara Gunathunga 
>> wrote:
>>
>>>
>>>
>>> On Mon, Oct 23, 2017 at 4:36 PM, Harsha Thirimanna 
>>> wrote:
>>>
 Hi Dev,

 Since we have new DCR/DCRM endpoint with new CXF implementation, shall
 we remove the old endpoint and impl from the new release rather than
 depreciating it and update the migration documentation based on that ?

 Because we are doing the unit testing improvement on top of all the
 component and we don't need to duplicate the effort like these duplicate
 implementation.

 WDYT ?

>>>
>>> In general there is no point to ship same endpoint/feature two times but
>>> is there any impact  on removing old endpoint ?
>>>
>>
>> ​Hi Sagara,​
>>
>> ​Yes, you are correct and it may be give some more issues if we don't fix
>> some issues in both places in next release.​
>>
>> We must update the information in migration guide and there are no any
>> other problems as I know the context.
>>
>>
>> J
>> ​ohan/Ishara/NuwanD can give more information around this.
>> ​
>>
>>>
>>> Thanks !
>>>

 *Harsha Thirimanna*
 *Associate Tech Lead | WSO2*

 Email: hars...@wso2.com
 Mob: +94715186770 <+94%2071%20518%206770>
 Blog: http://harshathirimanna.blogspot.com/
 Twitter: http://twitter.com/harshathirimann
 Linked-In: linked-in: http://www.linkedin.com/pub/ha
 rsha-thirimanna/10/ab8/122
 

>>>
>>>
>>>
>>> --
>>> Sagara Gunathunga
>>>
>>> Director; WSO2, Inc.;  http://wso2.com
>>> V.P Apache Web Services;http://ws.apache.org/
>>> Linkedin; http://www.linkedin.com/in/ssagara
>>> Blog ;  http://ssagara.blogspot.com
>>> Mobile : +9471 <+94%2071%20565%209887>2149951
>>>
>>>
>>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Technical Lead
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <+94%2071%20856%206859>*Lean . Enterprise .
> Middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Removing duplicate implementation from new release rather than depreciating it.

2017-10-23 Thread Darshana Gunawardana 
Hi Harsha,

If the endpoint definition, or internal SPIs going to be changed, we have
to deprecate the existing implementation as the general rule.

But in this case, we still have the same functionality exposed with
different underlying implementation and this really don't have any SPIs
associated with. So i'm +1 to remove the older implementation that we had
in IS 5.3.0 and have only the new implementation with IS 5.4.0.

Thanks,

On Mon, Oct 23, 2017 at 4:48 PM, Harsha Thirimanna  wrote:

>
> On Mon, Oct 23, 2017 at 4:42 PM, Sagara Gunathunga 
> wrote:
>
>>
>>
>> On Mon, Oct 23, 2017 at 4:36 PM, Harsha Thirimanna 
>> wrote:
>>
>>> Hi Dev,
>>>
>>> Since we have new DCR/DCRM endpoint with new CXF implementation, shall
>>> we remove the old endpoint and impl from the new release rather than
>>> depreciating it and update the migration documentation based on that ?
>>>
>>> Because we are doing the unit testing improvement on top of all the
>>> component and we don't need to duplicate the effort like these duplicate
>>> implementation.
>>>
>>> WDYT ?
>>>
>>
>> In general there is no point to ship same endpoint/feature two times but
>> is there any impact  on removing old endpoint ?
>>
>
> ​Hi Sagara,​
>
> ​Yes, you are correct and it may be give some more issues if we don't fix
> some issues in both places in next release.​
>
> We must update the information in migration guide and there are no any
> other problems as I know the context.
>
>
> J
> ​ohan/Ishara/NuwanD can give more information around this.
> ​
>
>>
>> Thanks !
>>
>>>
>>> *Harsha Thirimanna*
>>> *Associate Tech Lead | WSO2*
>>>
>>> Email: hars...@wso2.com
>>> Mob: +94715186770 <+94%2071%20518%206770>
>>> Blog: http://harshathirimanna.blogspot.com/
>>> Twitter: http://twitter.com/harshathirimann
>>> Linked-In: linked-in: http://www.linkedin.com/pub/ha
>>> rsha-thirimanna/10/ab8/122
>>> 
>>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Director; WSO2, Inc.;  http://wso2.com
>> V.P Apache Web Services;http://ws.apache.org/
>> Linkedin; http://www.linkedin.com/in/ssagara
>> Blog ;  http://ssagara.blogspot.com
>> Mobile : +9471 <+94%2071%20565%209887>2149951
>>
>>
>


-- 
Regards,


*Darshana Gunawardana*Technical Lead
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Removing duplicate implementation from new release rather than depreciating it.

2017-10-23 Thread Harsha Thirimanna 
On Mon, Oct 23, 2017 at 4:42 PM, Sagara Gunathunga  wrote:

>
>
> On Mon, Oct 23, 2017 at 4:36 PM, Harsha Thirimanna 
> wrote:
>
>> Hi Dev,
>>
>> Since we have new DCR/DCRM endpoint with new CXF implementation, shall we
>> remove the old endpoint and impl from the new release rather than
>> depreciating it and update the migration documentation based on that ?
>>
>> Because we are doing the unit testing improvement on top of all the
>> component and we don't need to duplicate the effort like these duplicate
>> implementation.
>>
>> WDYT ?
>>
>
> In general there is no point to ship same endpoint/feature two times but
> is there any impact  on removing old endpoint ?
>

​Hi Sagara,​

​Yes, you are correct and it may be give some more issues if we don't fix
some issues in both places in next release.​

We must update the information in migration guide and there are no any
other problems as I know the context.


J
​ohan/Ishara/NuwanD can give more information around this.
​

>
> Thanks !
>
>>
>> *Harsha Thirimanna*
>> *Associate Tech Lead | WSO2*
>>
>> Email: hars...@wso2.com
>> Mob: +94715186770 <+94%2071%20518%206770>
>> Blog: http://harshathirimanna.blogspot.com/
>> Twitter: http://twitter.com/harshathirimann
>> Linked-In: linked-in: http://www.linkedin.com/pub/ha
>> rsha-thirimanna/10/ab8/122
>> 
>>
>
>
>
> --
> Sagara Gunathunga
>
> Director; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
> Mobile : +9471 <+94%2071%20565%209887>2149951
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Removing duplicate implementation from new release rather than depreciating it.

2017-10-23 Thread Sagara Gunathunga 
On Mon, Oct 23, 2017 at 4:36 PM, Harsha Thirimanna  wrote:

> Hi Dev,
>
> Since we have new DCR/DCRM endpoint with new CXF implementation, shall we
> remove the old endpoint and impl from the new release rather than
> depreciating it and update the migration documentation based on that ?
>
> Because we are doing the unit testing improvement on top of all the
> component and we don't need to duplicate the effort like these duplicate
> implementation.
>
> WDYT ?
>

In general there is no point to ship same endpoint/feature two times but is
there any impact  on removing old endpoint ?

Thanks !

>
> *Harsha Thirimanna*
> *Associate Tech Lead | WSO2*
>
> Email: hars...@wso2.com
> Mob: +94715186770 <+94%2071%20518%206770>
> Blog: http://harshathirimanna.blogspot.com/
> Twitter: http://twitter.com/harshathirimann
> Linked-In: linked-in: http://www.linkedin.com/pub/
> harsha-thirimanna/10/ab8/122
> 
>



-- 
Sagara Gunathunga

Director; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
Mobile : +9471 <+94%2071%20565%209887>2149951
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Removing duplicate implementation from new release rather than depreciating it.

2017-10-23 Thread Harsha Thirimanna 
Hi Dev,

Since we have new DCR/DCRM endpoint with new CXF implementation, shall we
remove the old endpoint and impl from the new release rather than
depreciating it and update the migration documentation based on that ?

Because we are doing the unit testing improvement on top of all the
component and we don't need to duplicate the effort like these duplicate
implementation.

WDYT ?

*Harsha Thirimanna*
*Associate Tech Lead | WSO2*

Email: hars...@wso2.com
Mob: +94715186770
Blog: http://harshathirimanna.blogspot.com/
Twitter: http://twitter.com/harshathirimann
Linked-In: linked-in:
http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122

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

Re: [Dev] Enable Response signing cannot be done through admin service when creating SAML2 Web SSO Configuraton for a Service Provider

2017-10-23 Thread Chamara Ariyarathne 
Updated the ticket!

On Mon, Oct 23, 2017 at 3:38 PM, Thanuja Jayasinghe 
wrote:

> Hi Chamara,
>
> SAML service provider UI uses the same admin service to add sp
> configurations. So theoretically this should work.
>
> So can you please attach the SOAP request used to create the SAML2 service
> provider?
>
> Thanks,
> Thanuja
>
> On Sun, Oct 22, 2017 at 10:19 PM, Chamara Ariyarathne 
> wrote:
>
>> Of course, the test was done with a WUM updated pack
>>
>> On Sun, Oct 22, 2017 at 10:17 PM, Hasintha Indrajee 
>> wrote:
>>
>>> Did you observe this in a WUM updated pack ? If not can you please try
>>> with a WUM updated pack as well ?
>>>
>>> On Sat, Oct 21, 2017 at 8:18 PM, Chamara Ariyarathne 
>>> wrote:
>>>


 On Sat, Oct 21, 2017 at 7:03 PM, Farasath Ahamed 
 wrote:

> I suspect a caching issue here.
> Was this a single node setup or a multi node cluster?
>

 Reproduced in Single node.

>
> Also when you try out next time. Can you simply view the SP config and
> click the update button (without ticking and unticking) and see it it 
> works?
>

 Sure.

>
>
> On Friday, October 20, 2017, Chamara Ariyarathne 
> wrote:
>
>> Hi all,
>>
>> I'm using the IdentitySAMLSSOConfigService admin service to do the
>> SAML2 Web SSO Configuration and later using 
>> IdentityApplicationManagementService
>> admin service to add it to a service provider configuration.
>>
>> I am using this tag to Enable Response Signing.
>> true
>>
>> However when later checked with the travelocity webapp and the log
>> in fails. When I checked the SP configuration, I can see the checkbox is
>> ticked for Enable Response Signing in the UI.
>>
>> If I untick and tick again the checkbox and update the SP, then the
>> scenario passes. What that means is, the admin service cannot be used to
>> make the Enable Response Signing.
>>
>> This needs a fix.
>>
>> https://wso2.org/jira/browse/IDENTITY-6796
>>
>> --
>> *Chamara Ariyarathne*
>> WSO2 Inc; http://www.wso2.com/
>> Mobile; *+94772786766 <077%20278%206766>*
>>
>
>
> --
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
> 
>
>
>
>


 --
 *Chamara Ariyarathne*
 WSO2 Inc; http://www.wso2.com/
 Mobile; *+94772786766 <077%20278%206766>*

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


>>>
>>>
>>> --
>>> Hasintha Indrajee
>>> WSO2, Inc.
>>> Mobile:+94 771892453 <077%20189%202453>
>>>
>>>
>>
>>
>> --
>> *Chamara Ariyarathne*
>> WSO2 Inc; http://www.wso2.com/
>> Mobile; *+94772786766 <+94%2077%20278%206766>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Thanuja Lakmal*
> Associate Technical Lead
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94715979891
>



-- 
*Chamara Ariyarathne*
WSO2 Inc; http://www.wso2.com/
Mobile; *+94772786766*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] In a ESB sequence, how to continue process in case of error

2017-10-23 Thread Thomas LEGRAND 
Hello,

I have an inbound endpoint calling a sequence once triggered. In this
sequence, I call a REST API which can return a 404 causing the whole
sequence and subsequences to stop. But the return of the API is useful and
I would like to continue the process with it even if it is a 404.

Have you any idea how I can achieve that ?

Regards,

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

Re: [Dev] Enable Response signing cannot be done through admin service when creating SAML2 Web SSO Configuraton for a Service Provider

2017-10-23 Thread Thanuja Jayasinghe 
Hi Chamara,

SAML service provider UI uses the same admin service to add sp
configurations. So theoretically this should work.

So can you please attach the SOAP request used to create the SAML2 service
provider?

Thanks,
Thanuja

On Sun, Oct 22, 2017 at 10:19 PM, Chamara Ariyarathne 
wrote:

> Of course, the test was done with a WUM updated pack
>
> On Sun, Oct 22, 2017 at 10:17 PM, Hasintha Indrajee 
> wrote:
>
>> Did you observe this in a WUM updated pack ? If not can you please try
>> with a WUM updated pack as well ?
>>
>> On Sat, Oct 21, 2017 at 8:18 PM, Chamara Ariyarathne 
>> wrote:
>>
>>>
>>>
>>> On Sat, Oct 21, 2017 at 7:03 PM, Farasath Ahamed 
>>> wrote:
>>>
 I suspect a caching issue here.
 Was this a single node setup or a multi node cluster?

>>>
>>> Reproduced in Single node.
>>>

 Also when you try out next time. Can you simply view the SP config and
 click the update button (without ticking and unticking) and see it it 
 works?

>>>
>>> Sure.
>>>


 On Friday, October 20, 2017, Chamara Ariyarathne 
 wrote:

> Hi all,
>
> I'm using the IdentitySAMLSSOConfigService admin service to do the
> SAML2 Web SSO Configuration and later using 
> IdentityApplicationManagementService
> admin service to add it to a service provider configuration.
>
> I am using this tag to Enable Response Signing.
> true
>
> However when later checked with the travelocity webapp and the log
> in fails. When I checked the SP configuration, I can see the checkbox is
> ticked for Enable Response Signing in the UI.
>
> If I untick and tick again the checkbox and update the SP, then the
> scenario passes. What that means is, the admin service cannot be used to
> make the Enable Response Signing.
>
> This needs a fix.
>
> https://wso2.org/jira/browse/IDENTITY-6796
>
> --
> *Chamara Ariyarathne*
> WSO2 Inc; http://www.wso2.com/
> Mobile; *+94772786766 <077%20278%206766>*
>


 --
 Farasath Ahamed
 Software Engineer, WSO2 Inc.; http://wso2.com
 Mobile: +94777603866
 Blog: blog.farazath.com
 Twitter: @farazath619 
 




>>>
>>>
>>> --
>>> *Chamara Ariyarathne*
>>> WSO2 Inc; http://www.wso2.com/
>>> Mobile; *+94772786766 <077%20278%206766>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Hasintha Indrajee
>> WSO2, Inc.
>> Mobile:+94 771892453 <077%20189%202453>
>>
>>
>
>
> --
> *Chamara Ariyarathne*
> WSO2 Inc; http://www.wso2.com/
> Mobile; *+94772786766 <+94%2077%20278%206766>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Thanuja Lakmal*
Associate Technical Lead
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94715979891
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Enterprise Integrator 6.1.1-update7 Released!

2017-10-23 Thread Heshitha Hettihewa 
Hi all,

Please find the documentation link for the latest release below. Sorry for
the inconvenience occurred.

Documentation

https://docs.wso2.com/display/EI611/

Thanks.

On Sat, Oct 21, 2017 at 3:27 AM, Heshitha Hettihewa 
wrote:

> Hi all,
>
> The WSO2 Integration team is pleased to announce the release of Enterprise
> Integrator 6.1.1-update7. It is available for download from here
> .
>
> Tasks/Bug Fixes and Improvements
>
> https://wso2.org/jira/issues?filter=14270
>
> https://github.com/wso2/product-ei/issues?&q=is%
> 3Aissue%20milestone%3A6.1.1-update7%20is%3Aclosed
>
> ​​List of Open Issues
>
> https://wso2.org/jira/issues/?filter=13994
>
> https://github.com/wso2/product-ei/issues?q=is%3Aopen+is%3Aissue
>
> Mailing Lists
>
> Join our mailing lists and correspond with the developers directly.
>
> Developer List : dev@wso2.org | Subscribe | Mail Archive
>
> WSO2 Architecture List: architect...@wso2.org
>
> User Forum : StackOverflow
>
> How To Contribute
>
> Your feedback is most welcome!
>
> Reporting Issues​
>
> We encourage you to report issues, improvements and feature requests
> regarding WSO2 Integrator through WSO2 EI GIT Issues.
>
> ~ The WSO2 Integration Team ~
> --
> Heshitha Hettihewa
> *Software Engineer*
> Mobile : +94716866386
> <%2B94%20%280%29%20773%20451194>
> heshit...@wso2.com
>



-- 
Heshitha Hettihewa
*Software Engineer*
Mobile : +94716866386
<%2B94%20%280%29%20773%20451194>
heshit...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev