Re: [Dev] [VOTE] Release WSO2 MSF4J 2.1.1 RC1

[Nuwan Dias]

[x] Stable - go ahead and release.

Thanks,
NuwanD.

On Wed, Feb 8, 2017 at 8:55 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Devs,
>
> This is the 1st Release Candidate of WSO2 MSF4J(Microservices Framework
> for Java) 2.1.1.
>
> Please download, test the framework and vote. The vote will be open for
> 72 hours or as needed.
> Refer to GitHub readmes for guides.
>
> *Source and binary distribution files:*
> https://github.com/wso2/msf4j/releases/tag/v2.1.1-rc1
>
> *Maven staging repository:*
> https://maven.wso2.org/nexus/content/repositories/orgwso2msf4j-1012
>
> *The tag to be voted upon:*
> https://github.com/wso2/msf4j/tree/v2.1.1-rc1
>
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you,
> Platform Team
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809 <+94%2071%20275%206809>
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Dias

Software Architect - 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] [VOTE] Release WSO2 MSF4J 2.1.1 RC1

[Abimaran Kugathasan]

Tested with API Manager 3.0-SNAPSHOT, haven't encountered any issues.

[+] Stable - go ahead and release

On Mon, Feb 13, 2017 at 12:04 PM, Fazlan Nazeem  wrote:

> Tested with API Manager.
>
> We did not encounter [1]
>
> [+] Stable - go ahead and release
>
> [1] - https://github.com/wso2/msf4j/issues/329
>
> On Mon, Feb 13, 2017 at 11:50 AM, Tharindu Dharmarathna <
> tharin...@wso2.com> wrote:
>
>> Tested with API Manager.
>>
>> We did not encounter [1]
>>
>> [+] Stable - go ahead and release
>>
>> [1] - https://github.com/wso2/msf4j/issues/329
>>
>> On Thu, Feb 9, 2017 at 5:55 PM, Thilini Shanika 
>> wrote:
>>
>>> Tested with API Manager.
>>>
>>> We did not encounter [1]
>>>
>>> [+] Stable - go ahead and release
>>>
>>> [1] https://github.com/wso2/msf4j/issues/337
>>>
>>>
>>> On Wed, Feb 8, 2017 at 8:55 PM, Thusitha Thilina Dayaratne <
>>> thusit...@wso2.com> wrote:
>>>
 Hi Devs,

 This is the 1st Release Candidate of WSO2 MSF4J(Microservices
 Framework for Java) 2.1.1.

 Please download, test the framework and vote. The vote will be open
 for 72 hours or as needed.
 Refer to GitHub readmes for guides.

 *Source and binary distribution files:*
 https://github.com/wso2/msf4j/releases/tag/v2.1.1-rc1

 *Maven staging repository:*
 https://maven.wso2.org/nexus/content/repositories/orgwso2msf4j-1012

 *The tag to be voted upon:*
 https://github.com/wso2/msf4j/tree/v2.1.1-rc1



 [ ] Broken - do not release (explain why)
 [ ] Stable - go ahead and release

 Thank you,
 Platform Team
 --
 Thusitha Dayaratne
 Software Engineer
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com

 Mobile  +94712756809 <+94%2071%20275%206809>
 Blog  alokayasoya.blogspot.com
 Abouthttp://about.me/thusithathilina
 


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


>>>
>>>
>>> --
>>> Thilini Shanika
>>> Senior Software Engineer
>>> WSO2, Inc.; http://wso2.com
>>> 20, Palmgrove Avenue, Colombo 3
>>>
>>> E-mail: tgtshan...@gmail.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Tharindu Dharmarathna*Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091 <+94%2077%20910%209091>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> Fazlan Nazeem
>
> *Software Engineer*
>
> *WSO2 Inc*
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer - API Technologies

Email : abima...@wso2.com
Mobile : +94 773922820


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

Re: [Dev] Repos for Puppet Modules, Dockerfiles, and K8S Artifacts

[Imesh Gunaratne]

Thanks for bringing this up Chamila!

Yes, as Lakmal has pointed out until we release product wise repositories
marking above repositories as obsolete might not be correct.

Thanks

On Tue, Feb 14, 2017 at 8:22 AM, Lakmal Warusawithana 
wrote:

> +1. Before that we need to review current product wise releases. I have
> notice product wise puppet releases does not have full user guide (starting
> from puppet install etc).
>
> On Tue, Feb 14, 2017 at 8:12 AM, Chamila De Alwis 
> wrote:
>
>> Hi,
>>
>> Shall we mark the older repositories for the above [1][2][3] as obsolete
>> since they are now distributed among the product teams? There are pull
>> requests being opened and issues being created for them that should be done
>> at either the product specific repositories or each *-common repository.
>>
>> We shouldn't remove them yet, IMO, since there haven't been any product
>> stack wide release for any of the above artifacts. AFAIK only IS and APIM
>> has release product specific Puppet modules. Once a release is done for
>> every product, we could remove the older repositories however for now, we
>> should mark them as obsolete and direct to proper new repositories for any
>> new user to discover and interact with the new code.
>>
>> [1] - https://github.com/wso2/puppet-modules
>> [2] - https://github.com/wso2/dockerfiles
>> [3] - https://github.com/wso2/kubernetes-artifacts
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Senior Software Engineer | WSO2
>> Blog: https://medium.com/@chamilad
>>
>>
>>
>
>
> --
> Lakmal Warusawithana
> Director - Cloud Architecture; WSO2 Inc.
> Mobile : +94714289692 <+94%2071%20428%209692>
> Blog : http://lakmalsview.blogspot.com/
>
>


-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017

[Tishan Dahanayakage]

Adding again

On Tue, Feb 14, 2017 at 10:38 AM, Tishan Dahanayakage 
wrote:

