[Dev] Issue in Proxy service

[Lipsa Pradhan]

Hello everyone,

I had made a proxy service of one my dataservices. But I'm facing the
following error :


  Expected transport is "https" but
incoming transport found : "http" 



How to resolve this?

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

Re: [Dev] [IoTS] how to enable CORS in IOTS (for example: alpha version)

[Ayyoob Hamza]

> Thank you very much. Can I change the tomcat web.xml file and add the CORS
> filter to implement this requirement as a workaround?
>
Yes, You can find the code in [1]

[1]
https://github.com/wso2/carbon-device-mgt/tree/v1.1.0/components/identity-extensions/dynamic-client-registration
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] how to enable CORS in IOTS (for example: alpha version)

[云展智创]

Ayyoob,

Thank you very much. Can I change the tomcat web.xml file and add the CORS 
filter to implement this requirement as a workaround?

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

在 2017年6月20日，上午10:56，Ayyoob Hamza  写道：

> Hi Zhanwen,
> 
> The CORS configuration in api-manager.xml is related to the synapse gateway 
> (default port 8243/8280). But the API invocation through port 9443 goes 
> through tomcat gateway(valve). Therefore the configuration change that you 
> did won't work on the alpha pack. However, this should work if you access it 
> through 8243 but you need to try this on the IoTS 3.0.0 pack since synapse 
> gateway was not supported during the alpha release. In addition app creation 
> endpoint https://:9443/dynamic-client-web/register/ is not 
> supported from IoTS 3.0.0 RC, instead of "dynamic-client-web/register/" we 
> have to use the endpoint given in the below curl command to create 
> application.
> 
> curl -k -X POST https://localhost:8243/api-application-registration/register 
> -H 'authorization: Basic YWRtaW46YWRtaW4=' -H 'content-type: 
> application/json' -d '{ "applicationName":"appName", 
> "tags":["device_management"]}'
> 
> Thanks
> 
> Ayyoob Hamza
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> email: ayy...@wso2.com cell: +94 77 1681010
> 
> On Tue, Jun 20, 2017 at 7:33 AM, 云展智创  wrote:
> Hi team,
> 
> I had changed the api-manager.xml with the following setting, but I still got 
> the errors below:
> 
> 
> 
> XMLHttpRequest cannot load 
> https://:9443/dynamic-client-web/register/. Response to preflight 
> request doesn't pass access control check: No 'Access-Control-Allow-Origin' 
> header is present on the requested resource. Origin 'http://localhost:63342' 
> is therefore not allowed access. The response had HTTP status code 500.
> 
> I want to use the api https://:9443/dynamic-client-web/register/ to 
> get the client secret and client id and then to get access token with 
> oauth2/token
> 
> Could you tell me how to setup CORS in IOTS? 
> 
> Thanks.
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API Management
> 
> 
> ___
> 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] [IoTS] how to enable CORS in IOTS (for example: alpha version)

[Ayyoob Hamza]

Hi Zhanwen,

The CORS configuration in api-manager.xml is related to the synapse gateway
(default port 8243/8280). But the API invocation through port 9443 goes
through tomcat gateway(valve). Therefore the configuration change that you
did won't work on the alpha pack. However, this should work if you access
it through 8243 but you need to try this on the IoTS 3.0.0 pack since
synapse gateway was not supported during the alpha release. In addition app
creation endpoint https://:9443/dynamic-client-web/register/ is
not supported from IoTS 3.0.0 RC, instead of "dynamic-client-web/register/"
we have to use the endpoint given in the below curl command to create
application.

curl -k -X POST https://localhost:8243/api-application-registration/register
-H 'authorization: Basic YWRtaW46YWRtaW4=' -H 'content-type:
application/json' -d '{ "applicationName":"appName",
"tags":["device_management"]}'

Thanks

*Ayyoob Hamza*
*Senior Software Engineer*
WSO2 Inc.; http://wso2.com
email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>

On Tue, Jun 20, 2017 at 7:33 AM, 云展智创  wrote:

