Re: [Dev] Deploying multiple travelocity applications by renaming the web application name

2017-08-12 Thread Harsha Kumara 
Created JIRA in [1] in a case of we going to add it.

 https://wso2.org/jira/browse/IDENTITY-6257

On Sun, Aug 13, 2017 at 1:31 AM, Harsha Kumara  wrote:

> Hi All,
>
> I tried to deploy multiple travelocity applications samples by renaming
> the web application directory. But it didn't work. The reason for this
> behavior is in code level we check the web application context path
> contains travelocity.com. So if I renamed the web application to
> travelovitysample.com, it won't work as the initial travelocity.property
> configuration not getting loaded. I think it's better to add this.
>
> Code :
>
> if(servletContextEvent.getServletContext().getContextPath().contains("travelocity.com"))
>  {
> properties.load(servletContextEvent.getServletContext().
> getResourceAsStream("/WEB-INF/classes/travelocity.properties"));
> } else 
> if(servletContextEvent.getServletContext().getContextPath().contains("avis.com"))
>  {
> properties.load(servletContextEvent.getServletContext().
> getResourceAsStream("/WEB-INF/classes/avis.properties"));
> }
>
> Then I have added an else statement which will switch to
> travelocity.properties file in its own web application path.
>
> if(servletContextEvent.getServletContext().getContextPath().contains("travelocity.com"))
>  {
> properties.load(servletContextEvent.getServletContext().
> getResourceAsStream("/WEB-INF/classes/travelocity.properties"));
> } else 
> if(servletContextEvent.getServletContext().getContextPath().contains("avis.com"))
>  {
> properties.load(servletContextEvent.getServletContext().
> getResourceAsStream("/WEB-INF/classes/avis.properties"));
> } else {
> try {
> properties.load(servletContextEvent.getServletContext().
> 
> getResourceAsStream("/WEB-INF/classes/travelocity.properties"));
> } catch (Exception e) {
> LOGGER.log(Level.SEVERE, "Error while loading the default 
> configuration in /WEB-INF/classes/travelocity.properties", e);
> }
> }
>
> Thanks,
> Harsha
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618 <+94%2077%20550%205618>
> Blog:harshcreationz.blogspot.com
>



-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Deploying multiple travelocity applications by renaming the web application name

2017-08-12 Thread Harsha Kumara 
Hi All,

I tried to deploy multiple travelocity applications samples by renaming the
web application directory. But it didn't work. The reason for this behavior
is in code level we check the web application context path contains
travelocity.com. So if I renamed the web application to
travelovitysample.com, it won't work as the initial travelocity.property
configuration not getting loaded. I think it's better to add this.

Code :

if(servletContextEvent.getServletContext().getContextPath().contains("travelocity.com"))
{
properties.load(servletContextEvent.getServletContext().
getResourceAsStream("/WEB-INF/classes/travelocity.properties"));
} else 
if(servletContextEvent.getServletContext().getContextPath().contains("avis.com"))
{
properties.load(servletContextEvent.getServletContext().
getResourceAsStream("/WEB-INF/classes/avis.properties"));
}

Then I have added an else statement which will switch to
travelocity.properties file in its own web application path.

if(servletContextEvent.getServletContext().getContextPath().contains("travelocity.com"))
{
properties.load(servletContextEvent.getServletContext().
getResourceAsStream("/WEB-INF/classes/travelocity.properties"));
} else 
if(servletContextEvent.getServletContext().getContextPath().contains("avis.com"))
{
properties.load(servletContextEvent.getServletContext().
getResourceAsStream("/WEB-INF/classes/avis.properties"));
} else {
try {
properties.load(servletContextEvent.getServletContext().
getResourceAsStream("/WEB-INF/classes/travelocity.properties"));
} catch (Exception e) {
LOGGER.log(Level.SEVERE, "Error while loading the default
configuration in /WEB-INF/classes/travelocity.properties", e);
}
}

Thanks,
Harsha
-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Amazon Lambda connector for WSO2 Enterprise Integrator

2017-08-12 Thread Vivekananthan Sivanayagam 
Hi Miyuru,

You can refer [1] to get an idea of writing connector and refer [2] to
understand how "Amazon DynamoDB Connector" connector is working, you can
find an implementation here[3].


[1] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+Connector
[2] https://docs.wso2.com/display/ESBCONNECTORS/Amazon+DynamoDB+Connector
[3] https://github.com/wso2-extensions/esb-connector-amazondynamodb

Thanks,
Vivek

Vivekananthan Sivanayagam
Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138

On Fri, Aug 11, 2017 at 7:54 PM, Miyuru Madusanka  wrote:

> Hello dev guys at WSO2,
> I am working with the project and need some help from you. I need to know
> what are the resources I need to know/ follow to work on the below project.
> I am not familiar with any of your products earlier. So, could you please
> suggest how should I start or what are the things I need to practice? Your
> answers are much appreciated.  Thank you.
> Amazon Lambda connector for WSO2 Enterprise Integrator
>
> ___
> 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] [VOTE] Release of WSO2 IoT Server 3.1.0 RC version 4

2017-08-12 Thread ayyoob hamza 
Hi,

I have tested following functionalities

   - Create Device Type with HTTP transport
   - Create Device Type with MQTT transport
   - Create device instances for above device types
   - Publish device events
   - Device operation flow.
   - Sample installation and virtual firealarm flow.
   - Android enrollment
   - Connected cup flow.

Found no issues.

[+] Stable - go ahead and release.

On Fri, Aug 11, 2017 at 11:36 PM, Milan Perera  wrote:

> Hi Devs,
>
> We are pleased to announce the release candidate version 4 of WSO2 IoT Server
> 3.1.0.
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
>
> Known issues : https://github.com/wso2/product-iots/issues-RC4
> 
>
> Source and binary distribution files:
> https://github.com/wso2/product-iots/releases/tag/v3.1.0-RC4
>
> The tag to be voted upon:
> https://github.com/wso2/product-iots/tree/v3.1.0-RC4
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thank you
>
> Regards,
> --
> *Milan Perera *| Senior Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
> Email: mi...@wso2.com  | Web: www.wso2.com
> 
> 
>
> ___
> 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] Set static private IP addresses to AWS EC2 Instances registered with an AWS Elastic Load Balancer