> Hi Irene,
>
> Thanks for your interest in WSO2 and this project. I am adding possible
> project mentors here so that you can get more information.
>
> Thanks
> /Tishan
>
> On Tue, Feb 7, 2017 at 10:34 PM, irene tenison 
> wrote:
>
>> I would like to contribute to WSO2 on video scene detection project for
>> GSoC 2017.Please do help me and guide me with the project. About myself ..
>> I'm Irene from India and I'm quite interested in video editing and colour
>> grading works and so I think this project would be  most appropriately
>> handled by me.I would be so thankful if you can provide more information
>> about what you are trying to implement.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Tishan Dahanayakage
> Senior Software Engineer
> WSO2, Inc.
> Mobile:+94 716481328 <+94%2071%20648%201328>
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, re-transmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>



-- 
Tishan Dahanayakage
Senior Software Engineer
WSO2, Inc.
Mobile:+94 716481328

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
re-transmit, disseminate, or otherwise use the information contained in
this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [UUF] UUF-Client renderFragment fails with warning "Content is empty."

[Kasun Thennakoon]

Hi all,

Experience the $subject when using UUF-Client for rendering hbs fragments.
As I understand, the response of
*http://localhost:9090/publisher/fragments/{fragment-name}
 *contains an
HTML string and in this line[1] it is looking for *.html* attribute in the
response object when calling *pushContent* method. Which pass an *undefined
*value.IMHO this is what cause to display no content in the target zone.


[1]:
https://github.com/wso2/carbon-uuf-common/blob/master/components/org.wso2.carbon.uuf.common.foundation.ui/src/main/fragments/uuf-client/public/uuf-client/uuf-client.js#L226

-- 
*Kasun Thennakoon*
Software Engineer
WSO2, Inc.
Mobile:+94 711661919
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017

[Tishan Dahanayakage]

Hi Irene,

Thanks for your interest in WSO2 and this project. I am adding possible
project mentors here so that you can get more information.

Thanks
/Tishan

On Tue, Feb 7, 2017 at 10:34 PM, irene tenison 
wrote:

> I would like to contribute to WSO2 on video scene detection project for
> GSoC 2017.Please do help me and guide me with the project. About myself ..
> I'm Irene from India and I'm quite interested in video editing and colour
> grading works and so I think this project would be  most appropriately
> handled by me.I would be so thankful if you can provide more information
> about what you are trying to implement.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Tishan Dahanayakage
Senior Software Engineer
WSO2, Inc.
Mobile:+94 716481328

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
re-transmit, disseminate, or otherwise use the information contained in
this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] C5 Support for filtering

[Darshana Gunawardana]

[Re adding Vindula]

On Tue, Feb 14, 2017 at 10:31 AM, Darshana Gunawardana 
wrote:

> Hi all,
>
> Have we made any progress on this? Assuming that we are not covered these,
> i have created few JIRAs to track these.. Please resolve them, if those are
> already implemented or add any JIRA that needed to be added more.
>
> https://wso2.org/jira/browse/IDENTITY-5748 : "Add support for complex
> filters for user core and expose the same from product (SCIM) API"
> https://wso2.org/jira/browse/IDENTITY-5749 : "Add support for pagination
> for user core and expose the same from product (SCIM) API"
> https://wso2.org/jira/browse/IDENTITY-5750 : "Add support for sorting for
> user core and expose the same from product (SCIM) API"
> https://wso2.org/jira/browse/IDENTITY-5751 : "Add support for
> filtering\sorting\pagination together for user core and expose the same
> from product (SCIM) API"
>
> Thanks,
>
>
> On Fri, Nov 4, 2016 at 2:25 PM, Johann Nallathamby 
> wrote:
>
>> We need to support simple filters, pagination and sorting from user-core
>> APIs. I don't think there is a defined list of complex filters; it is
>> endless. So we can't support it from user-core. So what we can do is we can
>> provide a default implementation to evaluate complex filters using simple
>> filters in SCIMUserManager, and if someone wants to extend it they need to
>> extend SCIMUserManager implementation.
>>
>> On Fri, Nov 4, 2016 at 1:15 PM, Darshana Gunawardana 
>> wrote:
>>
>>> Hi,
>>>
>>> Do we have the support for complex filters, pagination, sorting from the
>>> C5 user-core?
>>>
>>> If not, we should support these since these are some major limitations
>>> we had in C4 user-core and we should avoid those limitations in C5.
>>>
>>> Thanks,
>>>
>>> On Thu, Oct 20, 2016 at 9:41 AM, Vindula Jayawardana 
>>> wrote:
>>>
 Hi Chamila,

 On Tue, Oct 18, 2016 at 4:18 PM, Chamila Wijayarathna <
 cdwijayarat...@gmail.com> wrote:

> Hi Johann, Vindula,
>
> On Tue, Oct 18, 2016 at 3:59 PM, Johann Nallathamby 
> wrote:
>
>>
>>
>> On Tue, Oct 18, 2016 at 10:05 AM, Vindula Jayawardana <
>> vind...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> With the current user core implementation we support only the equal
>>> filter (e.g. userName Eq "john"). However SCIM 2.0 specification [1]
>>> specify total of 10 such simple filters and complex filters which are
>>> combinations of simple filters using logical and grouping operators 
>>> (e.g.
>>> userType ne "Employee" and not (emails co "example.com" or
>>> emails.value co "example.org")). As we are in the process of C5
>>> implementation, have we considered the other filter type 
>>> implementations as
>>> well?
>>>
>>
>> Yes we need to consider these features in the extended user-core
>> implementation.
>>
>>>
>>> Moreover if we are supporting the complex filters, are we supporting
>>> it by simple filter by filter basis or the entire complex filter as a
>>> whole? If we are looking for the simple filter by filter basis, there 
>>> will
>>> be performance issues as well.
>>>
>>
>> It is better if we provide complex filters from extended user-core
>> itself for performance reasons. However if time doesn't permit to 
>> implement
>> all those APIs, we can have a scim UserManager implementation which will
>> call multiple simple filters and combine the result and return. Obviously
>> as you said performance of such implementation will be low. But it is
>> acceptable as an interim solution until extended user-core implementation
>> supports all the filters.
>>
> Can you please explain, what you refer as complex filters here? I
> think we need to implement operators listed in table 3 and 4 in the
> specification and implement a generic way to build complex queries reusing
> them. I don't think it would be practical to more complex filters, there
> can be large amount of complex filters that can be created by combining
> these simple filter. Please correct me if I'm wrong.
>

 What I meant by complex filters is exactly what you have mentioned
 above. Yes we can build large amount of complex filters (complex queries)
 by combining the simple filters using operators listed in table 3 and 4.