> Hi team,
>
> I had changed the api-manager.xml with the following setting, but I still
> got the errors below:
>
>
> XMLHttpRequest cannot load 
> https://:9443/dynamic-client-web/register/.
> Response to preflight request doesn't pass access control check: No
> 'Access-Control-Allow-Origin' header is present on the requested resource.
> Origin 'http://localhost:63342' is therefore not allowed access. The
> response had HTTP status code 500.
>
> I want to use the api https://:9443/dynamic-client-web/register/
> to get the client secret and client id and then to get access token with
> oauth2/token
>
> Could you tell me how to setup CORS in IOTS?
>
> Thanks.
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435 <+86%20139%202221%208435>
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API Management
>
>
> ___
> 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] [IoTS] how to enable CORS in IOTS (for example: alpha version)

[云展智创]

Hi team,

I had changed the api-manager.xml with the following setting, but I still got 
the errors below:



XMLHttpRequest cannot load 
https://:9443/dynamic-client-web/register/. Response to preflight 
request doesn't pass access control check: No 'Access-Control-Allow-Origin' 
header is present on the requested resource. Origin 'http://localhost:63342' is 
therefore not allowed access. The response had HTTP status code 500.

I want to use the api https://:9443/dynamic-client-web/register/ to 
get the client secret and client id and then to get access token with 
oauth2/token

Could you tell me how to setup CORS in IOTS? 

Thanks.
－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

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

Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0

[Hasitha Jayasundara]

Hi Malaka,

Thanks for the reply.I'll rearrange the existing code to use as IBM MQ
connector in the following days and update the thread.I'll call you if
there's any issue.

Thanks

On Tue, Jun 20, 2017 at 6:05 AM, Malaka Silva  wrote:

> Hi Hasitha,
>
> We will also create a git repo to maintain the code. Maheshika will
> provide the required details.
>
> On Tue, Jun 20, 2017 at 5:45 AM, Hasitha Jayasundara <
> hasithajayasunda...@gmail.com> wrote:
>
>> Hi all,
>>
>> Thanks for pointing out the above.I am doing a connector for IBM
>> WebSphere MQ.What I was thinking about the inbound part is somewhat wrong.I
>> missed this part "this should be added as an extension similar to [1]" from
>> the beginning.Really sorry for the misunderstanding.
>>
>> 1. UI changes - Removed it from the milestone plan
>> 2. Adding preferred authentications to the inbound - Really sorry for
>> this.It should be preferred parameters for the inbound(polling)
>>
>> @Riyafa @Malaka Thanks for the kind help.I'll definitely call you if
>> there's any issue.
>>
>> Thanks.
>>
>> [1].https://github.com/wso2-extensions/esb-inbound-amazonsqs
>>
>>
>> On Mon, Jun 19, 2017 at 4:39 PM, Malaka Silva  wrote:
>>
>>> Hi Hasitha,
>>>
>>> Adding inbound endpoint to the carbon mediation and debugging
>>>   You don't need to do this since this should be added as an extesnion
>>> similar to [1]
>>> Completing the user interface changes
>>>You don't need to do any UI changes. It'll be handled by ESB/EI [2]
>>> Adding preffered authentications to the inbound
>>> Not clear what you mean by this?
>>>
>>> @Riyafa - Thx for pointing this out. I guess Hasitha got bit confused
>>> with names. Anyway you should be doing a connector. Hasitha please
>>> confirm this.
>>>
>>> Also if something is not clear feel free to call my mobile.
>>>
>>> [1] https://github.com/wso2-extensions/esb-inbound-amazonsqs
>>> [2] https://docs.wso2.com/display/ESBCONNECTORS/Configuring+Amaz
>>> onSQS+Streaming+Inbound+Endpoint+Operations
>>>
>>> On Mon, Jun 19, 2017 at 10:48 AM, Riyafa Abdul Hameed 
>>> wrote:
>>> > Hi,
>>> >
>>> > I am just curious if you would be writing a connector or a mediator.
>>> >
>>> > Regards,
>>> > Riyafa
>>> >
>>> > On Mon, Jun 19, 2017 at 6:47 AM, Hasitha Jayasundara
>>> >  wrote:
>>> >>
>>> >> Hi all,
>>> >>
>>> >> Please find updated milestone plan here.
>>> >>
>>> >>
>>> >> https://docs.google.com/spreadsheets/d/19ijxAVHttxhLVuSJ0nfu
>>> MUZ4x4lAD6ueYL5C3FNaFpg/edit?usp=sharing
>>> >>
>>> >> Thanks
>>> >>
>>> >> On Thu, Jun 15, 2017 at 9:30 AM, Hasitha Jayasundara
>>> >>  wrote:
>>> >>>
>>> >>> Sure I'll be there around 1.pm.
>>> >>>
>>> >>> On Thu, Jun 15, 2017 at 9:29 AM, Malaka Silva 
>>> wrote:
>>> 
>>>  Can you come around 1pm?
>>> 
>>>  On Thu, Jun 15, 2017 at 9:27 AM, Hasitha Jayasundara
>>>   wrote:
>>> >
>>> > Hi Malaka,
>>> >
>>> > Sorry for the late reply.I'll come by office tomorrow.What time do
>>> you
>>> > prefer?morning or evening?
>>> >
>>> > Thanks
>>> >
>>> > On Thu, Jun 15, 2017 at 8:09 AM, Malaka Silva 
>>> wrote:
>>> >>
>>> >> Hi Hasitha,
>>> >>
>>> >> When will you be arranging the meeting?
>>> >>
>>> >> On Tue, Jun 13, 2017 at 9:41 AM, Malaka Silva 
>>> wrote:
>>> >>>
>>> >>> +1
>>> >>>
>>> >>> On Tue, Jun 13, 2017 at 9:08 AM, Kevin Ratnasekera <
>>> ke...@wso2.com>
>>> >>> wrote:
>>> 
>>>  Hi Hasitha,
>>> 
>>>  I am fine with either of days if it works for Malaka as weill,
>>> 
>>>  @malaka can you please check?
>>> 
>>>  Regards
>>>  Kevin
>>> 
>>>  On Mon, Jun 12, 2017 at 8:53 AM, Hasitha Jayasundara
>>>   wrote:
>>> >
>>> > Hi all,
>>> >
>>> > Will it possible to arrange a meeting on Thursday or Friday
>>> this
>>> > week?
>>> >
>>> > Thanks
>>> >
>>> > On Wed, Jun 7, 2017 at 9:22 AM, Malaka Silva 
>>> > wrote:
>>> >>
>>> >> Sure No Worries
>>> >>
>>> >> On Wed, Jun 7, 2017 at 7:37 AM, Hasitha Jayasundara
>>> >>  wrote:
>>> >>>
>>> >>> Hi all,
>>> >>>
>>> >>> Can we please move the meeting to next week?.Got a problem
>>> with
>>> >>> Friday evening.Really sorry for the inconvenience caused.
>>> >>>
>>> >>> Thanks
>>> >>>
>>> >>> On Tue, Jun 6, 2017 at 10:24 AM, Malaka Silva <
>>> mal...@wso2.com>
>>> >>> wrote:
>>> 
>>>  +1 I'll be available after 13.00
>>> 
>>>  On Tue, Jun 6, 2017 at 10:00 AM, Kevin 

Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0

[Malaka Silva]

Hi Hasitha,

We will also create a git repo to maintain the code. Maheshika will provide
the required details.

On Tue, Jun 20, 2017 at 5:45 AM, Hasitha Jayasundara <
hasithajayasunda...@gmail.com> wrote:

> Hi all,
>
> Thanks for pointing out the above.I am doing a connector for IBM WebSphere
> MQ.What I was thinking about the inbound part is somewhat wrong.I missed
> this part "this should be added as an extension similar to [1]" from the
> beginning.Really sorry for the misunderstanding.
>
> 1. UI changes - Removed it from the milestone plan
> 2. Adding preferred authentications to the inbound - Really sorry for
> this.It should be preferred parameters for the inbound(polling)
>
> @Riyafa @Malaka Thanks for the kind help.I'll definitely call you if
> there's any issue.
>
> Thanks.
>
> [1].https://github.com/wso2-extensions/esb-inbound-amazonsqs
>
>
> On Mon, Jun 19, 2017 at 4:39 PM, Malaka Silva  wrote:
>
>> Hi Hasitha,
>>
>> Adding inbound endpoint to the carbon mediation and debugging
>>   You don't need to do this since this should be added as an extesnion
>> similar to [1]
>> Completing the user interface changes
>>You don't need to do any UI changes. It'll be handled by ESB/EI [2]
>> Adding preffered authentications to the inbound
>> Not clear what you mean by this?
>>
>> @Riyafa - Thx for pointing this out. I guess Hasitha got bit confused
>> with names. Anyway you should be doing a connector. Hasitha please
>> confirm this.
>>
>> Also if something is not clear feel free to call my mobile.
>>
>> [1] https://github.com/wso2-extensions/esb-inbound-amazonsqs
>> [2] https://docs.wso2.com/display/ESBCONNECTORS/Configuring+Amaz
>> onSQS+Streaming+Inbound+Endpoint+Operations
>>
>> On Mon, Jun 19, 2017 at 10:48 AM, Riyafa Abdul Hameed 
>> wrote:
>> > Hi,
>> >
>> > I am just curious if you would be writing a connector or a mediator.
>> >
>> > Regards,
>> > Riyafa
>> >
>> > On Mon, Jun 19, 2017 at 6:47 AM, Hasitha Jayasundara
>> >  wrote:
>> >>
>> >> Hi all,
>> >>
>> >> Please find updated milestone plan here.
>> >>
>> >>
>> >> https://docs.google.com/spreadsheets/d/19ijxAVHttxhLVuSJ0nfu
>> MUZ4x4lAD6ueYL5C3FNaFpg/edit?usp=sharing
>> >>
>> >> Thanks
>> >>
>> >> On Thu, Jun 15, 2017 at 9:30 AM, Hasitha Jayasundara
>> >>  wrote:
>> >>>
>> >>> Sure I'll be there around 1.pm.
>> >>>
>> >>> On Thu, Jun 15, 2017 at 9:29 AM, Malaka Silva 
>> wrote:
>> 
>>  Can you come around 1pm?
>> 
>>  On Thu, Jun 15, 2017 at 9:27 AM, Hasitha Jayasundara
>>   wrote:
>> >
>> > Hi Malaka,
>> >
>> > Sorry for the late reply.I'll come by office tomorrow.What time do
>> you
>> > prefer?morning or evening?
>> >
>> > Thanks
>> >
>> > On Thu, Jun 15, 2017 at 8:09 AM, Malaka Silva 
>> wrote:
>> >>
>> >> Hi Hasitha,
>> >>
>> >> When will you be arranging the meeting?
>> >>
>> >> On Tue, Jun 13, 2017 at 9:41 AM, Malaka Silva 
>> wrote:
>> >>>
>> >>> +1
>> >>>
>> >>> On Tue, Jun 13, 2017 at 9:08 AM, Kevin Ratnasekera <
>> ke...@wso2.com>
>> >>> wrote:
>> 
>>  Hi Hasitha,
>> 
>>  I am fine with either of days if it works for Malaka as weill,
>> 
>>  @malaka can you please check?
>> 
>>  Regards
>>  Kevin
>> 
>>  On Mon, Jun 12, 2017 at 8:53 AM, Hasitha Jayasundara
>>   wrote:
>> >
>> > Hi all,
>> >
>> > Will it possible to arrange a meeting on Thursday or Friday this
>> > week?
>> >
>> > Thanks
>> >
>> > On Wed, Jun 7, 2017 at 9:22 AM, Malaka Silva 
>> > wrote:
>> >>
>> >> Sure No Worries
>> >>
>> >> On Wed, Jun 7, 2017 at 7:37 AM, Hasitha Jayasundara
>> >>  wrote:
>> >>>
>> >>> Hi all,
>> >>>
>> >>> Can we please move the meeting to next week?.Got a problem
>> with
>> >>> Friday evening.Really sorry for the inconvenience caused.
>> >>>
>> >>> Thanks
>> >>>
>> >>> On Tue, Jun 6, 2017 at 10:24 AM, Malaka Silva <
>> mal...@wso2.com>
>> >>> wrote:
>> 
>>  +1 I'll be available after 13.00
>> 
>>  On Tue, Jun 6, 2017 at 10:00 AM, Kevin Ratnasekera
>>   wrote:
>> >
>> > +1
>> >
>> > On Tue, Jun 6, 2017 at 9:51 AM, Hasitha Jayasundara
>> >  wrote:
>> >>
>> >> Hi all,
>> >>
>> >> Friday afternoon fine me with.Any suggestions?
>> >>
>> >> On Mon, Jun 5, 2017 at 9:30 

Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0