2017-08-12 Thread Chiranga Alwis 
Hi all,

I have posted the following question in StackOverflow under the title
corresponding to the mail subject. Any help, ideas and suggestions are
highly appreciated.


https://stackoverflow.com/questions/45648220/set-static-
private-ip-addresses-to-aws-ec2-instances-registered-with-an-aws-elas

-- 
Yours sincerely,

*Chiranga Alwis*
Software Engineer | WSO2

*Mobile : *+94775930497 <+94%2077%20593%200497>
*Email: *chirangaal...@gmail.com
*LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9


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

Re: [Dev] Regarding the OIDC openid scope in WSO2 IS

2017-08-12 Thread Omindu Rathnaweera 
I had a quick chat with the Johann as well. So for the sake of backward
compatibility we will not change this in the product and run the tests by
altering the registry entry.

@Fara: Am I correct to assume that oidc-scope-config.xml gets only affected
during the first startup ? In any case we need to document about both
configs if we haven't already.

On Sat, Aug 12, 2017 at 10:10 AM, Ashen Weerathunga  wrote:

>
>
> On Fri, Aug 11, 2017 at 10:13 AM, Farasath Ahamed 
> wrote:
>
>>
>>
>> On Friday, August 11, 2017, Omindu Rathnaweera  wrote:
>>
>>>
>>>
>>> On Thu, Aug 10, 2017 at 5:15 PM, Hasini Witharana 
>>> wrote:
>>>
 Hi,

 Currently I am working on making WSO2 IS OpenID Connect certified. I
 ran a test on requesting essential claims from OP, when the scope is
 openid. It gave an error saying unexpected claims returned.

>>>
>>> This is not an error, but a warning correct ?
>>>
>>>
 Then I inquired about this issue through the mailing list of OIDC
 specifications [1]. I got some information from that as openid scope
 should only return subject and issuer.

 IS 5.4.0 is supporting many claims for scope openid. They are :
   sub,email,email_verified,name,
 family_name,given_name,middle_name,nickname,
   preferred_username,profile,pic
 ture,website,gender,birthdate,zoneinfo,locale,
   phone_number,phone_number_veri
 fied,address,street,updated_at

 I couldn't find In the OIDC specification where it mention that, openid
 scope should only return subject and issuer.

>>>
>>> AFAIK, the spec has not specifically mentioned about what we should
>>> return for the openid scope and it only mentions about the what should be
>>> returned for the default 4 scopes. However it is understandable that the
>>> test client expects a minimum set of claims when having only the openid
>>> scope. If an RP needs additional claims, it should request them with
>>> specifying additional scopes and/or essential claims. So I think the
>>> correct behavior would be to return only a minimal set of claims for the
>>> openid scope.
>>>
>>
>> Since the spec hasn't specifed this minimal set of claims one can argue
>> that it is something specific to an RP. This is how our current
>> implementation works as well. Although we could define a set of claim bound
>> to the 'openid' scope, the service provider could control what it needs
>> from the claims bound to openid scope by using requested claims
>> configuration.
>>
>> Changing 'openid' scope to return issuer and sub claims only will be a
>> breaking change for many existing providers who rely on the additional
>> claims (some of them could be mandatory in PoV of the RP)
>>
>> IMO, if the spec doesn't mandate what should be returned for openid scope
>> then we can keep our existing implementation as it is.
>>
>
> +1 to keep existing claims if it's not a spec violation. Seems like we
> have defined all the standerd claims mentioned in the spec [1] under our
> openid scope implemenation. So if someone need to remove some of claims
> they can remove it from the oidc configurations in the registry.
>
> [1] http://openid.net/specs/openid-connect-core-1_0.html#StandardClaims
>
>
>>
>>>
 Can you please help me on this issue?

 Thank you.


 [1] - http://lists.openid.net/pipermail/openid-specs/2017-August/s
 ubject.html

 --

 *Hasini Witharana*
 Software Engineering Intern | WSO2


 *Email : hasi...@wso2.com*

 *Mobile : +94713850143 <+94%2071%20385%200143>[image:
 http://wso2.com/signature] *

>>>
>>>
>>> Regards,
>>> Omindu.
>>>
>>> --
>>> Omindu Rathnaweera
>>> Senior Software Engineer, WSO2 Inc.
>>> Mobile: +94 771 197 211 <+94%2077%20119%207211>
>>>
>>
>>
>> --
>> Farasath Ahamed
>> Software Engineer, WSO2 Inc.; http://wso2.com
>> Mobile: +94777603866
>> Blog: blog.farazath.com
>> Twitter: @farazath619 
>> 
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Ashen Weerathunga*
> Software Engineer
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: as...@wso2.com
> Mobile: +94716042995 <94716042995>
> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
> *
> 
>

Thanks,
Omindu

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