>
> Also what different would it made when we are handling these filters
> in user-core level and when handling using scimUserManager level? Are you
> reffering to the fact that when we need "username sw a" , we can retrieve
> only  the users who have username start with 'a' from database/ldap, so
> that we can achieve higher performance?
>
> In addition to that, I believe it would be good to consider other SCIM
> operations such as sorting and pagination at 

Re: [Dev] [IS] C5 Support for filtering

[Darshana Gunawardana]

Hi all,

Have we made any progress on this? Assuming that we are not covered these,
i have created few JIRAs to track these.. Please resolve them, if those are
already implemented or add any JIRA that needed to be added more.

https://wso2.org/jira/browse/IDENTITY-5748 : "Add support for complex
filters for user core and expose the same from product (SCIM) API"
https://wso2.org/jira/browse/IDENTITY-5749 : "Add support for pagination
for user core and expose the same from product (SCIM) API"
https://wso2.org/jira/browse/IDENTITY-5750 : "Add support for sorting for
user core and expose the same from product (SCIM) API"
https://wso2.org/jira/browse/IDENTITY-5751 : "Add support for
filtering\sorting\pagination together for user core and expose the same
from product (SCIM) API"

Thanks,


On Fri, Nov 4, 2016 at 2:25 PM, Johann Nallathamby  wrote:

> We need to support simple filters, pagination and sorting from user-core
> APIs. I don't think there is a defined list of complex filters; it is
> endless. So we can't support it from user-core. So what we can do is we can
> provide a default implementation to evaluate complex filters using simple
> filters in SCIMUserManager, and if someone wants to extend it they need to
> extend SCIMUserManager implementation.
>
> On Fri, Nov 4, 2016 at 1:15 PM, Darshana Gunawardana 
> wrote:
>
>> Hi,
>>
>> Do we have the support for complex filters, pagination, sorting from the
>> C5 user-core?
>>
>> If not, we should support these since these are some major limitations we
>> had in C4 user-core and we should avoid those limitations in C5.
>>
>> Thanks,
>>
>> On Thu, Oct 20, 2016 at 9:41 AM, Vindula Jayawardana 
>> wrote:
>>
>>> Hi Chamila,
>>>
>>> On Tue, Oct 18, 2016 at 4:18 PM, Chamila Wijayarathna <
>>> cdwijayarat...@gmail.com> wrote:
>>>
 Hi Johann, Vindula,

 On Tue, Oct 18, 2016 at 3:59 PM, Johann Nallathamby 
 wrote:

>
>
> On Tue, Oct 18, 2016 at 10:05 AM, Vindula Jayawardana <
> vind...@wso2.com> wrote:
>
>> Hi All,
>>
>> With the current user core implementation we support only the equal
>> filter (e.g. userName Eq "john"). However SCIM 2.0 specification [1]
>> specify total of 10 such simple filters and complex filters which are
>> combinations of simple filters using logical and grouping operators (e.g.
>> userType ne "Employee" and not (emails co "example.com" or
>> emails.value co "example.org")). As we are in the process of C5
>> implementation, have we considered the other filter type implementations 
>> as
>> well?
>>
>
> Yes we need to consider these features in the extended user-core
> implementation.
>
>>
>> Moreover if we are supporting the complex filters, are we supporting
>> it by simple filter by filter basis or the entire complex filter as a
>> whole? If we are looking for the simple filter by filter basis, there 
>> will
>> be performance issues as well.
>>
>
> It is better if we provide complex filters from extended user-core
> itself for performance reasons. However if time doesn't permit to 
> implement
> all those APIs, we can have a scim UserManager implementation which will
> call multiple simple filters and combine the result and return. Obviously
> as you said performance of such implementation will be low. But it is
> acceptable as an interim solution until extended user-core implementation
> supports all the filters.
>
 Can you please explain, what you refer as complex filters here? I think
 we need to implement operators listed in table 3 and 4 in the specification
 and implement a generic way to build complex queries reusing them. I don't
 think it would be practical to more complex filters, there can be large
 amount of complex filters that can be created by combining these simple
 filter. Please correct me if I'm wrong.

>>>
>>> What I meant by complex filters is exactly what you have mentioned
>>> above. Yes we can build large amount of complex filters (complex queries)
>>> by combining the simple filters using operators listed in table 3 and 4.
>>>

 Also what different would it made when we are handling these filters in
 user-core level and when handling using scimUserManager level? Are you
 reffering to the fact that when we need "username sw a" , we can retrieve
 only  the users who have username start with 'a' from database/ldap, so
 that we can achieve higher performance?

 In addition to that, I believe it would be good to consider other SCIM
 operations such as sorting and pagination at the same time. If we can come
 up with a generic design, that would be better. Otherwise, we'll have to
 put a huge effort to embed those functionalities again.

>>>
>>> Yes agree. We need a generic design which will ease our work 

[Dev] MongoDB user store manager

[Pushpalanka Jayawardhana]

Hi Asantha/All,

Regarding the MongoDB user store manager implemented at [1], is there a
specific reason why it can not be used as the primary user store?

[1] - https://github.com/asanthamax/mongodbuserstore
[2] -
http://asanthamax.blogspot.com/2016/06/mongodb-user-store-development-for-wso2.html

Thanks,
-- 
Pushpalanka.
-- 
Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
Senior Software Engineer, WSO2 Lanka (pvt) Ltd;  wso2.com/
Mobile: +94779716248
Blog: pushpalankajaya.blogspot.com/ | LinkedIn:
lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarification about File Connector version 2