[Hasitha Jayasundara]

Hi all,

Thanks for pointing out the above.I am doing a connector for IBM WebSphere
MQ.What I was thinking about the inbound part is somewhat wrong.I missed
this part "this should be added as an extension similar to [1]" from the
beginning.Really sorry for the misunderstanding.

1. UI changes - Removed it from the milestone plan
2. Adding preferred authentications to the inbound - Really sorry for
this.It should be preferred parameters for the inbound(polling)

@Riyafa @Malaka Thanks for the kind help.I'll definitely call you if
there's any issue.

Thanks.

[1].https://github.com/wso2-extensions/esb-inbound-amazonsqs


On Mon, Jun 19, 2017 at 4:39 PM, Malaka Silva  wrote:

> Hi Hasitha,
>
> Adding inbound endpoint to the carbon mediation and debugging
>   You don't need to do this since this should be added as an extesnion
> similar to [1]
> Completing the user interface changes
>You don't need to do any UI changes. It'll be handled by ESB/EI [2]
> Adding preffered authentications to the inbound
> Not clear what you mean by this?
>
> @Riyafa - Thx for pointing this out. I guess Hasitha got bit confused
> with names. Anyway you should be doing a connector. Hasitha please
> confirm this.
>
> Also if something is not clear feel free to call my mobile.
>
> [1] https://github.com/wso2-extensions/esb-inbound-amazonsqs
> [2] https://docs.wso2.com/display/ESBCONNECTORS/Configuring+
> AmazonSQS+Streaming+Inbound+Endpoint+Operations
>
> On Mon, Jun 19, 2017 at 10:48 AM, Riyafa Abdul Hameed 
> wrote:
> > Hi,
> >
> > I am just curious if you would be writing a connector or a mediator.
> >
> > Regards,
> > Riyafa
> >
> > On Mon, Jun 19, 2017 at 6:47 AM, Hasitha Jayasundara
> >  wrote:
> >>
> >> Hi all,
> >>
> >> Please find updated milestone plan here.
> >>
> >>
> >> https://docs.google.com/spreadsheets/d/19ijxAVHttxhLVuSJ0nfuMUZ4x4lAD
> 6ueYL5C3FNaFpg/edit?usp=sharing
> >>
> >> Thanks
> >>
> >> On Thu, Jun 15, 2017 at 9:30 AM, Hasitha Jayasundara
> >>  wrote:
> >>>
> >>> Sure I'll be there around 1.pm.
> >>>
> >>> On Thu, Jun 15, 2017 at 9:29 AM, Malaka Silva  wrote:
> 
>  Can you come around 1pm?
> 
>  On Thu, Jun 15, 2017 at 9:27 AM, Hasitha Jayasundara
>   wrote:
> >
> > Hi Malaka,
> >
> > Sorry for the late reply.I'll come by office tomorrow.What time do
> you
> > prefer?morning or evening?
> >
> > Thanks
> >
> > On Thu, Jun 15, 2017 at 8:09 AM, Malaka Silva 
> wrote:
> >>
> >> Hi Hasitha,
> >>
> >> When will you be arranging the meeting?
> >>
> >> On Tue, Jun 13, 2017 at 9:41 AM, Malaka Silva 
> wrote:
> >>>
> >>> +1
> >>>
> >>> On Tue, Jun 13, 2017 at 9:08 AM, Kevin Ratnasekera  >
> >>> wrote:
> 
>  Hi Hasitha,
> 
>  I am fine with either of days if it works for Malaka as weill,
> 
>  @malaka can you please check?
> 
>  Regards
>  Kevin
> 
>  On Mon, Jun 12, 2017 at 8:53 AM, Hasitha Jayasundara
>   wrote:
> >
> > Hi all,
> >
> > Will it possible to arrange a meeting on Thursday or Friday this
> > week?
> >
> > Thanks
> >
> > On Wed, Jun 7, 2017 at 9:22 AM, Malaka Silva 
> > wrote:
> >>
> >> Sure No Worries
> >>
> >> On Wed, Jun 7, 2017 at 7:37 AM, Hasitha Jayasundara
> >>  wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Can we please move the meeting to next week?.Got a problem with
> >>> Friday evening.Really sorry for the inconvenience caused.
> >>>
> >>> Thanks
> >>>
> >>> On Tue, Jun 6, 2017 at 10:24 AM, Malaka Silva  >
> >>> wrote:
> 
>  +1 I'll be available after 13.00
> 
>  On Tue, Jun 6, 2017 at 10:00 AM, Kevin Ratnasekera
>   wrote:
> >
> > +1
> >
> > On Tue, Jun 6, 2017 at 9:51 AM, Hasitha Jayasundara
> >  wrote:
> >>
> >> Hi all,
> >>
> >> Friday afternoon fine me with.Any suggestions?
> >>
> >> On Mon, Jun 5, 2017 at 9:30 AM, Malaka Silva <
> mal...@wso2.com>
> >> wrote:
> >>>
> >>> Wednesday morning or Friday afternoon fine with me.
> >>>
> >>> On Mon, Jun 5, 2017 at 9:26 AM, Kevin Ratnasekera
> >>>  wrote:
> 
>  Hi Hasitha,
> 
>  Great 

Re: [Dev] Isseues

[Johann Nallathamby]

Hi Lipsa,

The dev community doesn't generally encourage having one-on-one
conversations for issues. Generally all issues are discussed in the this
mailing list publicly. Unless it's a special discussion on a certain way a
feature must be designed/implemented/etc. the community may opt for a web
conference; but that also could happen mostly in the architecture list; not
in the dev list. Please send your questions to this list itself. Generally
you would receive much swifter responses because there is a group of people
watching this list.

However if you feel that you are not receiving fast enough responses,
because the questions are too specific to your use case, or not something
that is supported out of the box from the product and something that is not
documented as available in the product, then I would encourage you to
contact WSO2 support [1] in order to get all your questions answered with
guaranteed SLAs.

[1] http://wso2.com/support/

Regards,
Johann.

On Mon, Jun 19, 2017 at 12:43 PM, Lipsa Pradhan  wrote:

> I have many doubts. Can I have someone's mail ID or contact number to have
> a one-on-one conversation.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Senior Technical Lead - WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Madhawa Perera

[Menaka Jayawardena]

Congratulations Madhawa!

On Mon, Jun 19, 2017 at 4:45 PM, Chathura Dilan  wrote:

> Hi All,
>
> It's my pleasure to welcome Madhawa Perera as a WSO2 Committer.
>
> Madhawa has been a valuable contributor to the IoT team. In recognition
> of his contribution, dedication, and commitment he has been voted as a
> WSO2 committer.
>
> Madhawa, welcome aboard and keep up the good work!
>
> --
> Thanks and Best Regards,
>
> Chatura Dilan Perera
> *Associate Tech Lead** - WSO2 Inc.*
> +94777266673
> www.dilan.me
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
*
*Blog: https://menakamadushanka.wordpress.com/
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Problem in authentication