[Maduranga Siriwardena]

Hi Vivekananthan,

Created public jira [1].

[1] https://wso2.org/jira/browse/ESBCONNECT-186

On Wed, Feb 8, 2017 at 7:16 AM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Maduranga,
>
> We'll consider those behavior in the future release of the connector. Please
> create a Jira.
>
> @Malaka, Can you confirm it?
>
> Thanks,
> Vivek.
>
> Vivekananthan Sivanayagam
> Associate Software Engineer | WSO2
> E:vivekanant...@wso2.com
> M:+94752786138 <+94%2075%20278%206138>
>
> On Wed, Feb 8, 2017 at 6:05 PM, Maduranga Siriwardena 
> wrote:
>
>> Hi Vivekananthan,
>>
>> Comparing the linux file operations,
>>
>> *cp -r in/ out/*
>> "in" folder is copied to the "out" folder and "in" folder will be inside
>> the "out" folder.
>> *cp in/* out/*
>> contents of the "in" folder is copied to the "out" folder and there will
>> be no "in" folder inside the "out" folder. This is similar to copy
>> operation in the connector when the source is a folder.
>>
>> *mv in/ out/*
>> "in" folder is moved to the "out" folder and "in" folder will be inside
>> the "out" folder. "in" folder is removed in the operation.
>> *mv in/* out/*
>> contents of the "in" folder is moved to the "out" folder and there will
>> be no "in" folder inside the "out" folder. After the operation "in" folder
>> is also there.
>> *mv in/aa.txt out/*
>> "aa.txt" file will be moved to the "out" folder. We don't need to specify
>> the destination file name.
>> *mv in/aa.txt out/aa.txt*
>> "aa.txt" file will be moved to the "out" folder. This is similar to the
>> file move operation in the connector.
>>
>> Please do consider the above mentioned linux file copy and move
>> operations and the connector behavior.
>>
>> Thanks,
>>
>> On Tue, Feb 7, 2017 at 10:39 PM, Vivekananthan Sivanayagam <
>> vivekanant...@wso2.com> wrote:
>>
>>> Hi Maduranga,
>>>
>>> The basic behavior of the file/folder move operation is, once you move
>>> the file/folder from source to destination completely, the source
>>> file/folder will be deleted(Copy followed by Delete). If you want to keep
>>> the file/folder after moving to destination, you have to use the copy
>>> operation.
>>>
>>> If you want to move a file, you have to specify the destination as a
>>> file(with extension). If you need to just copy the file to the destination
>>> folder, here also you can use file copy operation(You don't need to mention
>>> the extension in the destination path).
>>>
>>> Thanks,
>>> Vivek
>>>
>>> Vivekananthan Sivanayagam
>>> Associate Software Engineer | WSO2
>>> E:vivekanant...@wso2.com
>>> M:+94752786138 <+94%2075%20278%206138>
>>>
>>> On Wed, Feb 8, 2017 at 6:11 AM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Malaka,

 I tried this with Windows local file system.

 Thanks,

 On Tue, Feb 7, 2017 at 6:34 PM, Malaka Silva  wrote:

> Hi Maduranga,
>
> What is the file system / Protocol you tried this with?
>
> On Tue, Feb 7, 2017 at 11:10 PM, Maduranga Siriwardena <
> madura...@wso2.com> wrote:
>
>>
>>
>> On Tue, Feb 7, 2017 at 10:54 AM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> While working with the file connector version 2 in [1], I noticed
>>> below limitations.
>>>
>>>1. When moving a folder there is no way to move the contents of
>>>a folder without deleting the source folder.
>>>2. When moving a file, if we specify a folder as a destination,
>>>this folder is converted to a file with the name of the source file
>>>(without the file extension). Shouldn't the file just copied to the
>>>destination folder?
>>>
>>> Destination folder is converted to a file with the destination
>> folder name (not with the name of the source file).
>>
>> Can these be done as improvements to the connector?
>>>
>>> [1] https://store.wso2.com/store/assets/esbconnector/details
>>> /48bab332-c6a6-4f5a-9b79-17e29c7ad4c6
>>>
>>> --
>>> Maduranga Siriwardena
>>> Software Engineer
>>> WSO2 Inc; http://wso2.com/
>>>
>>> Email: madura...@wso2.com
>>> Mobile: +94718990591 <+94%2071%20899%200591>
>>> Blog: http://madurangasblogs.blogspot.com/
>>> 
>>>
>>
>>
>>
>> --
>> Maduranga Siriwardena
>> Software Engineer
>> WSO2 Inc; http://wso2.com/
>>
>> Email: madura...@wso2.com
>> Mobile: +94718990591 <071%20899%200591>
>> Blog: http://madurangasblogs.blogspot.com/
>> 
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Associate Director / Architect
> M: +94 777 219 791 <+94%2077%20721%209791>
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : 

Re: [Dev] Enabling gzip Content-Encoding in WSO2 | FastXSLT Mediator

[Malaka Silva]

Hi Vivek,

Ideally users can't cover all the use cases with fastXSLT. Only basic use
cases can be covered. I guess this is one of those.

I'll add other ESB team members if they have a different opinion on this.

On Mon, Feb 13, 2017 at 5:42 PM, Vivek Kumar 
wrote:

> Hi ,
>
> I  am able to parse response from a web service through *XSLT Mediator*
> which has Content-Encoding as gzip(*Content-Encoding:gzip*)
>
> But when I parse the same response using *fastXSLT  Mediator* I am
> getting error like
>
>
>
> *[2017-02-13 17:22:42,255] ERROR - FastXSLTMediator Error while
> transforming the Stream *
>
> *org.apache.axis2.AxisFault: Error while building Passthrough stream*
>
> *   at
> org.apache.synapse.transport.passthru.util.RelayUtils.handleException(*
> *RelayUtils.java:284**)*
>
> *   at
> org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(*
> *RelayUtils.java:143**)*
>
> *   at org.wso2.carbon.mediator.fastXSLT.FastXSLTMediator.mediate(*
> *FastXSLTMediator.java:218**)*
>
> *   at org.apache.synapse.mediators.AbstractListMediator.mediate(*
> *AbstractListMediator.java:97**)*
>
> *   at org.apache.synapse.mediators.AbstractListMediator.mediate(*
> *AbstractListMediator.java:59**)*
>
> *   at org.apache.synapse.mediators.template.TemplateMediator.mediate(*
> *TemplateMediator.java:104**)*
>
> *   at org.apache.synapse.mediators.template.InvokeMediator.mediate(*
> *InvokeMediator.java:148**)*
>
> *   at org.apache.synapse.mediators.template.InvokeMediator.mediate(*
> *InvokeMediator.java:84**)*
>
> *   at org.apache.synapse.mediators.AbstractListMediator.mediate(*
> *AbstractListMediator.java:97**)*
>
> *   at org.apache.synapse.mediators.AbstractListMediator.mediate(*
> *AbstractListMediator.java:59**)*
>
> *   at org.apache.synapse.mediators.base.SequenceMediator.mediate(*
> *SequenceMediator.java:158**)*
>
> *   at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(*
> *Axis2SynapseEnvironment.java:337**)*
>
> *   at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(*
> *SynapseCallbackReceiver.java:554**)*
>
> *   at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(*
> *SynapseCallbackReceiver.java:188**)*
>
> *   at org.apache.axis2.engine.AxisEngine.receive(*
> *AxisEngine.java:180**)*
>
> *   at org.apache.synapse.transport.passthru.ClientWorker.run(*
> *ClientWorker.java:261**)*
>
> *   at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(*
> *NativeWorkerPool.java:172**)*
>
> *   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
> Source)*
>
> *   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)*
>
> *   at java.lang.Thread.run(Unknown Source)*
>
> *Caused by: **java.util.zip.ZipException**: Not in GZIP format*
>
> *   at java.util.zip.GZIPInputStream.readHeader(Unknown Source)*
>
> *   at java.util.zip.GZIPInputStream.(Unknown Source)*
>
>
>
>
>
> My Query:
>
> How do allow *gzip content-encoding*  in *WSO2ESB* .Does fastXSLT not
> allow *Content-Encoding:gzip* .Any suggestion would be much appreciated.
>
>
>
> *PS*:I could find any relevent information on google regarding above
> error.
>
> And we are bound to use *fastXSLT Mediator* as it is giving better
> performance.Please do let me know if you need more information to
> understand the scenario.
>
>
>
> *Thanks & Regards*,
> *Vivek Kumar*
> Eperium Business Solutions(I) Pvt Ltd,
> B-13, Sector 57,Noida.
>
>
>



-- 

Best Regards,

Malaka Silva
Associate Director / Architect
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
https://wso2.com/signature
http://www.wso2.com/about/team/malaka-silva/

https://store.wso2.com/store/

Don't make Trees rare, we should keep them with care
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Repos for Puppet Modules, Dockerfiles, and K8S Artifacts

[Lakmal Warusawithana]

+1. Before that we need to review current product wise releases. I have
notice product wise puppet releases does not have full user guide (starting
from puppet install etc).

On Tue, Feb 14, 2017 at 8:12 AM, Chamila De Alwis  wrote:

> Hi,
>
> Shall we mark the older repositories for the above [1][2][3] as obsolete
> since they are now distributed among the product teams? There are pull
> requests being opened and issues being created for them that should be done
> at either the product specific repositories or each *-common repository.
>
> We shouldn't remove them yet, IMO, since there haven't been any product
> stack wide release for any of the above artifacts. AFAIK only IS and APIM
> has release product specific Puppet modules. Once a release is done for
> every product, we could remove the older repositories however for now, we
> should mark them as obsolete and direct to proper new repositories for any
> new user to discover and interact with the new code.
>
> [1] - https://github.com/wso2/puppet-modules
> [2] - https://github.com/wso2/dockerfiles
> [3] - https://github.com/wso2/kubernetes-artifacts
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer | WSO2
> Blog: https://medium.com/@chamilad
>
>
>


-- 
Lakmal Warusawithana
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Repos for Puppet Modules, Dockerfiles, and K8S Artifacts

[Chamila De Alwis]

Hi,

Shall we mark the older repositories for the above [1][2][3] as obsolete
since they are now distributed among the product teams? There are pull
requests being opened and issues being created for them that should be done
at either the product specific repositories or each *-common repository.

We shouldn't remove them yet, IMO, since there haven't been any product
stack wide release for any of the above artifacts. AFAIK only IS and APIM
has release product specific Puppet modules. Once a release is done for
every product, we could remove the older repositories however for now, we
should mark them as obsolete and direct to proper new repositories for any
new user to discover and interact with the new code.

[1] - https://github.com/wso2/puppet-modules
[2] - https://github.com/wso2/dockerfiles
[3] - https://github.com/wso2/kubernetes-artifacts

Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Senior Software Engineer | WSO2
Blog: https://medium.com/@chamilad
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] wso2 IS 5.3.0 End User Dashboard

[mgbii bax]

Hello,

New logs below as requested.

http_access_2017-02-13.log:


>> 10.16.20.1 - - [13/Feb/2017:09:53:34 -0800] "GET /dashboard/ HTTP/1.1"
>> 302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML,
>> like Gecko) Chrome/55.0.2883.87 Safari/537.36"
>
> 10.16.20.1 - - [13/Feb/2017:09:53:34 -0800] "GET /dashboard/login.jag
>> HTTP/1.1" 302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36
>> (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36"
>
> 10.16.20.1 - - [13/Feb/2017:09:53:34 -0800] "GET
>> /dashboard/samlsso.jag?login=true HTTP/1.1" 200 1608 "-" "Mozilla/5.0
>> (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
>> Chrome/55.0.2883.87 Safari/537.36"
>
> 10.16.20.1 - - [13/Feb/2017:09:53:34 -0800] "GET /favicon.ico HTTP/1.1"
>> 405 832 "
>> https://lfhpkiug7uas.musicreports.com:9443/dashboard/samlsso.jag?login=true;
>> "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
>> Chrome/55.0.2883.87 Safari/537.36"
>
> 10.16.20.1 - - [13/Feb/2017:09:53:34 -0800] "POST /samlsso HTTP/1.1" 302 -
>> "
>> https://lfhpkiug7uas.musicreports.com:9443/dashboard/samlsso.jag?login=true;
>> "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
>> Chrome/55.0.2883.87 Safari/537.36"
>
> 10.16.20.1 - - [13/Feb/2017:09:55:41 -0800] "GET
>> /authenticationendpoint/login.do?SSOAuthSessionID=12A8D518C7B986BB09722727C2BEBF0E7CEA798EA8C8E198352722BD165D5957A1BEE5C59EFAE04344D2F54F8437F0973EB109DC81F62BA68E7BED301C170749FEF1B6F593E827D82589CF7F4B8C76C0A30D569F93400CB32A92305F52F846F6E73CA81F8AAE7F6C69E01F0DF538B888B15436337E123892AFAEA3F94336C952=%2Fsamlsso=false=false=carbon.super=fb012fb1-bd38-4463-8741-a296f7f54766=wso2.my.dashboard=samlsso=wso2_sp_dashboard=true=BasicAuthenticator:LOCAL
>> HTTP/1.1" 500 616 "
>> https://lfhpkiug7uas.musicreports.com:9443/dashboard/samlsso.jag?login=true;
>> "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
>> Chrome/55.0.2883.87 Safari/537.36"
>
> 10.16.20.1 - - [13/Feb/2017:09:55:42 -0800] "GET /favicon.ico HTTP/1.1"
>> 405 832 "
>> https://lfhpkiug7uas.musicreports.com:9443/authenticationendpoint/login.do?SSOAuthSessionID=12A8D518C7B986BB09722727C2BEBF0E7CEA798EA8C8E198352722BD165D5957A1BEE5C59EFAE04344D2F54F8437F0973EB109DC81F62BA68E7BED301C170749FEF1B6F593E827D82589CF7F4B8C76C0A30D569F93400CB32A92305F52F846F6E73CA81F8AAE7F6C69E01F0DF538B888B15436337E123892AFAEA3F94336C952=%2Fsamlsso=false=false=carbon.super=fb012fb1-bd38-4463-8741-a296f7f54766=wso2.my.dashboard=samlsso=wso2_sp_dashboard=true=BasicAuthenticator:LOCAL;
>> "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
>> Chrome/55.0.2883.87 Safari/537.36"
>
>
>>

wso2carbon.log:

TID: [-1234] [] [2017-02-13 09:55:41,925] ERROR
>> {org.apache.catalina.core.ApplicationDispatcher} -  Servlet.service() for
>> servlet samlsso_login.do threw exception
>
> java.io.IOException: java.net.ConnectException: Connection timed out
>> (Connection timed out)
>
> at
>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:467)
>
> at
>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
>
> at
>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>
> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>
> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>
> at
>> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>
> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>
> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>
> at
>> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:747)
>
> at
>> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:485)
>
> at
>> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:410)
>
> at
>> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:337)
>
> at
>> org.wso2.carbon.identity.application.authentication.endpoint.util.filter.AuthenticationEndpointFilter.doFilter(AuthenticationEndpointFilter.java:161)
>
> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>
> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>
> at
>> org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:120)
>
> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>
> at
>> 

Re: [Dev] wso2 IS 5.3.0 End User Dashboard

[mgbii bax]

Hello,

I have already posted the logs below..

from logs:
> 10.16.20.1 - - [12/Feb/2017:12:06:59 -0800] "GET /dashboard/ HTTP/1.1" 302
> - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like
> Gecko) Chrome/55.0.2883.87 Safari/537.36"
> 10.16.20.1 - - [12/Feb/2017:12:06:59 -0800] "GET /dashboard/login.jag
> HTTP/1.1" 302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36
> (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36"
> 10.16.20.1 - - [12/Feb/2017:12:06:59 -0800] "GET
> /dashboard/samlsso.jag?login=true HTTP/1.1" 200 1608 "-" "Mozilla/5.0
> (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/55.0.2883.87 Safari/537.36"
> 10.16.20.1 - - [12/Feb/2017:12:06:59 -0800] "GET /favicon.ico HTTP/1.1"
> 405 832 "https://sub.owndomain.com:9443/dashboard/samlsso.jag?login=true;
> "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/55.0.2883.87 Safari/537.36"
> 10.16.20.1 - - [12/Feb/2017:12:06:59 -0800] "POST /samlsso HTTP/1.1" 302 -
> "https://sub.owndomain.com:9443/dashboard/samlsso.jag?login=true;
> "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/55.0.2883.87 Safari/537.36"
> 10.16.20.1 - - [12/Feb/2017:12:09:10 -0800] "GET
> /authenticationendpoint/login.do?SSOAuthSessionID=17B09FD1FE
> 6F3B61B34F88DA13AAF56238F4A32343D04F7933F43D5C30B55CBC29DFE5
> F5549DCA8296B237E06BD288ABAEE827D7884844A68F5B495CD12C0B2259
> 95658EE5253FDBFD640A120EF5FBB7BBA3125F005232F99FCF5A1376F2E3
> 0C433EACD840FEB8254216393B24A6B20B0ED0A6405075215CAC7BFC24ED
> 137543=%2Fsamlsso=false
> veAuth=false=carbon.super=
> 87078deb-0812-4118-a227-ba3bd26dbf1b=wso2.my.dashboard=
> samlsso=wso2_sp_dashboard=true=BasicAuthenticator:LOCAL
> HTTP/1.1" 500 616 "https://sub.owndomain.com:944
> 3/dashboard/samlsso.jag?login=true" "Mozilla/5.0 (Windows NT 6.1; WOW64)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36"
> 10.16.20.1 - - [12/Feb/2017:12:09:11 -0800] "GET /favicon.ico HTTP/1.1"
> 405 832 "https://sub.owndomain.com:9443/authenticationendpoint/login
> .do?SSOAuthSessionID=17B09FD1FE6F3B61B34F88DA13AAF56238F4A32
> 343D04F7933F43D5C30B55CBC29DFE5F5549DCA8296B237E06BD288ABAEE
> 827D7884844A68F5B495CD12C0B225995658EE5253FDBFD640A120EF5FBB
> 7BBA3125F005232F99FCF5A1376F2E30C433EACD840FEB8254216393B24A
> 6B20B0ED0A6405075215CAC7BFC24ED137543=%
> 2Fsamlsso=false=false=
> carbon.super=87078deb-0812-4118-a227-
> ba3bd26dbf1b=wso2.my.dashboard=
> samlsso=wso2_sp_dashboard=true=
> BasicAuthenticator:LOCAL" "Mozilla/5.0 (Windows NT 6.1; WOW64)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36"



--

regards

gezeala bacuño II

On Sun, Feb 12, 2017 at 8:17 PM, Farasath Ahamed  wrote:

> Hi,
>
> Can you try to access the dashboard once again and post the error logs
> printed in wso2carbon.log? You can find this in WSO2_HOME/repository/logs/
> folder, where WSO2_HOME is the root of your WSO2 Identity Server.
>
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
> 
>
>
>
> On Sun, Feb 12, 2017 at 12:30 PM, mgbii bax  wrote:
>
>> Hello,
>>
>> I did not generate new keys since I have all the necessary certificates
>> and key for *.owndomain.com and owndomain.com. I used the same
>> certificates for our publicly accessible website. I followed the directions
>> from [1] link below to create a new keystore and import to client store. I
>> have also modified all affected files, replacing the wso2carbon.jks file
>> entries, new password, new alias, new key password etc. No End User
>> dashboard still. I keep on getting this message in my chrome browser:
>>
>> [1] https://docs.wso2.com/display/ADMIN446/Creating+New+Keystores
>>
>> I'm using a no GUI linux box to test the wso2 service that's why I don't
>> use "localhost".
>>
>> + Start from this link:
>> https://sub.owndomain.com:9443/dashboard
>>
>> + I get redirected to:
>> https://sub.owndomain.com:9443/dashboard/samlsso.jag?login=true
>>
>> + With a page that shows:
>> You are now being redirected to Identity Server. If the redirection
>> fails, please click on the button below.
>>
>> + With a "Redirect manually" button
>>
>> + Then after a few minutes..
>> https://sub.owndomain.com:9443/authenticationendpoint/login.
>> do?SSOAuthSessionID=1CFADEB31AC41CC6DF875E2477D387D2FC3CAF3C
>> FF13B80E6BB4E747743D549BD4A2076A1DB248B925785BE187247CB61630
>> 5D962EAE88275514941D5167CF195DCA7E02E1A0BC0F74BDCAC0E3778135
>> FF5CAC684B474F4C366598995DC769681E2E7ADB9D6261888C107E51CDD0
>> 76C58F78786004977A0BC033B5F50D6BA207=%2
>> Fsamlsso=false=false=
>> carbon.super=b6a8a00f-fe21-4e54-b69c-
>> 49ccb3014549=wso2.my.dashboard=
>> samlsso=wso2_sp_dashboard=true=
>> BasicAuthenticator:LOCAL
>>
>> + With a page that shows:
>> Authentication Error !
>> Something went wrong 

Re: [Dev] [WSO2 IS] Generated IdP metadata urls are always pointing to localhost:9443

[Hanen Ben Rhouma]

Thanks Kasun,

Isn't there a way to change the resident IdP urls generated by default, my
goal is to use the metadata Url instead of the file and this can't be
achieved by creating a custom IdP instance, it should be routed by the
resident one.

Regards,
Hanen

On Mon, Feb 13, 2017 at 10:44 AM, Kasun Bandara 
wrote:

> Hi Hanen,
>
> For each tenant, you should be able to define their own separate metadata
> information as you stated. Can you please check your scenario with [1].
>
> [1] http://saml-metadata-featurer.blogspot.com.au/2016/
> 11/saml-metadata-feature-for-identity.html
>
> Regards,
> Kasun.
>
>
>
> Kasun Gayan Bandara
> PhD Research Student
> Machine Learning Group
>
> Faculty of Information Technology, Clayton
> Monash University
> 25 Exhibition Walk, Clayton Campus
> Wellington Road
> Clayton VIC 3800
> Australia.
>
> E: herath.band...@monash.edu
> M (+61) 43 491 6476
>
> 
>
>
>
> On Mon, Feb 13, 2017 at 8:29 PM, Hanen Ben Rhouma 
> wrote:
>
>>
>> Hello Guys,
>>
>> I have a question regarding the generated IdP metadata, the generated SSo
>> Url and Logout Url are always pointing to localhost:9443, I changed
>> the HostName and Offset in carbon.xml and even the IdentityProviderURL
>> and DefaultLogoutEndpoint in identity.xml but still the Urls are the same.
>>
>> How can I adapt such metadata dynamically to each environment and
>> according to each tenant?
>>
>>
>> Regards,
>> Hanen
>>
>> ___
>> 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

Re: [Dev] [WSO2 IS] Generated IdP metadata urls are always pointing to localhost:9443

[Kasun Bandara]

Hi Hanen,

For each tenant, you should be able to define their own separate metadata
information as you stated. Can you please check your scenario with [1].

[1]
http://saml-metadata-featurer.blogspot.com.au/2016/11/saml-metadata-feature-for-identity.html

Regards,
Kasun.



Kasun Gayan Bandara
PhD Research Student
Machine Learning Group

Faculty of Information Technology, Clayton
Monash University
25 Exhibition Walk, Clayton Campus
Wellington Road
Clayton VIC 3800
Australia.

E: herath.band...@monash.edu
M (+61) 43 491 6476





On Mon, Feb 13, 2017 at 8:29 PM, Hanen Ben Rhouma 
wrote:

>
> Hello Guys,
>
> I have a question regarding the generated IdP metadata, the generated SSo
> Url and Logout Url are always pointing to localhost:9443, I changed
> the HostName and Offset in carbon.xml and even the IdentityProviderURL
> and DefaultLogoutEndpoint in identity.xml but still the Urls are the same.
>
> How can I adapt such metadata dynamically to each environment and
> according to each tenant?
>
>
> Regards,
> Hanen
>
> ___
> 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

Re: [Dev] [Architecture] WSO2 Enterprise Integrator 6.0.0 Alpha Released !

[Gillian Dass]

Hi all,

WSO2 EI docs are now public. Since the content is still work in progress,
this version contains only the Introduction, QSG and basic tutorial.

Regards,
Gillian

On Fri, Feb 10, 2017 at 5:02 PM, Harshana Eranga Martin <
harshan...@gmail.com> wrote:

> Thanks Tishan :-)
>
> Thanks and Regards,
> Harshana
>
> On Fri, 10 Feb 2017 at 9:39 pm, Tishan Dahanayakage 
> wrote:
>
>> When are we going to make documents publicaly available
>>
>> On Feb 10, 2017 3:26 PM, "prabath"  wrote:
>>
>> Hi Tishan.
>>
>> Document is not visible to the outside.
>>
>> Thanks.
>>
>> On Fri, Feb 10, 2017 at 3:33 PM, Tishan Dahanayakage 
>> wrote:
>>
>> Hi Harshana,
>>
>> Please find the documentation here[1]. Please note this is Work In
>> Progress. So if you find any issues please report. :)
>>
>> [1] https://docs.wso2.com/display/EI600/WSO2+Enterprise+
>> Integrator+Documentation
>> Thanks
>> /Tishan
>>
>> On Fri, Feb 10, 2017 at 3:40 AM, Harshana Eranga Martin <
>> harshan...@gmail.com> wrote:
>>
>> Hi Himasha,
>>
>> What is the url to the product documentation?
>>
>>
>> On Fri, 10 Feb 2017 at 7:34 am, Himasha Guruge  wrote:
>>
>> WSO2 Integration Team is pleased to announce the alpha release of WSO2
>> Enterprise Integrator (EI) 6.0.0.
>>
>> Source & Distribution: https://github.com/wso2/product-ei/releases/
>> tag/v6.0.0-alpha
>> Bug fixes: https://github.com/wso2/product-ei/issues?page=1;
>> q=is%3Aissue+is%3Aclosed
>> Known issues: https://github.com/wso2/product-ei/issues
>>
>> *How to Run*
>>
>> 1.Extract the downloaded zip.
>>
>> 2.Go to the bin directory in the extracted folder.
>>
>> 3.Run the start-all.sh or start-all.bat as appropriate.
>>
>> 4.Launch a web browser and navigate to https://localhost:8243/carbon to
>> access the Enterprise Integrator Management Console.
>>
>> 5.Navigate to https://localhost:9444/carbon to access analytics
>> management console and https://localhost:9444/dashboard to access
>> Enterprise Integrator Dashboard.
>>
>> 6.Navigate to https://localhost:9445/carbon to access business process
>> management console.
>>
>> 7.Navigate to https://localhost:9446/carbon to access broker management
>> console.
>>
>> 8.Use "admin", "admin" as the username and password to login as an admin.
>>
>> Thanks,
>>
>>   -WSO2 Integration Team-
>>
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>> --
>> Sent from Gmail Mobile for IPhone
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>>
>>
>> --
>> Tishan Dahanayakage
>> Senior Software Engineer
>> WSO2, Inc.
>> Mobile:+94 716481328 <+94%2071%20648%201328>
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, re-transmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>>
>>
>> --
>> Prabath Ariyarathna.
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
> --
> Sent from Gmail Mobile for IPhone
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Gillian Dass
WSO2 Inc.
http://wso2.com

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

[Dev] [WSO2 IS] Generated IdP metadata urls are always pointing to localhost:9443

[Hanen Ben Rhouma]

Hello Guys,

I have a question regarding the generated IdP metadata, the generated SSo
Url and Logout Url are always pointing to localhost:9443, I changed
the HostName and Offset in carbon.xml and even the IdentityProviderURL
and DefaultLogoutEndpoint in identity.xml but still the Urls are the same.

How can I adapt such metadata dynamically to each environment and according
to each tenant?


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

Re: [Dev] GSoC 2017

[Sriskandarajah Suhothayan]

Thanks for your interest.

You can find the Siddhi Grammer file here[1] we have to implement according
to this, But for now, I would like to see you creating a PoC of a language
plugin for Eclipse showing syntax highlighting and code completion for a
sample language. It does not need to be for Siddhi.

Regards
Suho

[1]
https://github.com/wso2/siddhi/blob/master/modules/siddhi-query-compiler/src/main/antlr4/org/wso2/siddhi/query/compiler/SiddhiQL.g4


On Sat, Feb 11, 2017 at 12:56 PM, Vihanga Liyanage <
vihangaliyanage...@gmail.com> wrote:

> Hi Suho,
>
> I read through your project proposals for GSoC 2017 and particularly
> interested in the project Proposal 5: Eclipse Plugin for Siddhi
> 
> , which lists you as the possible mentor. I'd really like to work on this
> idea further, hoping to get selected for GSoC and complete the project at
> the end.
> It'll be really great if you could point me in a direction where I could
> do some more background work on this.
>
> Best Regards,
> Vihanga Liyanage,
> Undergraduate,
> University of Colombo School of Computing.
> M: +94 71 012 4103 <071%20012%204103>
>
> 
> 
> 
>



-- 

*S. Suhothayan*
Associate Director / Architect & Team Lead of WSO2 Complex Event Processor
*WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 <077%20975%206757> | 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