[Lipsa Pradhan]

Hello

I am using Enterprise Integrator. I want to authorise customised users,
using authentication service to have access tokens. I had tried "proxy
service" method for this. But it isn't working.

How can I do this?


I'm getting this while firing the proxy service.

http://www.w3.org/2003/05/soap-envelope;
xmlns:axis2ns7="http://www.w3.org/2003/05/soap-envelope;>
  
  axis2ns7:Sender
  
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;>wsse:InvalidSecurity
  


  Expected transport is "https" but
incoming transport found : "http" 



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

[Dev] WSO2 Committers += Madhawa Perera

[Chathura Dilan]

Hi All,

It's my pleasure to welcome Madhawa Perera as a WSO2 Committer.

Madhawa has been a valuable contributor to the IoT team. In recognition of
his contribution, dedication, and commitment he has been voted as a WSO2
 committer.

Madhawa, welcome aboard and keep up the good work!

-- 
Thanks and Best Regards,

Chatura Dilan Perera
*Associate Tech Lead** - WSO2 Inc.*
+94777266673
www.dilan.me
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0

[Malaka Silva]

Hi Hasitha,

Adding inbound endpoint to the carbon mediation and debugging
  You don't need to do this since this should be added as an extesnion
similar to [1]
Completing the user interface changes
   You don't need to do any UI changes. It'll be handled by ESB/EI [2]
Adding preffered authentications to the inbound
Not clear what you mean by this?

@Riyafa - Thx for pointing this out. I guess Hasitha got bit confused
with names. Anyway you should be doing a connector. Hasitha please
confirm this.

Also if something is not clear feel free to call my mobile.

[1] https://github.com/wso2-extensions/esb-inbound-amazonsqs
[2] 
https://docs.wso2.com/display/ESBCONNECTORS/Configuring+AmazonSQS+Streaming+Inbound+Endpoint+Operations

On Mon, Jun 19, 2017 at 10:48 AM, Riyafa Abdul Hameed  wrote:
> Hi,
>
> I am just curious if you would be writing a connector or a mediator.
>
> Regards,
> Riyafa
>
> On Mon, Jun 19, 2017 at 6:47 AM, Hasitha Jayasundara
>  wrote:
>>
>> Hi all,
>>
>> Please find updated milestone plan here.
>>
>>
>> https://docs.google.com/spreadsheets/d/19ijxAVHttxhLVuSJ0nfuMUZ4x4lAD6ueYL5C3FNaFpg/edit?usp=sharing
>>
>> Thanks
>>
>> On Thu, Jun 15, 2017 at 9:30 AM, Hasitha Jayasundara
>>  wrote:
>>>
>>> Sure I'll be there around 1.pm.
>>>
>>> On Thu, Jun 15, 2017 at 9:29 AM, Malaka Silva  wrote:

 Can you come around 1pm?

 On Thu, Jun 15, 2017 at 9:27 AM, Hasitha Jayasundara
  wrote:
>
> Hi Malaka,
>
> Sorry for the late reply.I'll come by office tomorrow.What time do you
> prefer?morning or evening?
>
> Thanks
>
> On Thu, Jun 15, 2017 at 8:09 AM, Malaka Silva  wrote:
>>
>> Hi Hasitha,
>>
>> When will you be arranging the meeting?
>>
>> On Tue, Jun 13, 2017 at 9:41 AM, Malaka Silva  wrote:
>>>
>>> +1
>>>
>>> On Tue, Jun 13, 2017 at 9:08 AM, Kevin Ratnasekera 
>>> wrote:

 Hi Hasitha,

 I am fine with either of days if it works for Malaka as weill,

 @malaka can you please check?

 Regards
 Kevin

 On Mon, Jun 12, 2017 at 8:53 AM, Hasitha Jayasundara
  wrote:
>
> Hi all,
>
> Will it possible to arrange a meeting on Thursday or Friday this
> week?
>
> Thanks
>
> On Wed, Jun 7, 2017 at 9:22 AM, Malaka Silva 
> wrote:
>>
>> Sure No Worries
>>
>> On Wed, Jun 7, 2017 at 7:37 AM, Hasitha Jayasundara
>>  wrote:
>>>
>>> Hi all,
>>>
>>> Can we please move the meeting to next week?.Got a problem with
>>> Friday evening.Really sorry for the inconvenience caused.
>>>
>>> Thanks
>>>
>>> On Tue, Jun 6, 2017 at 10:24 AM, Malaka Silva 
>>> wrote:

 +1 I'll be available after 13.00

 On Tue, Jun 6, 2017 at 10:00 AM, Kevin Ratnasekera
  wrote:
>
> +1
>
> On Tue, Jun 6, 2017 at 9:51 AM, Hasitha Jayasundara
>  wrote:
>>
>> Hi all,
>>
>> Friday afternoon fine me with.Any suggestions?
>>
>> On Mon, Jun 5, 2017 at 9:30 AM, Malaka Silva 
>> wrote:
>>>
>>> Wednesday morning or Friday afternoon fine with me.
>>>
>>> On Mon, Jun 5, 2017 at 9:26 AM, Kevin Ratnasekera
>>>  wrote:

 Hi Hasitha,

 Great progress so far, since the coding period have already
 started, we need to plan things ahead and come up with a 
 proper milestone
 plan before we proceed anything further. Will it be possible 
 you to join a
 meeting within this week?

 @malaka Can you please suggest possible time for you to have
 a meeting?

 Regards
 Kevin

 On Mon, May 29, 2017 at 10:34 AM, Hasitha Jayasundara
  wrote:
>
> Hi all,
>
> I have updated the sample MQ-Client [1] to establish SSL
> connections with IBM WebSphere MQ. Still carry on the 
> research with the
> provided links about the IBM specific options that can be 

[Dev] [APIM] Terminate SSL connection at ELB

[Chamara Philips]

Hi Devs,

What is the procedure to terminate the SSL connection at the ELB with WSO2
APIM? Client calls the ELB through HTTPS and that requires the ELB to have
a CA. But the connection from ELB to APIM should use HTTP. (ELB and APIM
are in the same VPC. I am under the impression that there would be no
additional security issues introduced because of this approach since the
ELB and WSO2 Server are both in the same VPC. Please correct me if it isn't)

What configurations should be set for the above approach?

Thanks & Regards
-- 
-- 
Hareendra Chamara (BSc.Eng(Hons))
Sysco acceleration,
SyscoLabs(Pvt) Ltd
Mobile : +94 (0) 767 184161 <94767184161> | +65 (9) 425 2874 <6594252874>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Problem when creating APIs

[Thomas LEGRAND]

Hello again!

I did not know how to fix this so I recreated a clean instance of the API
Manager to plug it to my Identity Server and I can enjoy the API creation
again!

Maybe that was because my API was created before the implementation of the
connectivity between the AM and the IS.

It is more a workaround than a fix but...meh :)

Regards,

Thomas

2017-06-16 15:57 GMT+02:00 Thomas LEGRAND :

> Hello,
>
> Since I make the IS and the AM work together, I have so many problems.
> This time, it became impossible to create APIs via the AM because, when I
> reach the "Implement" step, I can't set my Production & Sandbox endpoints:
>
> [image: Images intégrées 1]
> And if I click on "Next: Manage >", I have a JSON error appearing:
>
> {"error" : true, "message" : " Invalid Endpoint config", "data" :
>> {"apiName" : "MyAPI", "version" : "1.0.0", "provider" : "admin"}}
>
>
> So I try to define a valid endpoint in the "Prototyped API" part in the
> previous screen:
>
> [image: Images intégrées 2]
>
> And I continue via the same button "Next: Manage >" and BOOM. Same message
> :(
>
>
> Is there something special to configure?
>
> Regards,
>
> Thomas
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Isseues

[Lipsa Pradhan]

I have many doubts. Can I have someone's mail ID or contact number to have
a one-on-one conversation.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev