Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager 3.2.0 RC1

[Dinusha Senanayaka]

Hi Arshardh,

Could you please point the 3.2.0 migration doc as well ?

Regards,
Dinusha

On Fri, Jul 31, 2020 at 11:25 PM Arshardh Ifthikar 
wrote:

> Hi all,
>
> We are pleased to announce the first release candidate of WSO2 API Manager
> 3.2.0.
>
> This release fixes the following issues.
>
>- Fixes : product-apim
>
> <https://github.com/wso2/product-apim/issues?q=is%3Aissue+is%3Aclosed+closed%3A2020-03-20..2020-07-31>
>- Fixes : analytics-apim
><https://github.com/wso2/analytics-apim/milestone/26?closed=1>
>
> Source and distribution,
> Runtime : https://github.com/wso2/product-apim/releases/tag/v3.2.0-rc1
> Analytics :
> https://github.com/wso2/analytics-apim/releases/tag/v3.2.0-rc1
>
> Documentation : https://apim.docs.wso2.com/en/3.2.0/
>
> Please download, test the product and vote.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> WSO2 API Manager Team
>
> --
> *Arshardh Ifthikar*
> Senior Software Engineer | WSO2 Inc.
>
> Email: arsha...@wso2.com
> Mobile: +94777218551
> Web: http://wso2.com
>
> <http://wso2.com/signature>
>


-- 
Dinusha Senanayaka
Senior Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94764069991
LinkedIn : https://www.linkedin.com/in/dinushasenanayaka/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Unable to build the Micro Gateway distribution using the command in the documentation

[Dinusha Senanayaka]

Malintha, can you please fix the label name to be consistent in the sample.
In the publisher, label is given as "MRKETING_STORE", but in  setup and
build commands label is used as "Internal"  which is kind of confusing.
Better if we an keep label as "MRKETING_STORE" for all the places.

Regards,
Dinusha

On Fri, Jun 29, 2018 at 8:22 AM Malintha Amarasinghe 
wrote:

> Thanks for reporting this Iloshini. I have fixed the documentation.
>
> Thanks!
>
>
> On Thu, Jun 28, 2018 at 10:38 PM, Iloshini Karunarathne  > wrote:
>
>> Hi All,
>>
>> There is an issue when building the micro-gateway distribution by using
>> the command, *micro-gw build -l internal* in the documentation [1].
>> Found that the source files haven't built and the target folder is empty.
>>
>> As per the source code, the command should be *micro-gw build -n
>> internal *and able to successfully build the micro-gateway distribution
>> using this command.
>>
>> This issue occurs when using the APIM Micro Gateway *Beta release* and
>> IMHO it will be better if we can update the documentation [1] accordingly.
>>
>>
>> [1]. https://docs.wso2.com/display/AM2xx/Configuring+the+API+Microgateway
>>
>> Thanks,
>> Iloshini
>>
>> Regards,
>>
>> *Iloshini Karunarathne*
>>
>> *Software Engineer | Support Team*
>> *WSO2*
>>
>> Email : ilosh...@wso2.com
>> Mobile : +94719821300
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 Documentation Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to documentation+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>
>
> --
> Malintha Amarasinghe
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>


-- 
Dinusha Dilrukshi
Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94764069991
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Unable to run micro-gw generated balx file

[Dinusha Senanayaka]

Thanks Malintha/Nuwan. Had no specific use case to run .balx with standard
ballerina distribution. Was just trying different stuff. Will use the
script provided with distribution.

Regards,
Dinusha

On Wed, Jun 27, 2018 at 5:36 PM Nuwan Dias  wrote:

> We will be getting rid of the .balx file generated outside the project
> directory. Therefore it would be best if you could extract the .zip file
> that's generated and run the program via the provided bash script.
>
> On Wed, Jun 27, 2018 at 5:03 PM Dinusha Senanayaka 
> wrote:
>
>>
>> Hi Malintha,
>>
>> On Wed, Jun 27, 2018 at 4:57 PM Malintha Amarasinghe 
>> wrote:
>>
>>> Hi Dinusha,
>>>
>>> It should work, basically the shell script created inside the
>>> distribution (distribution/micro-gw-marketing_store/bin/micro_gw.sh)
>>> also doing a ballerina run command.
>>>
>>> Does running the above file (./micro_gw.sh) work?
>>>
>> Yes,  that works.
>>
>>> If it works, the ballerina runtime installed in your machine may be not
>>> matching with the balx file generated here. Please check with "ballerina
>>> --version"
>>>
>> 0.970.1. What should be the ballerina version relevant to  micro-gw alpha
>> release ?
>>
>> Regards,
>> Dinusha
>>
>>>
>>> Thanks!
>>>
>>> On Wed, Jun 27, 2018 at 4:01 PM, Dinusha Senanayaka 
>>> wrote:
>>>
>>>> Hi APIM team,
>>>>
>>>> I'm trying to run micro-gw build generated balx file as a separate
>>>> ballerina program and getting following error. Is that something possible ?
>>>> Any idea on what could be wrong here ?
>>>>
>>>> Tried to execute the balx file in project's target directory and then
>>>> the one in "target/distribution/micro-gw-marketing_store/exec" directory.
>>>>
>>>> projects/marketing_store/target/distribution/micro-gw-marketing_store/exec$
>>>> *tree*
>>>> .
>>>> ├── ballerina-internal.log
>>>> └── marketing_store.balx
>>>>
>>>> $ *ballerina run marketing_store.balx --config ../conf/micro-gw.conf *
>>>> ballerina: Oh no, something really went wrong. Bad. Sad.
>>>>
>>>> *There should be a file named "ballerina-internal.log" in the current
>>>> directory.*
>>>> If you are able to share with us the code that broke Ballerina then
>>>> we would REALLY appreciate if you would report this to us:
>>>> go to https://github.com/ballerina-platform/ballerina-lang/issues and
>>>> create a bug report with both this log file and the sample code.
>>>>
>>>> Following exception can be seen in "ballerina-internal.log" file.
>>>>
>>>> ERROR {org.ballerinalang.launcher.Main} - ballerina: invalid program
>>>> file format
>>>> org.ballerinalang.util.exceptions.ProgramFileFormatException:
>>>> ballerina: invalid program file format
>>>> at org.ballerinalang.BLangProgramLoader.read(BLangProgramLoader.java:46)
>>>> at
>>>> org.ballerinalang.launcher.LauncherUtils.runProgram(LauncherUtils.java:82)
>>>> at org.ballerinalang.launcher.Main$RunCmd.execute(Main.java:256)
>>>> at java.util.Optional.ifPresent(Optional.java:159)
>>>> at org.ballerinalang.launcher.Main.main(Main.java:66)
>>>> Caused by: java.lang.IndexOutOfBoundsException: Index: 33554432, Size:
>>>> 125
>>>> at java.util.ArrayList.rangeCheck(ArrayList.java:657)
>>>> at java.util.ArrayList.get(ArrayList.java:433)
>>>> at
>>>> org.ballerinalang.util.codegen.PackageInfo.getCPEntry(PackageInfo.java:103)
>>>> at
>>>> org.ballerinalang.util.codegen.ProgramFileReader.getAttributeInfo(ProgramFileReader.java:1143)
>>>> at
>>>> org.ballerinalang.util.codegen.ProgramFileReader.readAttributeInfoEntries(ProgramFileReader.java:1133)
>>>> at
>>>> org.ballerinalang.util.codegen.ProgramFileReader.readStructInfoEntries(ProgramFileReader.java:497)
>>>> at
>>>> org.ballerinalang.util.codegen.ProgramFileReader.readPackageInfo(ProgramFileReader.java:377)
>>>> at
>>>> org.ballerinalang.util.codegen.ProgramFileReader.readProgramInternal(ProgramFileReader.java:159)
>>>> at
>>>> org.ballerinalang.util.codegen.ProgramFileReader.readProgram(ProgramFileReader.java:126)
>>>> at org.ballerinalang.BLangProgramLoader.read(BLangProgramLoader.java:39)
>

Re: [Dev] [APIM] Unable to run micro-gw generated balx file

[Dinusha Senanayaka]

Hi Malintha,

On Wed, Jun 27, 2018 at 4:57 PM Malintha Amarasinghe 
wrote:

> Hi Dinusha,
>
> It should work, basically the shell script created inside the distribution
> (distribution/micro-gw-marketing_store/bin/micro_gw.sh) also doing a
> ballerina run command.
>
> Does running the above file (./micro_gw.sh) work?
>
Yes,  that works.

> If it works, the ballerina runtime installed in your machine may be not
> matching with the balx file generated here. Please check with "ballerina
> --version"
>
0.970.1. What should be the ballerina version relevant to  micro-gw alpha
release ?

Regards,
Dinusha

>
> Thanks!
>
> On Wed, Jun 27, 2018 at 4:01 PM, Dinusha Senanayaka 
> wrote:
>
>> Hi APIM team,
>>
>> I'm trying to run micro-gw build generated balx file as a separate
>> ballerina program and getting following error. Is that something possible ?
>> Any idea on what could be wrong here ?
>>
>> Tried to execute the balx file in project's target directory and then the
>> one in "target/distribution/micro-gw-marketing_store/exec" directory.
>>
>> projects/marketing_store/target/distribution/micro-gw-marketing_store/exec$
>> *tree*
>> .
>> ├── ballerina-internal.log
>> └── marketing_store.balx
>>
>> $ *ballerina run marketing_store.balx --config ../conf/micro-gw.conf *
>> ballerina: Oh no, something really went wrong. Bad. Sad.
>>
>> *There should be a file named "ballerina-internal.log" in the current
>> directory.*
>> If you are able to share with us the code that broke Ballerina then
>> we would REALLY appreciate if you would report this to us:
>> go to https://github.com/ballerina-platform/ballerina-lang/issues and
>> create a bug report with both this log file and the sample code.
>>
>> Following exception can be seen in "ballerina-internal.log" file.
>>
>> ERROR {org.ballerinalang.launcher.Main} - ballerina: invalid program
>> file format
>> org.ballerinalang.util.exceptions.ProgramFileFormatException: ballerina:
>> invalid program file format
>> at org.ballerinalang.BLangProgramLoader.read(BLangProgramLoader.java:46)
>> at
>> org.ballerinalang.launcher.LauncherUtils.runProgram(LauncherUtils.java:82)
>> at org.ballerinalang.launcher.Main$RunCmd.execute(Main.java:256)
>> at java.util.Optional.ifPresent(Optional.java:159)
>> at org.ballerinalang.launcher.Main.main(Main.java:66)
>> Caused by: java.lang.IndexOutOfBoundsException: Index: 33554432, Size: 125
>> at java.util.ArrayList.rangeCheck(ArrayList.java:657)
>> at java.util.ArrayList.get(ArrayList.java:433)
>> at
>> org.ballerinalang.util.codegen.PackageInfo.getCPEntry(PackageInfo.java:103)
>> at
>> org.ballerinalang.util.codegen.ProgramFileReader.getAttributeInfo(ProgramFileReader.java:1143)
>> at
>> org.ballerinalang.util.codegen.ProgramFileReader.readAttributeInfoEntries(ProgramFileReader.java:1133)
>> at
>> org.ballerinalang.util.codegen.ProgramFileReader.readStructInfoEntries(ProgramFileReader.java:497)
>> at
>> org.ballerinalang.util.codegen.ProgramFileReader.readPackageInfo(ProgramFileReader.java:377)
>> at
>> org.ballerinalang.util.codegen.ProgramFileReader.readProgramInternal(ProgramFileReader.java:159)
>> at
>> org.ballerinalang.util.codegen.ProgramFileReader.readProgram(ProgramFileReader.java:126)
>> at org.ballerinalang.BLangProgramLoader.read(BLangProgramLoader.java:39)
>> ... 4 more
>>
>> Regards,
>> Dinusha
>>
>> --
>> Dinusha Dilrukshi
>> Technical Lead
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94764069991
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
> Malintha Amarasinghe
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>


-- 
Dinusha Dilrukshi
Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94764069991
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] Unable to run micro-gw generated balx file

[Dinusha Senanayaka]

Hi APIM team,

I'm trying to run micro-gw build generated balx file as a separate
ballerina program and getting following error. Is that something possible ?
Any idea on what could be wrong here ?

Tried to execute the balx file in project's target directory and then the
one in "target/distribution/micro-gw-marketing_store/exec" directory.

projects/marketing_store/target/distribution/micro-gw-marketing_store/exec$
*tree*
.
├── ballerina-internal.log
└── marketing_store.balx

$ *ballerina run marketing_store.balx --config ../conf/micro-gw.conf *
ballerina: Oh no, something really went wrong. Bad. Sad.

*There should be a file named "ballerina-internal.log" in the current
directory.*
If you are able to share with us the code that broke Ballerina then
we would REALLY appreciate if you would report this to us:
go to https://github.com/ballerina-platform/ballerina-lang/issues and
create a bug report with both this log file and the sample code.

Following exception can be seen in "ballerina-internal.log" file.

ERROR {org.ballerinalang.launcher.Main} - ballerina: invalid program file
format
org.ballerinalang.util.exceptions.ProgramFileFormatException: ballerina:
invalid program file format
at org.ballerinalang.BLangProgramLoader.read(BLangProgramLoader.java:46)
at
org.ballerinalang.launcher.LauncherUtils.runProgram(LauncherUtils.java:82)
at org.ballerinalang.launcher.Main$RunCmd.execute(Main.java:256)
at java.util.Optional.ifPresent(Optional.java:159)
at org.ballerinalang.launcher.Main.main(Main.java:66)
Caused by: java.lang.IndexOutOfBoundsException: Index: 33554432, Size: 125
at java.util.ArrayList.rangeCheck(ArrayList.java:657)
at java.util.ArrayList.get(ArrayList.java:433)
at
org.ballerinalang.util.codegen.PackageInfo.getCPEntry(PackageInfo.java:103)
at
org.ballerinalang.util.codegen.ProgramFileReader.getAttributeInfo(ProgramFileReader.java:1143)
at
org.ballerinalang.util.codegen.ProgramFileReader.readAttributeInfoEntries(ProgramFileReader.java:1133)
at
org.ballerinalang.util.codegen.ProgramFileReader.readStructInfoEntries(ProgramFileReader.java:497)
at
org.ballerinalang.util.codegen.ProgramFileReader.readPackageInfo(ProgramFileReader.java:377)
at
org.ballerinalang.util.codegen.ProgramFileReader.readProgramInternal(ProgramFileReader.java:159)
at
org.ballerinalang.util.codegen.ProgramFileReader.readProgram(ProgramFileReader.java:126)
at org.ballerinalang.BLangProgramLoader.read(BLangProgramLoader.java:39)
... 4 more

Regards,
Dinusha

-- 
Dinusha Dilrukshi
Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94764069991
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Error when trying to setup micro-gw

[Dinusha Senanayaka]

Thanks Dinusha/Harsha. Build distribution has been created in target even
that error was there.

Regards,
Dinusha

On Tue, Jun 26, 2018 at 11:27 AM, Harsha Kumara  wrote:

>
>
> On Tue, Jun 26, 2018 at 11:14 AM Dinusha Senanayaka 
> wrote:
>
>> Hi APIM team,
>>
>> Executed following command as per  doc [2]  to build generated source and
>> got error [1]. Do we need to include any libraries ? (using micro-gw alpha
>> release).
>>
>> micro-gw build -l marketing_store
>>
>>
>> [1]  could not find package wso2/gateway:*
>>
> This is harmless. I believe this is because packages not in the ballerina
> central as build try to pull these packages.  Build command will execute
> fine and distribution should be created.
>
>>
>> [2] https://docs.wso2.com/display/AM2xx/Configuring+the+API+Microgateway#
>> ConfiguringtheAPIMicrogateway-GeneratingaMicrogatewaydistribution
>>
>> Regards,
>> Dinusha
>>
>> --
>> Dinusha Dilrukshi
>> Technical Lead
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94764069991
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
> --
> Harsha Kumara
> Associate Technical Lead, WSO2 Inc.
> Mobile: +94775505618
> Blog:harshcreationz.blogspot.com
>



-- 
Dinusha Dilrukshi
Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94764069991
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] Error when trying to setup micro-gw

[Dinusha Senanayaka]

Hi APIM team,

Executed following command as per  doc [2]  to build generated source and
got error [1]. Do we need to include any libraries ? (using micro-gw alpha
release).

micro-gw build -l marketing_store


[1]  could not find package wso2/gateway:*

[2]
https://docs.wso2.com/display/AM2xx/Configuring+the+API+Microgateway#ConfiguringtheAPIMicrogateway-GeneratingaMicrogatewaydistribution

Regards,
Dinusha

-- 
Dinusha Dilrukshi
Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94764069991
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge PR

[Dinusha Senanayaka]

On Thu, Feb 22, 2018 at 10:29 AM, SajithAR Ariyarathna 
wrote:

> Hi Devs,
>
> Please review & merged PR https://github.com/wso2/carbon-appmgt/pull/709
> which fixes https://github.com/wso2/carbon-appmgt/issues/708 .
>

Merged.

Regards,
Dinusha

>
> Thanks.
>
> --
> Sajith Janaprasad Ariyarathna
> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> 
>



-- 
Dinusha Dilrukshi
Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94764069991
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need to change the type of some variables to make the Identity Server, OIDC compliant.

[Dinusha Senanayaka]

Even though it's a spec violation (that we have made), there can be current
production applications which they cannot change or need complete process
to change them. In such scenario, migration to new IS version will be
blocked, even they having other needs of migrating to new version. Also as
a best practice migrations in middle layer should not cause changes to end
applications. If we keep a property, it will be helpful to handle such
situations right. Anyway, yeah agree that if it's a rare scenario we can
ignore it.

Regards,
Dinusha

On Wed, Sep 20, 2017 at 2:01 PM, Sagara Gunathunga <sag...@wso2.com> wrote:

>
>
> On Wed, Sep 20, 2017 at 1:44 PM, Johann Nallathamby <joh...@wso2.com>
> wrote:
>
>> I would like to see others comments also.
>>
>> Since this is a spec violation do we need to be backward compatible? I
>> would say we don't have to be. But I know we can have users who want like
>> it to be a breaking change. So it's important what other IAM members think.
>>
>
> I have 2 points on this
>
> 1. According  to OIDC spec this is a bug so we have to fix it.
>
> 2. The real meaning of  backward compatibility through  a property is,
>  there is a mode that IS continues to return a invalid  content.  IMO it's
> ok to break the clients who depend on invalid content, when they upgrade to
> newer version  of IS they have to change those logic as migration step.
>
> Thanks !
>
>>
>> If we need to have a property we can have a blanket property for all such
>> backward incompatible changes in IS 5.4.0 and allow the user to configure,
>> without having one property for each change.
>>
>> Regards,
>> Johann.
>>
>> On Wed, Sep 20, 2017 at 1:40 PM, Dinusha Senanayaka <dinu...@wso2.com>
>> wrote:
>>
>>> Yes, this can break existing clients which has parsed current id_token
>>> and using these two values. One option is to introduce a new config to keep
>>> the old format of id_token and if the config value is switched, we support
>>> for the new format which is compliance for OIDC specification. We can
>>> deprecate supporting for old format after few releases.
>>>
>>> Regards,
>>> Dinusha
>>>
>>> On Wed, Sep 20, 2017 at 9:26 AM, Hasini Witharana <hasi...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> OIDC test suite has been updated and now new issues have come in basic
>>>> profile (where response_type=code). The issues are given below.
>>>>
>>>> 1. OP-scope-email
>>>>  In here email_verified is returned as a string in id_token and it
>>>> should be a boolean value.
>>>>
>>>> 2. OP-scope-phone
>>>>  In here phone_number_verified is returned as a string in id_token
>>>> and it should be a booleanvalue.
>>>>
>>>> If we change these parameters to return boolean values, will the
>>>> existing users get effected by that?
>>>>
>>>> Thank you.
>>>> --
>>>>
>>>> *Hasini Witharana*
>>>> Software Engineering Intern | WSO2
>>>>
>>>>
>>>> *Email : hasi...@wso2.com <hasi...@wso2.com>*
>>>>
>>>> *Mobile : +94713850143 <071%20385%200143>[image:
>>>> http://wso2.com/signature] <http://wso2.com/signature>*
>>>>
>>>
>>>
>>>
>>> --
>>> Dinusha Dilrukshi
>>> Technical Lead
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94764069991 <+94%2076%20406%209991>
>>> Blog: http://dinushasblog.blogspot.com/
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Johann Dilantha Nallathamby*
>> Senior Lead Solutions Engineer
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - *+9476950*
>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sagara Gunathunga
>
> Director; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


-- 
Dinusha Dilrukshi
Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94764069991
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need to change the type of some variables to make the Identity Server, OIDC compliant.

[Dinusha Senanayaka]

Yes, this can break existing clients which has parsed current id_token and
using these two values. One option is to introduce a new config to keep the
old format of id_token and if the config value is switched, we support for
the new format which is compliance for OIDC specification. We can deprecate
supporting for old format after few releases.

Regards,
Dinusha

On Wed, Sep 20, 2017 at 9:26 AM, Hasini Witharana  wrote:

> Hi,
>
> OIDC test suite has been updated and now new issues have come in basic
> profile (where response_type=code). The issues are given below.
>
> 1. OP-scope-email
>  In here email_verified is returned as a string in id_token and it
> should be a boolean value.
>
> 2. OP-scope-phone
>  In here phone_number_verified is returned as a string in id_token and
> it should be a booleanvalue.
>
> If we change these parameters to return boolean values, will the existing
> users get effected by that?
>
> Thank you.
> --
>
> *Hasini Witharana*
> Software Engineering Intern | WSO2
>
>
> *Email : hasi...@wso2.com *
>
> *Mobile : +94713850143 <071%20385%200143>[image:
> http://wso2.com/signature] *
>



-- 
Dinusha Dilrukshi
Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94764069991
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Dynamic zip file download from Jaggery application

[Dinusha Senanayaka]

We have done something similar in AppM for mobile apps where publisher
uploads binary (.apk etc) and users comes to store install these apps to
device.  Download has handled as a byte stream and storage location is
stored in property of app-manger.xml
(${carbon.home}/repository/resources/mobileapps/)
and HostObject method has been provided to get the location.

@Chathura should be able to explain the logic more since he implemented
this.

Regards,
Dinusha.

On Mon, Oct 17, 2016 at 6:06 PM, Godwin Shrimal  wrote:

> Hi All,
>
> We need to dynamically create zip file and allow download it from jaggery
> application. For resolve the concurrent access of the system, we are going
> to create a directory with the time-stamp and archive that directory and
> allow user to download it. Then we need to create a separate cleanup task
> to clean those directories and archive files.
>
> We can create above zip files in jaggery application level (ex.
> jaggery/dashboard/resource/) and create a cleanup task in OSGI level to
> delete the files/directories periodically. Here we need to keep a configure
> to find the jaggery application context from OSGI level.
>
> Do we have a better approach for this or is it fine to use a configuration
> for particular jaggery context ?
>
> Thanks
> Godwin
>
> --
> *Godwin Amila Shrimal*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarification regarding carbon-appmgt permissions

[Dinusha Senanayaka]

On Wed, Oct 12, 2016 at 9:02 AM, Megala Uthayakumar <meg...@wso2.com> wrote:

> Hi Dinusha,
>
> Thanks for the response. For the time being, we will include the webapp
> related permissions as well in the EMM console.
>
+1. Please create a JIRA as improvement to track this.

>
> Thanks.
>
> Regards,
> Megala
>
> On Wed, Oct 12, 2016 at 6:42 AM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi Megala,
>>
>> Ideally there should be a permission called Mobile App/Subscribe, but
>> currently it has only Web App/Subscribe. This is something we should
>> improve later.
>>
>> Regards,
>> Dinusha.
>>
>> On Tue, Oct 11, 2016 at 9:23 PM, Megala Uthayakumar <meg...@wso2.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> I am working on a jira regarding adding app-store related permissions to
>>> EMM console [1]. In EMM we use app-store for installing and handling mobile
>>> apps. So I thought of adding the permissions that are only related with
>>> mobile-apps. But in carbon-appmgt, when the user logins, it checks for the
>>> subscriber role for the web-apps [2][3], even though it has a separate set
>>> of permissions for mobile-apps [4]. So in that case, even though the user
>>> is only concerned about mobile-apps, he/she should have subscriber role for
>>> web apps to login to app-store. Is this the correct behavior?
>>>
>>> [1] https://wso2.org/jira/browse/EMM-1333
>>> [2] https://github.com/wso2/carbon-appmgt/blob/master/featur
>>> es/org.wso2.carbon.appmgt.store.feature/src/main/resources/
>>> store/controllers/acs.jag#L116
>>> [3] https://github.com/wso2/carbon-appmgt/blob/master/compon
>>> ents/org.wso2.carbon.appmgt.hostobjects/src/main/java/org/ws
>>> o2/carbon/appmgt/hostobjects/APIStoreHostObject.java#L2682
>>> [4] https://github.com/wso2/carbon-appmgt/blob/master/compon
>>> ents/org.wso2.carbon.appmgt.impl/src/main/resources/META-INF
>>> /component.xml
>>>
>>> Thanks
>>>
>>> Regards,
>>> Megala
>>> --
>>> Megala Uthayakumar
>>>
>>> Software Engineer
>>> Mobile : 0779967122
>>>
>>
>>
>>
>> --
>> Dinusha Dilrukshi
>> Associate Technical Lead
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
> Megala Uthayakumar
>
> Software Engineer
> Mobile : 0779967122
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarification regarding carbon-appmgt permissions

[Dinusha Senanayaka]

Hi Megala,

Ideally there should be a permission called Mobile App/Subscribe, but
currently it has only Web App/Subscribe. This is something we should
improve later.

Regards,
Dinusha.

On Tue, Oct 11, 2016 at 9:23 PM, Megala Uthayakumar  wrote:

> Hi All,
>
> I am working on a jira regarding adding app-store related permissions to
> EMM console [1]. In EMM we use app-store for installing and handling mobile
> apps. So I thought of adding the permissions that are only related with
> mobile-apps. But in carbon-appmgt, when the user logins, it checks for the
> subscriber role for the web-apps [2][3], even though it has a separate set
> of permissions for mobile-apps [4]. So in that case, even though the user
> is only concerned about mobile-apps, he/she should have subscriber role for
> web apps to login to app-store. Is this the correct behavior?
>
> [1] https://wso2.org/jira/browse/EMM-1333
> [2] https://github.com/wso2/carbon-appmgt/blob/master/
> features/org.wso2.carbon.appmgt.store.feature/src/main/
> resources/store/controllers/acs.jag#L116
> [3] https://github.com/wso2/carbon-appmgt/blob/master/
> components/org.wso2.carbon.appmgt.hostobjects/src/main/
> java/org/wso2/carbon/appmgt/hostobjects/APIStoreHostObject.java#L2682
> [4] https://github.com/wso2/carbon-appmgt/blob/master/
> components/org.wso2.carbon.appmgt.impl/src/main/
> resources/META-INF/component.xml
>
> Thanks
>
> Regards,
> Megala
> --
> Megala Uthayakumar
>
> Software Engineer
> Mobile : 0779967122
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM] Registry Exception thrown at EMM publisher/store login

[Dinusha Senanayaka]

This happens because two different products trying to share the same config
registry and having conflicting resources.  If products are deployed
separately then we can mount config registry to different paths, but here
EMM needs both features to be install in same product.

One option would be to prefix the resource with product name, so that
resource path will be different. But this won't look nice from product
perspective. Also need migration client for existing users if we are doing
it now.
eg: /_system/config/repository/components/org.wso2.carbon.registry/queries/
*tag-summary-appmgt*

@Nuwan: Any ideas ?

Regards,
Dinusha.

On Thu, Oct 6, 2016 at 3:18 PM, Kamidu Punchihewa  wrote:

> Hi Sameera,
>
> This is a know issue with EMM 2.2.0-beta pack. You can track the progress
> of the issue by following the Jira ticket[1].
>
> [1] https://wso2.org/jira/browse/EMM-1669
>
> Thanks and Best Regards,
>
> Kamidu Sachith Punchihewa
> *Software Engineer*
> WSO2, Inc.
> lean . enterprise . middleware
> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>
>
> 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, retransmit, 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.
>
> On Thu, Oct 6, 2016 at 3:14 PM, Sameera Gunarathne 
> wrote:
>
>> Hi all,
>>
>> After login to the EMM app publisher/store we can see the following
>> error:
>>
>> [2016-10-03 13:51:00,155] ERROR 
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry}
>> -  Registry Exception occurred while executing the query
>> org.wso2.carbon.registry.core.exceptions.RegistryException: Invalid
>> value "8" for parameter "parameterIndex" [90008-175]
>> at org.wso2.carbon.registry.core.jdbc.dataaccess.SQLQueryProces
>> sor.executeQuery(SQLQueryProcessor.java:239)
>> at org.wso2.carbon.registry.core.jdbc.queries.QueryProcessorMan
>> ager.executeQuery(QueryProcessorManager.java:137)
>> at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.executeQ
>> uery(EmbeddedRegistry.java:2283)
>> at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.ex
>> ecuteQuery(CacheBackedRegistry.java:480)
>> at org.wso2.carbon.registry.core.session.UserRegistry.executeQu
>> eryInternal(UserRegistry.java:1757)
>> at org.wso2.carbon.registry.core.session.UserRegistry.access$35
>> 00(UserRegistry.java:61)
>> at org.wso2.carbon.registry.core.session.UserRegistry$36.run(Us
>> erRegistry.java:1705)
>> at org.wso2.carbon.registry.core.session.UserRegistry$36.run(Us
>> erRegistry.java:1702)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at org.wso2.carbon.registry.core.session.UserRegistry.executeQu
>> ery(UserRegistry.java:1702)
>> at org.wso2.carbon.appmgt.impl.APIConsumerImpl.getAllTags(APICo
>> nsumerImpl.java:843)
>> at 
>> org.wso2.carbon.appmgt.impl.UserAwareAPIConsumer.getAllTags(UserAwareAPIConsumer.java:39)
>> ..
>>
>> After some debugging it seems to be both APIM feature and APPM feature
>> trying to execute same query at the registry path /_system/config/repositor
>> y/components/org.wso2.carbon.registry/queries/tag-summary [1]. Since
>> they are different queries [2] & [3] when loading the APPM publisher/store
>> components it triggers this error. Then I built carbon-appmgt locally by
>> giving a different path to store query scripts. Then the issue is fixed.
>> Seems like if it can be done to either of the components this issue can be
>> fixed. Any help or suggestions highly appreciated.
>>
>> [1]
>>
>> [2] - https://github.com/wso2/carbon-apimgt/blob/d37855ec3551c97
>> c70166d990504801b2d72d18b/components/apimgt/org.wso2.
>> carbon.apimgt.impl/src/main/java/org/wso2/carbon/apimgt/
>> impl/AbstractAPIManager.java#L210
>>
>> [3] - https://github.com/wso2/carbon-appmgt/blob/master/componen
>> ts/org.wso2.carbon.appmgt.impl/src/main/java/org/wso2/
>> carbon/appmgt/impl/AbstractAPIManager.java#L152
>>
>> Thanks & Regards,
>> --
>> Sameera Gunarathne
>> Software Engineer, WSO2 Inc. http://wso2.com
>> 
>> Email: samee...@wso2.com
>> Mobile: +94714155561
>>
>> ___
>> 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
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: 

Re: [Dev] Dependency issue for carbon-appmgt master branch

[Dinusha Senanayaka]

+Jena

On Thu, Sep 8, 2016 at 10:27 AM, Dulitha Wijewantha 
wrote:

> Hi guys,
> Getting build issue on master for carbon-appmgt
>
> Cheers~
> [ERROR] Failed to execute goal on project org.wso2.carbon.appmgt.impl:
> Could not resolve dependencies for project org.wso2.carbon.appmgt:org.
> wso2.carbon.appmgt.impl:bundle:1.2.3-SNAPSHOT: The following artifacts
> could not be resolved: org.wso2.carbon.identity:org.
> wso2.carbon.identity.core:jar:5.2.1-SNAPSHOT,
> org.wso2.carbon.identity:org.wso2.carbon.identity.
> application.mgt:jar:5.2.1-SNAPSHOT, org.wso2.carbon.identity:org.
> wso2.carbon.user.mgt.stub:jar:5.2.1-SNAPSHOT,
> org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.stub:jar:5.2.1-SNAPSHOT,
> org.wso2.carbon.identity:org.wso2.carbon.identity.
> application.mgt.stub:jar:5.2.1-SNAPSHOT, org.wso2.carbon.identity:org.
> wso2.carbon.identity.entitlement.stub:jar:5.2.1-SNAPSHOT: Failure to find
> org.wso2.carbon.identity:org.wso2.carbon.identity.core:jar:5.2.1-SNAPSHOT
> in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in
> the local repository, resolution will not be reattempted until the update
> interval of wso2-nexus has elapsed or updates are forced -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project org.wso2.carbon.appmgt.impl: Could not resolve dependencies
> for project 
> org.wso2.carbon.appmgt:org.wso2.carbon.appmgt.impl:bundle:1.2.3-SNAPSHOT:
> The following artifacts could not be resolved: org.wso2.carbon.identity:org.
> wso2.carbon.identity.core:jar:5.2.1-SNAPSHOT,
> org.wso2.carbon.identity:org.wso2.carbon.identity.
> application.mgt:jar:5.2.1-SNAPSHOT, org.wso2.carbon.identity:org.
> wso2.carbon.user.mgt.stub:jar:5.2.1-SNAPSHOT,
> org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.stub:jar:5.2.1-SNAPSHOT,
> org.wso2.carbon.identity:org.wso2.carbon.identity.
> application.mgt.stub:jar:5.2.1-SNAPSHOT, org.wso2.carbon.identity:org.
> wso2.carbon.identity.entitlement.stub:jar:5.2.1-SNAPSHOT: Failure to find
> org.wso2.carbon.identity:org.wso2.carbon.identity.core:jar:5.2.1-SNAPSHOT
> in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in
> the local repository, resolution will not be reattempted until the update
> interval of wso2-nexus has elapsed or updates are forced
> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.
> getDependencies(LifecycleDependencyResolver.java:210)
> at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.
> resolveProjectDependencies(LifecycleDependencyResolver.java:117)
> at org.apache.maven.lifecycle.internal.MojoExecutor.
> ensureDependenciesAreResolved(MojoExecutor.java:258)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:201)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
> MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.
> buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.
> singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.
> execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.
> main(Launcher.java:352)
> Caused by: org.apache.maven.project.DependencyResolutionException: Could
> not resolve dependencies for project org.wso2.carbon.appmgt:org.
> wso2.carbon.appmgt.impl:bundle:1.2.3-SNAPSHOT: The following artifacts
> could not be resolved: org.wso2.carbon.identity:org.
> wso2.carbon.identity.core:jar:5.2.1-SNAPSHOT,
> org.wso2.carbon.identity:org.wso2.carbon.identity.
> application.mgt:jar:5.2.1-SNAPSHOT, org.wso2.carbon.identity:org.
> wso2.carbon.user.mgt.stub:jar:5.2.1-SNAPSHOT,
> org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.stub:jar:5.2.1-SNAPSHOT,
> org.wso2.carbon.identity:org.wso2.carbon.identity.
> 

Re: [Dev] [AS-6.0.0] [SAML-SSO] Sending authenticated user attributes to webapp

[Dinusha Senanayaka]

Also we have sample tomcat valve[1] and filter[2] written, that shows app
can be used JWT token to identify the user and add to session. You should
be able to use them as well in samples.

[1]
https://github.com/wso2/product-app-manager/tree/master/modules/samples/JWTSecurity/Valve/Tomcat_8
[2]
https://github.com/wso2/product-app-manager/tree/master/modules/samples/JWTSecurity/Filter


On Tue, Aug 30, 2016 at 11:51 AM, Dinusha Senanayaka <dinu...@wso2.com>
wrote:

>
>
> On Tue, Aug 30, 2016 at 11:37 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> AS 6.0.0 is not an OSGi runtime. It's pure tomcat plus WSO2 features
>> as tomcat extensions. We could reuse the code here from App Manager.
>>
>
> Ah Ok. You can get the AppM code from here [1].
> [1] https://github.com/wso2/carbon-appmgt/tree/master/
> components/org.wso2.carbon.appmgt.gateway/src/main/java/
> org/wso2/carbon/appmgt/gateway/token
>
> Regards,
> Dinusha.
>
>>
>> @Johann/Sagara, shall we send the user attributes as JWT token to backend
>> webapp?
>>
>> On Tue, Aug 30, 2016 at 11:27 AM, Dinusha Senanayaka <dinu...@wso2.com>
>> wrote:
>>
>>> In App Manager, we process the SAML response and add SAML response
>>> assertions as JWT token and send to backend as a header. Shouldn't we try
>>> to install AppM features and get the gateway features into AS without
>>> redoing the same ?
>>>
>>> Regards,
>>> Dinusha.
>>>
>>> On Mon, Aug 29, 2016 at 8:50 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
>>>> We need to send the user attributes that are returned from SAML
>>>> response with the successful authentication, to the webapp using some way.
>>>> We discussed whether we could send this as a session attribute or using a
>>>> request parameter.
>>>>
>>>> @Kalpa, let's create a jira for this and add this to change to upcoming
>>>> milestone release.
>>>>
>>>> Thanks,
>>>>
>>>> --
>>>> *Kishanthan Thangarajah*
>>>> Technical Lead,
>>>> Platform Technologies Team,
>>>> WSO2, Inc.
>>>> lean.enterprise.middleware
>>>>
>>>> Mobile - +94773426635
>>>> Blog - *http://kishanthan.wordpress.com
>>>> <http://kishanthan.wordpress.com>*
>>>> Twitter - *http://twitter.com/kishanthan
>>>> <http://twitter.com/kishanthan>*
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Dinusha Dilrukshi
>>> Associate Technical Lead
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94725255071
>>> Blog: http://dinushasblog.blogspot.com/
>>>
>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Technical Lead,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> <http://kishanthan.wordpress.com>*
>> Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
>>
>
>
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AS-6.0.0] [SAML-SSO] Sending authenticated user attributes to webapp

[Dinusha Senanayaka]

On Tue, Aug 30, 2016 at 11:37 AM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:

> AS 6.0.0 is not an OSGi runtime. It's pure tomcat plus WSO2 features
> as tomcat extensions. We could reuse the code here from App Manager.
>

Ah Ok. You can get the AppM code from here [1].
[1]
https://github.com/wso2/carbon-appmgt/tree/master/components/org.wso2.carbon.appmgt.gateway/src/main/java/org/wso2/carbon/appmgt/gateway/token

Regards,
Dinusha.

>
> @Johann/Sagara, shall we send the user attributes as JWT token to backend
> webapp?
>
> On Tue, Aug 30, 2016 at 11:27 AM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> In App Manager, we process the SAML response and add SAML response
>> assertions as JWT token and send to backend as a header. Shouldn't we try
>> to install AppM features and get the gateway features into AS without
>> redoing the same ?
>>
>> Regards,
>> Dinusha.
>>
>> On Mon, Aug 29, 2016 at 8:50 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> We need to send the user attributes that are returned from SAML response
>>> with the successful authentication, to the webapp using some way. We
>>> discussed whether we could send this as a session attribute or using a
>>> request parameter.
>>>
>>> @Kalpa, let's create a jira for this and add this to change to upcoming
>>> milestone release.
>>>
>>> Thanks,
>>>
>>> --
>>> *Kishanthan Thangarajah*
>>> Technical Lead,
>>> Platform Technologies Team,
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - +94773426635
>>> Blog - *http://kishanthan.wordpress.com
>>> <http://kishanthan.wordpress.com>*
>>> Twitter - *http://twitter.com/kishanthan
>>> <http://twitter.com/kishanthan>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Dinusha Dilrukshi
>> Associate Technical Lead
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>*
> Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AS-6.0.0] [SAML-SSO] Sending authenticated user attributes to webapp

[Dinusha Senanayaka]

In App Manager, we process the SAML response and add SAML response
assertions as JWT token and send to backend as a header. Shouldn't we try
to install AppM features and get the gateway features into AS without
redoing the same ?

Regards,
Dinusha.

On Mon, Aug 29, 2016 at 8:50 PM, Kishanthan Thangarajah  wrote:

> We need to send the user attributes that are returned from SAML response
> with the successful authentication, to the webapp using some way. We
> discussed whether we could send this as a session attribute or using a
> request parameter.
>
> @Kalpa, let's create a jira for this and add this to change to upcoming
> milestone release.
>
> Thanks,
>
> --
> *Kishanthan Thangarajah*
> Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppM] SAML response signature validation in tenants

[Dinusha Senanayaka]

IMO, there should be a common SSOUtil package with all common SSO functions
client needed, which can use in all products.
- Request/Response signing
- Signature validation
- All other SAML Response related validations (audience, validity period
etc)

This is something we noticed during the security war room we recently had
as well. Most of the products APIM, AppM, GReg, ES, DS etc (in jagery-apps)
have handled these validations using different methods. Some have write own
utils, some have called *org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil
*and so. Effort we had to put was huge and repetitive because of not having
a common code.

For this scenario, I think using all the methods from
*org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil
*is cleaner, rather using different dependencies, unless we introduce a
clear common new module.

Regards,
Dinusha.

On Fri, Aug 19, 2016 at 3:31 PM, Rushmin Fernando  wrote:

> In our case we can re-use *org.wso2.carbon.webapp.mgt  *for signature
> validation since it has implemented it with the use of the agent code.
>
> And we can use the agent utils (*org.wso2.carbon.identity.sso.agent) *for
> unmarshelling the response
>
> But didn't see a util to marshall the requests ? Is it missing here ?
>
>
> On Fri, Aug 19, 2016 at 3:24 PM, Johann Nallathamby 
> wrote:
>
>>
>>
>> On Fri, Aug 19, 2016 at 12:26 PM, Darshana Gunawardana > > wrote:
>>
>>>
>>>
>>> On Fri, Aug 19, 2016 at 10:25 AM, Johann Nallathamby 
>>> wrote:
>>>
 This is what we have the SSO agent for.

>>>
>>> SSO Agent is not carbon specific. Hence it does not have reading
>>> tenant's key and validating the signature.
>>>
>>> SSO Agent have an interface to plug carbon use cases. AS SSO valve
>>> reference shared above have that specific implementation. That
>>> implementation invoked via sso agent.
>>>
>>
>> +1. That should be the way to go here also.
>>
>>
>>>
>>> Thanks
>>>
>>>
 @Rushmin, did you check the SSOAgent code? This was improved recently
 also and is used in AS 6.0. The goal of the implementation was to make it a
 library to be used everywhere in the platform. Can you please check on
 that? If there are any limitations we need to fix that library and try to
 use it everywhere we need it.

 Please check with Kernel team where to get this and use this.

 On Fri, Aug 19, 2016 at 9:56 AM, Ishara Karunarathna 
 wrote:

> Hi,
>
> On Fri, Aug 19, 2016 at 9:47 AM, Darshana Gunawardana <
> darsh...@wso2.com> wrote:
>
>>
>>
>> On Thu, Aug 18, 2016 at 4:43 PM, Rushmin Fernando 
>> wrote:
>>
>>>
>>> In current App Manager the service providers of tenants are getting
>>> created in the super tenant space.
>>>
>>> We are in the process of creating the service providers in the
>>> relevant tenants.
>>>
>>> In the app manager gateway, we use SAML SSO to authenticate the
>>> users, and the aforementioned service providers are used.
>>>
>>> When it comes to validating the the SAML response signature, I can
>>> see that we can re-use
>>> *org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil::getX509CredentialImplForTenant()*
>>>
>>> As per the code, it uses the tenant key store to get the
>>> certificates. And we can get the certificate by using the tenant name as
>>> the alias
>>>
>>> @IS team, do you see any issues with re-using this code in our
>>> gateway ?
>>>
>>
>> Using this util makes gateway -which is a client side(sp) component-
>> depends on the SAML component -which is server side(idp) component-
>>
>> IMO, its not nice to have that dependency. Once example is, this
>> dependency will expose you a samlsso (idp) endpoint from the gateway. And
>> also gateway profile would need to have saml components and makes you to
>> have whole framework related dependencies as well.
>>
>> Thinking about client side (sp) components which already doing this
>> there are two components we have in wso2 platform.
>> 1. Carbon SAML authenticator : https://github.com/wso2-exte
>> nsions/identity-carbon-auth-saml2
>> 2. AS SSO valve : https://github.com/wso2/carb
>> on-deployment/blob/4.7.x/components/webapp-mgt/org.wso2.carb
>> on.webapp.mgt/src/main/java/org/wso2/carbon/webapp/mgt/sso/S
>> AMLSignatureValidatorImpl.java
>>
>> Better to use utls from those two components, if we have such
>> methods. Most suitable component for gateway is #2, since carbon
>> authenticator don't have usage in gateway.
>>
>> I guess it's even worthy initiate separate component to handle all
>> these saml utils, given that we have isolated components across the
>> platform and we have to fix huge number of components if we identified a
>> core issue.
>>
> 

Re: [Dev] [AppM] Creating XACML Policies and Service Providers in Tenants

[Dinusha Senanayaka]

On Mon, Aug 8, 2016 at 5:43 PM, Ishara Karunarathna 
wrote:

> Hi Rushmin,
>
> On Mon, Aug 8, 2016 at 5:26 PM, Rushmin Fernando  wrote:
>
>> Hi Ishara,
>>
>> We are currently using the following two admin services to create service
>> providers.
>>
>> IdentitySAMLSSOConfigService
>> IdentityApplicationManagementService
>>
> admin/manage
>
> permission should be there for both services
>
>  hmm .. admin/manage is admin rights ? This mean we need to assign admin
> rights to publisher. :( . Is there any possibility of adding fine grained
> permission for these two services as well, similar to XACML services ?
>

Regards,
Dinusha.

>
>> If we are to follow the above SAML authenticator method for this as well,
>> what are the permissions should a role have ?
>>
>> Regards
>> Rushmin
>>
>> On Mon, Aug 8, 2016 at 5:18 PM, Lahiru Cooray  wrote:
>>
>>> Hi Ishara,
>>> Thanks a lot for the info..
>>>
>>> On Mon, Aug 8, 2016 at 4:04 PM, Ishara Karunarathna 
>>> wrote:
>>>
 Hi Dinusha,

 In this case I think publisher user should be able to create those SP,
 XACML policies etc.
 Since publisher use is within the publisher role you can assign
 necessary permission to that role.
 Once user login (SSO) to publisher with his credential  he can get a
 cookie for that
 and he can use that  cookie to authenticate to the admin services.

 @Rushmin,
 We don't have a authenticator for OAuth token. Better to get a ID token
 using OIDC or after validating OAuth token
 and create a carbon authenticator like saml carbon authenticator.

 Thanks,
 Ishara




 On Mon, Aug 8, 2016 at 3:47 PM, Rushmin Fernando 
 wrote:

> In addition to creating these entries from the UI, we need to create
> the same using our ReST API as well. And the API is OAuth protected.
>
> Is there an authenticator which gives back a cookie for an OAuth token
> as well ?
>
> On Mon, Aug 8, 2016 at 3:29 PM, Ishara Karunarathna 
> wrote:
>
>> Hi Lahiru.
>>
>>
>> Its not the admin user.User trying to do this operation should have
>> enough permission to do this.
>>
>> Use
>>
>>
>>
>> *entitlement/policy/view*
>>
>> Add this permission to the user who is trying to view those policies.
>>
>>
>> BR,
>>
>> Ishara
>>
>>
>> On Mon, Aug 8, 2016 at 3:20 PM, Lahiru Cooray 
>> wrote:
>>
>>> + [DEV]
>>>
>>> On Mon, Aug 8, 2016 at 3:19 PM, Lahiru Cooray 
>>> wrote:
>>>
 Hi all,

 *Current behaviour:*
 Currently in AppM, when we are creating XACML policies/Service
 Providers via IS admin services, we are providing the super tenant 
 admin
 credentials (where the credentials are stored in a config) to get
 authenticated. Further, XACML policies/Service providers are only 
 created
 in super tenant and marked as a SAAS app to be used in tenants.

 *Problem:*
 As we are moving for AppM - Cloud integration, we are trying to
 deploy these in relevant tenant spaces. So as a solution we have tried 
 to
 use *SAML2SSOAuthenticator*[1]  (retrieving a cookie passing the
 SAML response and use the same in subsequent service calls) but figured
 that this is not applicable for non admin users.
 (*eg:* In AppM user story, non admin users should be allowed to
 create apps with XAML policies)

 Any suggestions for this would be highly appreciated!


 [1] https://github.com/wso2/carbon-identity/blob/8cd996c1dc6
 d9e7c0df491322af6e9ddf1cf3709/components/carbon-authenticato
 rs/saml2-sso-authenticator/org.wso2.carbon.identity.authenti
 cator.saml2.sso/src/main/java/org/wso2/carbon/identity/authe
 nticator/saml2/sso/SAML2SSOAuthenticator.java

 --
 *Lahiru Cooray*
 Software Engineer
 WSO2, Inc.;http://wso2.com/
 lean.enterprise.middleware

 Mobile: +94 715 654154

>>>
>>>
>>>
>>> --
>>> *Lahiru Cooray*
>>> Software Engineer
>>> WSO2, Inc.;http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 715 654154
>>>
>>
>>
>>
>> --
>> Ishara Karunarathna
>> Associate Technical Lead
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
>> +94717996791
>>
>>
>>
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile 

Re: [Dev] [AppM] Creating XACML Policies and Service Providers in Tenants

[Dinusha Senanayaka]

Hi Ishara,

On Mon, Aug 8, 2016 at 3:29 PM, Ishara Karunarathna 
wrote:

> Hi Lahiru.
>
>
> Its not the admin user.User trying to do this operation should have enough
> permission to do this.
>

This is something we need to  clarify. Not only XACML policy
create/update/view. Publisher user need to add/update/delete service
providers as well. This happens internally by calling to admin services
provided by IdP. Requirement is, we don't have admin credentials stored for
each tenant space. Is there a way we can create the SP and XACML policies
in each tenant space. We thought if we get a cookie using
*SAML2SSOAuthenticator
*we can pass that cookie to admin service and call relevant operations. But
seems that's not a solution for issue ?

Regards,
Dinusha.



>
> Use
>
>
>
> *entitlement/policy/view*
>
> Add this permission to the user who is trying to view those policies.
>
>
> BR,
>
> Ishara
>
>
> On Mon, Aug 8, 2016 at 3:20 PM, Lahiru Cooray  wrote:
>
>> + [DEV]
>>
>> On Mon, Aug 8, 2016 at 3:19 PM, Lahiru Cooray  wrote:
>>
>>> Hi all,
>>>
>>> *Current behaviour:*
>>> Currently in AppM, when we are creating XACML policies/Service Providers
>>> via IS admin services, we are providing the super tenant admin credentials
>>> (where the credentials are stored in a config) to get authenticated.
>>> Further, XACML policies/Service providers are only created in super tenant
>>> and marked as a SAAS app to be used in tenants.
>>>
>>> *Problem:*
>>> As we are moving for AppM - Cloud integration, we are trying to deploy
>>> these in relevant tenant spaces. So as a solution we have tried to use
>>> *SAML2SSOAuthenticator*[1]  (retrieving a cookie passing the SAML
>>> response and use the same in subsequent service calls) but figured that
>>> this is not applicable for non admin users.
>>> (*eg:* In AppM user story, non admin users should be allowed to create
>>> apps with XAML policies)
>>>
>>> Any suggestions for this would be highly appreciated!
>>>
>>>
>>> [1] https://github.com/wso2/carbon-identity/blob/8cd996c1dc6
>>> d9e7c0df491322af6e9ddf1cf3709/components/carbon-authenticato
>>> rs/saml2-sso-authenticator/org.wso2.carbon.identity.authenti
>>> cator.saml2.sso/src/main/java/org/wso2/carbon/identity/
>>> authenticator/saml2/sso/SAML2SSOAuthenticator.java
>>>
>>> --
>>> *Lahiru Cooray*
>>> Software Engineer
>>> WSO2, Inc.;http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 715 654154
>>>
>>
>>
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>
>
>
> --
> Ishara Karunarathna
> Associate Technical Lead
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile:
> +94717996791
>
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] App manager REST API issue with MySQL

[Dinusha Senanayaka]

Hi Chathura,

Is this happen in latest AppM (master or 1.2.0 release)? Also  could see
space in the path: /mobileapps/admin/android/*Anti Virus 3*/1.2.0
. Can you try without having spaces in the App name.

Regards,
Dinusha.

On Mon, Aug 1, 2016 at 4:31 PM, Chathura Dilan  wrote:

> Hi All,
>
> We are getting following error in EMM after configure it with MySQL 5.5
> when adding a mobile app with REST API.
>
>
>
> TID: [-1234] [] [2016-08-01 10:20:21,492] ERROR
> {org.wso2.carbon.appmgt.rest.api.publisher.AppsApiService} -  Error
> occurred while creating mobile application : Anti Virus 3
> org.wso2.carbon.appmgt.api.AppManagementException: Error occurred while
> creating the mobile application : Anti Virus 3
> at
> org.wso2.carbon.appmgt.impl.AbstractAPIManager.handleException(AbstractAPIManager.java:692)
> at
> org.wso2.carbon.appmgt.impl.APIProviderImpl.createMobileApp(APIProviderImpl.java:470)
> at
> org.wso2.carbon.appmgt.impl.UserAwareAPIProvider.createMobileApp(UserAwareAPIProvider.java:36)
> at
> org.wso2.carbon.appmgt.rest.api.publisher.impl.AppsApiServiceImpl.appsAppTypePost(AppsApiServiceImpl.java:217)
> at
> org.wso2.carbon.appmgt.rest.api.publisher.AppsApi.appsAppTypePost(AppsApi.java:118)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:200)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:251)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:293)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:212)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:268)
> 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.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
> at
> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
> at
> org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve.invoke(WebappAuthenticationValve.java:45)
> at
> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
> at
> 

Re: [Dev] [VOTE] WSO2 App Manager 1.2.0 RC3

[Dinusha Senanayaka]

Hi All,

We are closing this vote. Vote hasn't got any -1 votes. We will proceed
with publishing the maven artifacts to nexus and hosting the GA pack.

Regards,
Dinusha.

On Thu, Jul 21, 2016 at 3:53 AM, Dinusha Senanayaka <dinu...@wso2.com>
wrote:

> Tested with following scenarios and found no issue.
>
> - Throttling
> - JWT generation for different apps
> - Recent apps loading
> - Deleting apps in multiple states
>
> +1
> Stable - Go ahead and release.
>
> Regards,
> Dinusha.
>
> On Thu, Jul 21, 2016 at 1:01 AM, Lahiru Cooray <lahi...@wso2.com> wrote:
>
>> Tested following Scenarios:
>>
>>- SSO and SLO
>>- App visibility restrictions
>>- Resource level role based restriction
>>- Favourite apps/page functionality
>>- Sorting and searching
>>
>>
>> +1
>> Stable - Go ahead and release.
>>
>>
>> On Wed, Jul 20, 2016 at 11:09 PM, Lahiru Cooray <lahi...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 3rd Release Candidate of the WSO2 App Manager 1.2.0
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>> Refer to github readme for guides.
>>>
>>> The distribution is available to download at [1]
>>>
>>> [1] :
>>> https://github.com/wso2/product-app-manager/releases/download/v1.2.0-RC3/wso2appm-1.2.0.zip
>>>
>>> Fixed Issue in [2], known issues [3], tag to be vote upon [4]
>>>
>>> [2] : https://wso2.org/jira/issues/?filter=13104
>>> [3] : https://wso2.org/jira/issues/?filter=13148
>>> [4] :
>>> https://github.com/wso2/product-app-manager/releases/tag/v1.2.0-RC3
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>> Thanks,
>>> App Manager Team
>>>
>>> --
>>> *Lahiru Cooray*
>>> Software Engineer
>>> WSO2, Inc.;http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 715 654154
>>>
>>
>>
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] WSO2 App Manager 1.2.0 RC3

[Dinusha Senanayaka]

Tested with following scenarios and found no issue.

- Throttling
- JWT generation for different apps
- Recent apps loading
- Deleting apps in multiple states

+1
Stable - Go ahead and release.

Regards,
Dinusha.

On Thu, Jul 21, 2016 at 1:01 AM, Lahiru Cooray  wrote:

> Tested following Scenarios:
>
>- SSO and SLO
>- App visibility restrictions
>- Resource level role based restriction
>- Favourite apps/page functionality
>- Sorting and searching
>
>
> +1
> Stable - Go ahead and release.
>
>
> On Wed, Jul 20, 2016 at 11:09 PM, Lahiru Cooray  wrote:
>
>> Hi Devs,
>>
>> This is the 3rd Release Candidate of the WSO2 App Manager 1.2.0
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> The distribution is available to download at [1]
>>
>> [1] :
>> https://github.com/wso2/product-app-manager/releases/download/v1.2.0-RC3/wso2appm-1.2.0.zip
>>
>> Fixed Issue in [2], known issues [3], tag to be vote upon [4]
>>
>> [2] : https://wso2.org/jira/issues/?filter=13104
>> [3] : https://wso2.org/jira/issues/?filter=13148
>> [4] : https://github.com/wso2/product-app-manager/releases/tag/v1.2.0-RC3
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> Thanks,
>> App Manager Team
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>
>
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] WSO2 App Manager 1.2.0 RC2

[Dinusha Senanayaka]

Closing vote because of [1]. We will open RC3 vote.

[1] https://wso2.org/jira/browse/APPM-1573

Regards,
Dinusha.

On Wed, Jul 20, 2016 at 11:20 AM, Dinusha Senanayaka <dinu...@wso2.com>
wrote:

> Hi All,
>
> Tested following scenarios and found no issue.
>
> - SSO/SLO between store/publisher/GW apps
> - Visibility restriction for app
> - Resource level visibiblity restriction
> - Throttling
> - Relay state for GW URLs
> - Annonymous access
> - Tags
> - User comments/rating
> - Share apps between tenants/ Publish to external stores
>
> +1 for releasing.
>
> Regards,
> Dinusha.
>
> On Wed, Jul 20, 2016 at 10:18 AM, Thilini Shanika <thili...@wso2.com>
> wrote:
>
>> Tested following Scenarios
>>
>> - App create/update/lifecycle change, app invocation in super tenant and
>> tenant domains
>> - Anonymous apps, role restricted apps in super tenant and tenant domains
>> - Tenanted stores and tenanted user signup
>> - Rest API token generation and API invocation in super tenant and tenant
>> domains
>>
>> +1
>> Stable - Go ahead and release.
>>
>>
>> On Tue, Jul 19, 2016 at 1:01 AM, Lahiru Cooray <lahi...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 2nd Release Candidate of the WSO2 App Manager 1.2.0
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>> Refer to github readme for guides.
>>>
>>> The distribution is available to download at [1]
>>>
>>> [1] :
>>> https://github.com/wso2/product-app-manager/releases/download/v1.2.0-RC2/wso2appm-1.2.0.zip
>>>
>>> Fixed Issue in [2], known issues [3], tag to be vote upon [4]
>>>
>>> [2] : https://wso2.org/jira/issues/?filter=13104
>>> [3] : https://wso2.org/jira/issues/?filter=13148
>>> [4] : https://github.com/wso2/carbon-appmgt/tree/v1.2.1
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>> Thanks,
>>> App Manager Team
>>>
>>> --
>>> *Lahiru Cooray*
>>> Software Engineer
>>> WSO2, Inc.;http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 715 654154
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] WSO2 App Manager 1.2.0 RC2

[Dinusha Senanayaka]

Hi All,

Tested following scenarios and found no issue.

- SSO/SLO between store/publisher/GW apps
- Visibility restriction for app
- Resource level visibiblity restriction
- Throttling
- Relay state for GW URLs
- Annonymous access
- Tags
- User comments/rating
- Share apps between tenants/ Publish to external stores

+1 for releasing.

Regards,
Dinusha.

On Wed, Jul 20, 2016 at 10:18 AM, Thilini Shanika  wrote:

> Tested following Scenarios
>
> - App create/update/lifecycle change, app invocation in super tenant and
> tenant domains
> - Anonymous apps, role restricted apps in super tenant and tenant domains
> - Tenanted stores and tenanted user signup
> - Rest API token generation and API invocation in super tenant and tenant
> domains
>
> +1
> Stable - Go ahead and release.
>
>
> On Tue, Jul 19, 2016 at 1:01 AM, Lahiru Cooray  wrote:
>
>> Hi Devs,
>>
>> This is the 2nd Release Candidate of the WSO2 App Manager 1.2.0
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> The distribution is available to download at [1]
>>
>> [1] :
>> https://github.com/wso2/product-app-manager/releases/download/v1.2.0-RC2/wso2appm-1.2.0.zip
>>
>> Fixed Issue in [2], known issues [3], tag to be vote upon [4]
>>
>> [2] : https://wso2.org/jira/issues/?filter=13104
>> [3] : https://wso2.org/jira/issues/?filter=13148
>> [4] : https://github.com/wso2/carbon-appmgt/tree/v1.2.1
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> Thanks,
>> App Manager Team
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>> ___
>> 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
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] WSO2 App Manager 1.2.0 RC1

[Dinusha Senanayaka]

Found issue [1] which need to be fixed. Hence closing this vote and we will
be opening RC2 vote soon.

[1] https://wso2.org/jira/browse/APPM-1568

Regards,
Dinusha.

On Sun, Jul 17, 2016 at 10:05 PM, Lakshani Gamage  wrote:

> Hi all,
>
> I tested followings.
>
>- Business Owner functionalities.
>- App creation and life cycle changing flows.
>- App documentation. (Publisher and Store)
>- Sorting and Searching in Store.
>- Smoke tested with Oracle DB.
>
> Works fine. I didn't encounter any issues.
>
> [+] Stable - go ahead and release
> Thanks and Regards,
> Lakshani.
>
> On Sat, Jul 16, 2016 at 5:19 PM, Thilini Shanika 
> wrote:
>
>> Adding Architecture
>>
>> On Sat, Jul 16, 2016 at 6:36 AM, Thilini Shanika 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 1st Release Candidate of the WSO2 App Manager 1.2.0
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>> Refer to github readme for guides.
>>>
>>> The distribution is available to download at [1]
>>>
>>> [1] :
>>> https://github.com/wso2/product-app-manager/releases/download/v1.2.0-RC1/wso2appm-1.2.0.zip
>>>
>>> Fixed Issue in [2], known issues [3], tag to be vote upon [4]
>>>
>>> [2] : https://wso2.org/jira/issues/?filter=13104
>>> [3] : https://wso2.org/jira/browse/WSFRUBY-72?filter=13140
>>> [4] : https://github.com/wso2/carbon-appmgt/tree/v1.2.0-RC1
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>> Thanks,
>>> App Manager Team
>>>
>>> --
>>> Thilini Shanika
>>> Senior Software Engineer
>>> WSO2, Inc.; http://wso2.com
>>> 20, Palmgrove Avenue, Colombo 3
>>>
>>> E-mail: tgtshan...@gmail.com
>>>
>>>
>>
>>
>> --
>> Thilini Shanika
>> Senior Software Engineer
>> WSO2, Inc.; http://wso2.com
>> 20, Palmgrove Avenue, Colombo 3
>>
>> E-mail: tgtshan...@gmail.com
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Lakshani Gamage
>
> *Software Engineer, WSO2*
>
> *Mobile : +94 71 5478184 <%2B94%20%280%29%20773%20451194>*
> *Blog : http://lakshanigamage.blogspot.com/
> *
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Regarding APPM-1160

[Dinusha Senanayaka]

Agree with Ruwan's point that we should not keep credentials per tenant.
But, passing tenantId as a query parameter to API seems a security
concern.  This provides capability to access some other tenant's device
list to any of the tenant having valid access token. One way that I could
think of to avoid this is, keep only consumer/secret key in the
app-manager.xml and generate the access token when user login into the
store. In the API side, identify the user and tenant domain using access
token and filter only devices belong to that tenant space. Again, this
won't be a good solution, since we need to use password grant type which
requires to access the user password to get the access token at the time of
user login. So we back to keeping per tenant credential solution :).

Regards,
Dinusha.


On Fri, Jul 8, 2016 at 12:25 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:

> Hi All,
> I think REST connector should have single endpoint. The rest call can have
> tenant ID in a header or as a request parameter. Then the API gateway(
> API-Manager) should be able to distinguish the respective endpoint if
> necessary. This is a functionality of APIM.
>
> The reasons are,
> 1. REST connector request/response will not be change at all between
> tenants
> 2. It is not needed to maintain credentials per tenant in AppM side.
>
> -1 on having configuration per tenant wise even in registry.
> I do not agree with the JIRA.
>
> Cheers,
> Ruwan
>
> On Fri, Jul 8, 2016 at 11:38 AM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi Sajith,
>>
>> We could not keep each and every tenant authentication configuration in
>> app-manager.xml, due to dynamic nature of tenant creation and the growth.
>>
>> appmgt.mdm.rest.connector is the default connector that we provided to
>> connect with WSO2EMM. We could keep it's configurations in the registry.
>> Also I don't think at least 1% of the requirements will come to use
>> specific connector other than using default connectors provided by us (EMM).
>>
>> Regards,
>> Dinusha.
>>
>> On Fri, Jul 8, 2016 at 11:22 AM, Sajith Abeywardhana <saji...@wso2.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> EMM supports multi-tenancy it is designed to work with one instance of
>>>> App Manager via OSGI services. When they work together they function as one
>>>> product, hence EMM and App Manager share same tenants across the multi
>>>> tenanted environment.
>>>>
>>>
>>> This means we don't need to keep the tenant config when we are
>>> connecting using OSGi service.
>>>
>>>
>>>> This is a special scenario where AppM connects to EMM via  EMM REST
>>>> APIs. According to how we have developed the plugin tenant admin and
>>>> password needs to be stored in the plugin configuration. This is a
>>>> plugin specific configuration, therefore, the plugin developer has
>>>> flexibility to store those configurations in any way he prefers.
>>>>
>>>
>>> When we are connecting using REST connector we need to have a tenant
>>> config in AppM side. How about that we kept those tenant config in
>>> app-manager.xml as below.
>>>
>>> 
>>>
>>> >> bundle="org.wso2.carbon.appmgt.mdm.restconnector">
>>> >> name="ImageURL">/store/extensions/assets/mobileapp/resources/models/%s.png
>>> 
>>> https://localhost:9450/mdm-admin
>>> 
>>> https://localhost:9448/oauth2/token
>>> >> name="ClientKey">WjLm24IxBVLF0oz0VJfmtJbjJbka
>>> >> name="ClientSecret">v3KkIQXkJ1SDp_Bf8uUQxu5p7TQa
>>> hr.com <h...@wso2.com>,eng.com
>>> <e...@wso2.com>,mrk.com
>>> 
>>>
>>> >> bundle="org.wso2.carbon.appmgt.mdm.osgiconnector">
>>> >> name="ImageURL">/store/extensions/assets/mobileapp/resources/models/%s.png
>>> 
>>>
>>> 
>>> 
>>> hradmin
>>> hr.123
>>> 
>>> 
>>> engadmin
>>> eng.123
>>> 
>>> 
>>> mrkadmin
>>> eng.123
>>> 
>>> 
>>>
&

Re: [Dev] Regarding APPM-1160

[Dinusha Senanayaka]

Hi Sajith,

We could not keep each and every tenant authentication configuration in
app-manager.xml, due to dynamic nature of tenant creation and the growth.

appmgt.mdm.rest.connector is the default connector that we provided to
connect with WSO2EMM. We could keep it's configurations in the registry.
Also I don't think at least 1% of the requirements will come to use
specific connector other than using default connectors provided by us (EMM).

Regards,
Dinusha.

On Fri, Jul 8, 2016 at 11:22 AM, Sajith Abeywardhana <saji...@wso2.com>
wrote:

> Hi All,
>
> EMM supports multi-tenancy it is designed to work with one instance of
>> App Manager via OSGI services. When they work together they function as one
>> product, hence EMM and App Manager share same tenants across the multi
>> tenanted environment.
>>
>
> This means we don't need to keep the tenant config when we are connecting
> using OSGi service.
>
>
>> This is a special scenario where AppM connects to EMM via  EMM REST
>> APIs. According to how we have developed the plugin tenant admin and
>> password needs to be stored in the plugin configuration. This is a
>> plugin specific configuration, therefore, the plugin developer has
>> flexibility to store those configurations in any way he prefers.
>>
>
> When we are connecting using REST connector we need to have a tenant
> config in AppM side. How about that we kept those tenant config in
> app-manager.xml as below.
>
> 
>
>  bundle="org.wso2.carbon.appmgt.mdm.restconnector">
>  name="ImageURL">/store/extensions/assets/mobileapp/resources/models/%s.png
> 
> https://localhost:9450/mdm-admin
> 
> https://localhost:9448/oauth2/token
>  name="ClientKey">WjLm24IxBVLF0oz0VJfmtJbjJbka
>  name="ClientSecret">v3KkIQXkJ1SDp_Bf8uUQxu5p7TQa
> hr.com <h...@wso2.com>,eng.com
> <e...@wso2.com>,mrk.com
> 
>
>  bundle="org.wso2.carbon.appmgt.mdm.osgiconnector">
>  name="ImageURL">/store/extensions/assets/mobileapp/resources/models/%s.png
> 
>
> 
> 
> hradmin
> hr.123
> 
> 
> engadmin
> eng.123
> 
> 
> mrkadmin
> eng.123
> 
> 
>
> 
>
>
>
> --
> *Sajith Abeywardhana* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka.
> Mobile: +94772260485
> Email: saji...@wso2.com | Web: www.wso2.com
>
>
> On Tue, Jul 5, 2016 at 12:01 PM, Chathura Dilan <chathu...@wso2.com>
> wrote:
>
>> Hi Dinusha,
>>
>> EMM supports multi-tenancy it is designed to work with one instance of
>> App Manager via OSGI services. When they work together they function as one
>> product, hence EMM and App Manager share same tenants across the multi
>> tenanted environment.
>>
>
>> This is a special scenario where AppM connects to EMM via  EMM REST
>> APIs. According to how we have developed the plugin tenant admin and
>> password needs to be stored in the plugin configuration. This is a
>> plugin specific configuration, therefore, the plugin developer has
>> flexibility to store those configurations in any way he prefers.
>>
>> When it's comes to multi tenancy, +1 we have to store those
>> configurations in the registry for the rest connector plugin . But how we
>> store those values are plugin specific.
>>
>>
>> On Tue, Jul 5, 2016 at 10:51 AM, Dinusha Senanayaka <dinu...@wso2.com>
>> wrote:
>>
>>> Hi Chathura,
>>>
>>> Does multi-tenancy supports in EMM for device management ? If yes, we
>>> need to fix [1] as well, which means we cannot keep this configuration in
>>> the app-manager.xml. Need to take it to registry.
>>>
>>> [1] https://wso2.org/jira/browse/APPM-1160
>>>
>>> Regards,
>>> Dinsuha.
>>>
>>> --
>>> Dinusha Dilrukshi
>>> Associate Technical Lead
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94725255071
>>> Blog: http://dinushasblog.blogspot.com/
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Chatura Dilan Perera
>> *Associate Tech Lead** - WSO2 Inc.*
>> www.dilan.me
>>
>
>
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Regarding APPM-1160

[Dinusha Senanayaka]

Hi Chathura,

Does multi-tenancy supports in EMM for device management ? If yes, we need
to fix [1] as well, which means we cannot keep this configuration in the
app-manager.xml. Need to take it to registry.

[1] https://wso2.org/jira/browse/APPM-1160

Regards,
Dinsuha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Enterprise Subscription + Default JWT implementation

[Dinusha Senanayaka]

Hi Rushmin,

If I remember correctly, we have two options in JWT generation.
If  option is set to true then the claims are taken
from SAML Response and populate the JWT. If that property is set to false,
then we take the all claims from user store where it can cause the issue
that you have pointed.

+1 for checking user existence before retrieving claims from user store.

On a side note, applications that having multiple authenticators have to
provision the user if application is depend on some claims from our user
store.

Regards,
Dinusha.

On Thu, Jun 30, 2016 at 4:43 PM, Rushmin Fernando  wrote:

> [+ dev@]
>
> On Thu, Jun 30, 2016 at 4:41 PM, Rushmin Fernando 
> wrote:
>
>> One thing we can do is, check whether the user is available using
>> userStoreManager.isExistingUser() method call before the line [1]
>>
>>
>> [1]
>> https://github.com/wso2/carbon-appmgt/blob/master/components/org.wso2.carbon.appmgt.impl/src/main/java/org/wso2/carbon/appmgt/impl/token/DefaultClaimsRetriever.java#L91
>>
>> On Thu, Jun 30, 2016 at 4:31 PM, Rushmin Fernando 
>> wrote:
>>
>>>
>>> Sajith / Dinusha,
>>>
>>> In our default JWT implementation it tries to get the claims of the user
>>> from the  gateway node's user store.
>>>
>>> But when it comes to the enterprise subscription scenario, the
>>> authenticated user doesn't exist in the node's user store ( because the
>>> user is authenticated by a third party IDP like google )
>>>
>>> The impact is, we can't enable enterprise subscription since it gives an
>>> error while generating the JWT
>>>
>>> Is this something we have discussed before ?
>>>
>>>
>>

>
>>>
>>>
>>> --
>>> *Best Regards*
>>>
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>>
>>> mobile : +94772891266
>>>
>>>
>>>
>>
>>
>> --
>> *Best Regards*
>>
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>
>> mobile : +94772891266
>>
>>
>>
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94772891266
>
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

Verified in a clean repo and works fine. Thanks Kasun.

Regards,
Dinusha.

On Tue, Jun 28, 2016 at 2:20 PM, Kasun Bandara <kas...@wso2.com> wrote:

> Hi Dinusha,
>
> You should be using  identity framework 5.1.1-SNAPSHOT for the release.
>
> Thanks,
> Kasun.
>
> On Tue, Jun 28, 2016 at 1:56 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>>
>>
>> On Tue, Jun 28, 2016 at 1:33 PM, Kasun Bandara <kas...@wso2.com> wrote:
>>
>>> Hi Dinusha,
>>>
>>> Currently we have two branches in Identity framework. "r
>>> *elease-productis-5.2.0*" is for the IS 5.2.0 release which is based on
>>> "5.1.1-SNAPSHOT" & current "master" branch is for the IS 5.3.0 release
>>> which is based on "5.5.0-SNAPSHOT"
>>>
>> What is the version we should use to get this fix ?  5.1.1-SNAPSHOT or
>> 5.5.0-SNAPSHOT ? And we need to make sure that will get release with your
>> july 08th plan release.
>>
>> Regards,
>> Dinusha.
>>
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> On Tue, Jun 28, 2016 at 1:12 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>> wrote:
>>>
>>>> Thanks Kasun. We will update p2-repo and let you know. Anyway, the
>>>> xacml feature version is 5.5.0-SNAPSHOT ?
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>> On Tue, Jun 28, 2016 at 10:49 AM, Kasun Bandara <kas...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Dinusha,
>>>>>
>>>>> We have successfully upgraded our repositories to kernel 4.4.6. You
>>>>> can find the required feature update from [1] & [2].
>>>>>
>>>>> Thanks,
>>>>> Kasun.
>>>>>
>>>>> [1]
>>>>> https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml
>>>>>
>>>>> [2]
>>>>> https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml
>>>>>
>>>>> On Tue, Jun 28, 2016 at 9:50 AM, Dinusha Senanayaka <dinu...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Kasun,
>>>>>>
>>>>>> Any update on this ?
>>>>>>
>>>>>> Regards,
>>>>>> Dinusha.
>>>>>>
>>>>>> On Mon, Jun 27, 2016 at 10:05 AM, Kasun Bandara <kas...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Dinusha,
>>>>>>>
>>>>>>> We will be upgrading to kernel 4.4.6 with the required upgrade to
>>>>>>> opensaml & joda versions with in today. I will update the thread once 
>>>>>>> it's
>>>>>>> done.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Kasun.
>>>>>>>
>>>>>>> On Mon, Jun 27, 2016 at 9:58 AM, Dinusha Senanayaka <
>>>>>>> dinu...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi Kasun,
>>>>>>>>
>>>>>>>> Can you please review and merge PR [1] which fix the issue
>>>>>>>> mentioned in $subject. Please treat this as urgent since AppM product
>>>>>>>> release testing blocked without fixing this.
>>>>>>>>
>>>>>>>> [1] https://github.com/wso2/carbon-identity-framework/pull/346
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Dinusha.
>>>>>>>>
>>>>>>>> On Fri, Jun 24, 2016 at 4:16 PM, Kasun Bandara <kas...@wso2.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Dinuhsa,
>>>>>>>>>
>>>>>>>>> We will be releasing the required repositories on top of the
>>>>>>>>> kernel 4.4.6 release next week for the IS 5.3.0-M3. Along with that 
>>>>>>>>> we have
>>>>>>>>> decided to release a component release for release-productis-5.2.0 
>>>>>>>>> branch
>>>>>>>>> as well, which you can use on top of kernel 4.4.6. (5.1.1 SNAPSHOT)
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>

Re: [Dev] Renaming App Manager gateway cookie name to APPMSESSIONID from 'appmSamlSsoTokenId'

[Dinusha Senanayaka]

On Tue, Jun 28, 2016 at 2:23 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:

> +1 APPMSESSIONID, yes "appmSamlSsoTokenId" looks ugly.
>
> Do we plan to support multiple authentication mechanisms per single
> deployment? or is this going to be systemwide config?
>
I think having multiple authentication mechanisms that could choose based
on the app would give more flexibility. btw, we don't have planed any work
on that yet. May be after next immediate release.

Regards,
Dinusha.

>
> Cheers,
> Ruwan
>
> On Tue, Jun 28, 2016 at 2:12 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> +1 for having it as APPMSESSIONID. There are few places in the code we do
>> some functionalities by getting this cookie value. We have to change those
>> places and test properly.
>>
>> Regards,
>> Dinusha.
>>
>> On Tue, Jun 28, 2016 at 2:07 PM, Rushmin Fernando <rush...@wso2.com>
>> wrote:
>>
>>>
>>> I suggest that we should do the aforementioned change.
>>>
>>> *Reason*
>>>
>>> Even though we use SAML as the authentication mechanism in the gateway
>>> as of now, we might use different authentication mechanisms in near future.
>>> And session handling should be independent of authentication mechanism.
>>>
>>> So binding the name of the cookie to 'SAML' is ugly
>>>
>>> WDYT ?
>>>
>>>
>>>
>>> --
>>> *Best Regards*
>>>
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware
>>>
>>> mobile : +94772891266
>>>
>>>
>>>
>>
>>
>> --
>> Dinusha Dilrukshi
>> Associate Technical Lead
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
>
> *Ruwan Abeykoon*
> *Associate Director/Architect**,*
> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
> *lean.enterprise.middleware.*
>
> email: ruw...@wso2.com
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Renaming App Manager gateway cookie name to APPMSESSIONID from 'appmSamlSsoTokenId'

[Dinusha Senanayaka]

+1 for having it as APPMSESSIONID. There are few places in the code we do
some functionalities by getting this cookie value. We have to change those
places and test properly.

Regards,
Dinusha.

On Tue, Jun 28, 2016 at 2:07 PM, Rushmin Fernando  wrote:

>
> I suggest that we should do the aforementioned change.
>
> *Reason*
>
> Even though we use SAML as the authentication mechanism in the gateway as
> of now, we might use different authentication mechanisms in near future.
> And session handling should be independent of authentication mechanism.
>
> So binding the name of the cookie to 'SAML' is ugly
>
> WDYT ?
>
>
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> mobile : +94772891266
>
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

On Tue, Jun 28, 2016 at 1:33 PM, Kasun Bandara <kas...@wso2.com> wrote:

> Hi Dinusha,
>
> Currently we have two branches in Identity framework. "r
> *elease-productis-5.2.0*" is for the IS 5.2.0 release which is based on
> "5.1.1-SNAPSHOT" & current "master" branch is for the IS 5.3.0 release
> which is based on "5.5.0-SNAPSHOT"
>
What is the version we should use to get this fix ?  5.1.1-SNAPSHOT or
5.5.0-SNAPSHOT ? And we need to make sure that will get release with your
july 08th plan release.

Regards,
Dinusha.

>
> Thanks,
> Kasun.
>
> On Tue, Jun 28, 2016 at 1:12 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Thanks Kasun. We will update p2-repo and let you know. Anyway, the xacml
>> feature version is 5.5.0-SNAPSHOT ?
>>
>> Regards,
>> Dinusha.
>>
>> On Tue, Jun 28, 2016 at 10:49 AM, Kasun Bandara <kas...@wso2.com> wrote:
>>
>>> Hi Dinusha,
>>>
>>> We have successfully upgraded our repositories to kernel 4.4.6. You can
>>> find the required feature update from [1] & [2].
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> [1]
>>> https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml
>>>
>>> [2]
>>> https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml
>>>
>>> On Tue, Jun 28, 2016 at 9:50 AM, Dinusha Senanayaka <dinu...@wso2.com>
>>> wrote:
>>>
>>>> Hi Kasun,
>>>>
>>>> Any update on this ?
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>> On Mon, Jun 27, 2016 at 10:05 AM, Kasun Bandara <kas...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Dinusha,
>>>>>
>>>>> We will be upgrading to kernel 4.4.6 with the required upgrade to
>>>>> opensaml & joda versions with in today. I will update the thread once it's
>>>>> done.
>>>>>
>>>>> Thanks,
>>>>> Kasun.
>>>>>
>>>>> On Mon, Jun 27, 2016 at 9:58 AM, Dinusha Senanayaka <dinu...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Kasun,
>>>>>>
>>>>>> Can you please review and merge PR [1] which fix the issue mentioned
>>>>>> in $subject. Please treat this as urgent since AppM product release 
>>>>>> testing
>>>>>> blocked without fixing this.
>>>>>>
>>>>>> [1] https://github.com/wso2/carbon-identity-framework/pull/346
>>>>>>
>>>>>> Regards,
>>>>>> Dinusha.
>>>>>>
>>>>>> On Fri, Jun 24, 2016 at 4:16 PM, Kasun Bandara <kas...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Dinuhsa,
>>>>>>>
>>>>>>> We will be releasing the required repositories on top of the kernel
>>>>>>> 4.4.6 release next week for the IS 5.3.0-M3. Along with that we have
>>>>>>> decided to release a component release for release-productis-5.2.0 
>>>>>>> branch
>>>>>>> as well, which you can use on top of kernel 4.4.6. (5.1.1 SNAPSHOT)
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Kasun.
>>>>>>>
>>>>>>> On Fri, Jun 24, 2016 at 12:44 PM, Dinusha Senanayaka <
>>>>>>> dinu...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi Kasun,
>>>>>>>>
>>>>>>>> Please find the identity features used in AppM.
>>>>>>>>
>>>>>>>>
>>>>>>>> org.wso2.carbon.identity:org.wso2.carbon.security.mgt.feature:${carbon.identity.version}
>>>>>>>> 
>>>>>>>>
>>>>>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.mgt.feature:${carbon.identity.version}
>>>>>>>> 
>>>>>>>>
>>>>>>>> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.feature:${carbon.identity.version}
>>>>>>>> 
>>>>>>>>
>>>>>>>> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.ui.feature:${carbon.identity.version}
>>>>>>>> 
>>>>>>

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

Thanks Kasun. We will update p2-repo and let you know. Anyway, the xacml
feature version is 5.5.0-SNAPSHOT ?

Regards,
Dinusha.

On Tue, Jun 28, 2016 at 10:49 AM, Kasun Bandara <kas...@wso2.com> wrote:

> Hi Dinusha,
>
> We have successfully upgraded our repositories to kernel 4.4.6. You can
> find the required feature update from [1] & [2].
>
> Thanks,
> Kasun.
>
> [1]
> https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml
>
> [2] https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml
>
> On Tue, Jun 28, 2016 at 9:50 AM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi Kasun,
>>
>> Any update on this ?
>>
>> Regards,
>> Dinusha.
>>
>> On Mon, Jun 27, 2016 at 10:05 AM, Kasun Bandara <kas...@wso2.com> wrote:
>>
>>> Hi Dinusha,
>>>
>>> We will be upgrading to kernel 4.4.6 with the required upgrade to
>>> opensaml & joda versions with in today. I will update the thread once it's
>>> done.
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> On Mon, Jun 27, 2016 at 9:58 AM, Dinusha Senanayaka <dinu...@wso2.com>
>>> wrote:
>>>
>>>> Hi Kasun,
>>>>
>>>> Can you please review and merge PR [1] which fix the issue mentioned in
>>>> $subject. Please treat this as urgent since AppM product release testing
>>>> blocked without fixing this.
>>>>
>>>> [1] https://github.com/wso2/carbon-identity-framework/pull/346
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>> On Fri, Jun 24, 2016 at 4:16 PM, Kasun Bandara <kas...@wso2.com> wrote:
>>>>
>>>>> Hi Dinuhsa,
>>>>>
>>>>> We will be releasing the required repositories on top of the kernel
>>>>> 4.4.6 release next week for the IS 5.3.0-M3. Along with that we have
>>>>> decided to release a component release for release-productis-5.2.0 branch
>>>>> as well, which you can use on top of kernel 4.4.6. (5.1.1 SNAPSHOT)
>>>>>
>>>>> Thanks,
>>>>> Kasun.
>>>>>
>>>>> On Fri, Jun 24, 2016 at 12:44 PM, Dinusha Senanayaka <dinu...@wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Hi Kasun,
>>>>>>
>>>>>> Please find the identity features used in AppM.
>>>>>>
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.security.mgt.feature:${carbon.identity.version}
>>>>>> 
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.mgt.feature:${carbon.identity.version}
>>>>>> 
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.feature:${carbon.identity.version}
>>>>>> 
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.ui.feature:${carbon.identity.version}
>>>>>> 
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.core.feature:${carbon.identity.version}
>>>>>> 
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.provider.server.feature:${carbon.identity.version}
>>>>>> 
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.user.registration.server.feature:${carbon.identity.version}
>>>>>> 
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.oauth.feature:${carbon.identity.version}
>>>>>> 
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.feature:${carbon.identity.version}
>>>>>> 
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.user.profile.server.feature:${carbon.identity.version}
>>>>>> 
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.oauth.server.feature:${carbon.identity.oauth.version}
>>>>>>
>>>>>> org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.server.feature:${carbon.identity.oauth.version}
>>>>>>
>>>>>> org.wso2.carbon:org.wso2.carbon.identity.oauth.common.feature:${identity.oauth.common.version}
>>>>>> 
>>>>>>
>>>>>> org.

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

Hi Kasun,

Any update on this ?

Regards,
Dinusha.

On Mon, Jun 27, 2016 at 10:05 AM, Kasun Bandara <kas...@wso2.com> wrote:

> Hi Dinusha,
>
> We will be upgrading to kernel 4.4.6 with the required upgrade to opensaml
> & joda versions with in today. I will update the thread once it's done.
>
> Thanks,
> Kasun.
>
> On Mon, Jun 27, 2016 at 9:58 AM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi Kasun,
>>
>> Can you please review and merge PR [1] which fix the issue mentioned in
>> $subject. Please treat this as urgent since AppM product release testing
>> blocked without fixing this.
>>
>> [1] https://github.com/wso2/carbon-identity-framework/pull/346
>>
>> Regards,
>> Dinusha.
>>
>> On Fri, Jun 24, 2016 at 4:16 PM, Kasun Bandara <kas...@wso2.com> wrote:
>>
>>> Hi Dinuhsa,
>>>
>>> We will be releasing the required repositories on top of the kernel
>>> 4.4.6 release next week for the IS 5.3.0-M3. Along with that we have
>>> decided to release a component release for release-productis-5.2.0 branch
>>> as well, which you can use on top of kernel 4.4.6. (5.1.1 SNAPSHOT)
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> On Fri, Jun 24, 2016 at 12:44 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>> wrote:
>>>
>>>> Hi Kasun,
>>>>
>>>> Please find the identity features used in AppM.
>>>>
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.security.mgt.feature:${carbon.identity.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.mgt.feature:${carbon.identity.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.feature:${carbon.identity.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.ui.feature:${carbon.identity.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.core.feature:${carbon.identity.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.provider.server.feature:${carbon.identity.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.user.registration.server.feature:${carbon.identity.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.oauth.feature:${carbon.identity.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.feature:${carbon.identity.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.user.profile.server.feature:${carbon.identity.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.oauth.server.feature:${carbon.identity.oauth.version}
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.server.feature:${carbon.identity.oauth.version}
>>>>
>>>> org.wso2.carbon:org.wso2.carbon.identity.oauth.common.feature:${identity.oauth.common.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.basicauth.server.feature:${carbon.identity.version}
>>>> 
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.samlsso.server.feature:${carbon.identity.version}
>>>> 
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.claim.mgt.feature:${carbon.identity.version}
>>>> 
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.thrift.authentication.feature:${carbon.identity.version}
>>>> 
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.server.feature:${carbon.identity.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authentication.framework.server.feature:${carbon.identity.version}
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.sso.saml.feature:${carbon.identity.version}
>>>> 
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.authenticator.saml2.sso.feature:${carbon.identity-inbound-auth-saml2.version}
>>>> 
>>>>
>>>> org.wso2.carbon.identity:org.wso2.carbon.identity.user.profile.feature:${carbon.identity.version}
&g

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

Hi Kasun,

Can you please review and merge PR [1] which fix the issue mentioned in
$subject. Please treat this as urgent since AppM product release testing
blocked without fixing this.

[1] https://github.com/wso2/carbon-identity-framework/pull/346

Regards,
Dinusha.

On Fri, Jun 24, 2016 at 4:16 PM, Kasun Bandara <kas...@wso2.com> wrote:

> Hi Dinuhsa,
>
> We will be releasing the required repositories on top of the kernel 4.4.6
> release next week for the IS 5.3.0-M3. Along with that we have decided to
> release a component release for release-productis-5.2.0 branch as well,
> which you can use on top of kernel 4.4.6. (5.1.1 SNAPSHOT)
>
> Thanks,
> Kasun.
>
> On Fri, Jun 24, 2016 at 12:44 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi Kasun,
>>
>> Please find the identity features used in AppM.
>>
>>
>> org.wso2.carbon.identity:org.wso2.carbon.security.mgt.feature:${carbon.identity.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.mgt.feature:${carbon.identity.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.feature:${carbon.identity.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.ui.feature:${carbon.identity.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.core.feature:${carbon.identity.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.provider.server.feature:${carbon.identity.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.user.registration.server.feature:${carbon.identity.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.oauth.feature:${carbon.identity.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.feature:${carbon.identity.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.user.profile.server.feature:${carbon.identity.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.oauth.server.feature:${carbon.identity.oauth.version}
>>
>> org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.server.feature:${carbon.identity.oauth.version}
>>
>> org.wso2.carbon:org.wso2.carbon.identity.oauth.common.feature:${identity.oauth.common.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.basicauth.server.feature:${carbon.identity.version}
>> 
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.samlsso.server.feature:${carbon.identity.version}
>> 
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.claim.mgt.feature:${carbon.identity.version}
>> 
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.thrift.authentication.feature:${carbon.identity.version}
>> 
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.user.mgt.server.feature:${carbon.identity.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authentication.framework.server.feature:${carbon.identity.version}
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.sso.saml.feature:${carbon.identity.version}
>> 
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.authenticator.saml2.sso.feature:${carbon.identity-inbound-auth-saml2.version}
>> 
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.user.profile.feature:${carbon.identity.version}
>>
>> org.wso2.carbon.identity:org.wso2.carbon.um.ws.service.feature:${carbon.identity.version}
>>
>> org.wso2.carbon.identity:org.wso2.carbon.um.ws.service.server.feature:${carbon.identity.version}
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.mgt.feature:${carbon.identity.version}
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.xacml.feature:${carbon.identity.version}
>>
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.provisioning.server.feature:${carbon.identity.version}
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.openid.server.feature:${carbon.identity.version}
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.oidc.server.feature:${carbon.identity.version}
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.passive.sts.server.feature:${carbon.identity.version}
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.iwa.server.feature:${carbon.identity.version}
>>
>> org.wso2.carbon.identity:org.wso2.carbon.identity.application.authenticator.request

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

> repository release.
>
>
> [1]
> https://github.com/wso2-extensions/identity-agent-sso/blob/master/features/org.wso2.carbon.identity.sso.agent.server.feature/pom.xml
>
> Thanks,
> Kasun.
>
> On Fri, Jun 24, 2016 at 12:21 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>>
>> We are using several identity features. "
>> org.wso2.carbon.identity.xacml.feature"  is causing the issue it seems.
>>
>> On Fri, Jun 24, 2016 at 12:12 PM, Kasun Bandara <kas...@wso2.com> wrote:
>>
>>> Hi Dinusha,
>>>
>>> Can you please specify the relevant identity features you are using ?.
>>> IS-5.2.0 will be based on kernel 4.4.6. We are planning the component
>>> release along with the IS 5.2.0 GA release .
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> On Fri, Jun 24, 2016 at 11:44 AM, Dinusha Senanayaka <dinu...@wso2.com>
>>> wrote:
>>>
>>>> Kasun, this blocks the AppM kernel-4.4.6 upgrade. Is it possible to do
>>>> this today ? I thought IS-5.2.0 is already based on kernel 4.4.6.
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>> On Fri, Jun 24, 2016 at 11:38 AM, Kasun Bandara <kas...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Dinusha,
>>>>>
>>>>> Yes. we will be fixing this issue with once we upgrade the kernel
>>>>> version to 4.4.6. The opensaml version of the feature you have mentioned
>>>>> will be upgraded to opensaml-2.6.4.wso2v3. The corresponding repository
>>>>> release will be done along with the IS 5.2.0 GA release.
>>>>>
>>>>> Thanks,
>>>>> Kasun.
>>>>>
>>>>> On Fri, Jun 24, 2016 at 11:28 AM, Dinusha Senanayaka <dinu...@wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Hi Kasun,
>>>>>>
>>>>>> Non of the appmgt features are bundling opensaml. It's comes to AppM
>>>>>> product through identity features. Seems through the
>>>>>> org.wso2.carbon.identity.xacml.server.feature  [1] and it has still using
>>>>>> opensaml-2.6.4.wso2v2 [2]. Could you please fix that. That should resolve
>>>>>> this.
>>>>>>
>>>>>> [1]
>>>>>> https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml#L118
>>>>>> [2]
>>>>>> https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml#L1476
>>>>>>
>>>>>> Regards,
>>>>>> Dinusha.
>>>>>>
>>>>>> On Fri, Jun 24, 2016 at 10:55 AM, Kasun Bandara <kas...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Sajith,
>>>>>>>
>>>>>>> This issue was identified in [1] and we have fixed the issue with
>>>>>>> [2]. This issue can be resolve by using the new opensaml orbit. We are
>>>>>>> planning to release identity repositories (~50) on top of kernel 4.4.6,
>>>>>>> after fixing the security vulnerabilities as stated in [3]. You can 
>>>>>>> refer
>>>>>>> [4] to get the latest updates on IS 5.2.0 GA release.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Kasun.
>>>>>>>
>>>>>>>
>>>>>>> [1] https://wso2.org/jira/browse/IDENTITY-4680
>>>>>>>
>>>>>>> [2] [Engineering] Request to merge and release opensaml 2.6.4.wso2v3
>>>>>>> orbit
>>>>>>>
>>>>>>> [3] [Engineering] Security Hackathon to start from tomorrow
>>>>>>>
>>>>>>> [4] [Engineering] IS 5.2.0 GA Update
>>>>>>>
>>>>>>> On Fri, Jun 24, 2016 at 10:10 AM, Sajith Abeywardhana <
>>>>>>> saji...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi IS Team,
>>>>>>>>
>>>>>>>> AppM has been updated to the carbon kernel 4.4.6, and also I
>>>>>>>> updated the IS version to 5.1.1-SNAPSHOT. When I try to login to the
>>>>>>>> publisher jaggery app I got below exception[1].
>>>>>>>>
>>>>>>>> T

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

We are using several identity features. "
org.wso2.carbon.identity.xacml.feature"  is causing the issue it seems.

On Fri, Jun 24, 2016 at 12:12 PM, Kasun Bandara <kas...@wso2.com> wrote:

> Hi Dinusha,
>
> Can you please specify the relevant identity features you are using ?.
> IS-5.2.0 will be based on kernel 4.4.6. We are planning the component
> release along with the IS 5.2.0 GA release .
>
> Thanks,
> Kasun.
>
> On Fri, Jun 24, 2016 at 11:44 AM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Kasun, this blocks the AppM kernel-4.4.6 upgrade. Is it possible to do
>> this today ? I thought IS-5.2.0 is already based on kernel 4.4.6.
>>
>> Regards,
>> Dinusha.
>>
>> On Fri, Jun 24, 2016 at 11:38 AM, Kasun Bandara <kas...@wso2.com> wrote:
>>
>>> Hi Dinusha,
>>>
>>> Yes. we will be fixing this issue with once we upgrade the kernel
>>> version to 4.4.6. The opensaml version of the feature you have mentioned
>>> will be upgraded to opensaml-2.6.4.wso2v3. The corresponding repository
>>> release will be done along with the IS 5.2.0 GA release.
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> On Fri, Jun 24, 2016 at 11:28 AM, Dinusha Senanayaka <dinu...@wso2.com>
>>> wrote:
>>>
>>>> Hi Kasun,
>>>>
>>>> Non of the appmgt features are bundling opensaml. It's comes to AppM
>>>> product through identity features. Seems through the
>>>> org.wso2.carbon.identity.xacml.server.feature  [1] and it has still using
>>>> opensaml-2.6.4.wso2v2 [2]. Could you please fix that. That should resolve
>>>> this.
>>>>
>>>> [1]
>>>> https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml#L118
>>>> [2]
>>>> https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml#L1476
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>> On Fri, Jun 24, 2016 at 10:55 AM, Kasun Bandara <kas...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Sajith,
>>>>>
>>>>> This issue was identified in [1] and we have fixed the issue with [2].
>>>>> This issue can be resolve by using the new opensaml orbit. We are planning
>>>>> to release identity repositories (~50) on top of kernel 4.4.6, after 
>>>>> fixing
>>>>> the security vulnerabilities as stated in [3]. You can refer [4] to get 
>>>>> the
>>>>> latest updates on IS 5.2.0 GA release.
>>>>>
>>>>> Thanks,
>>>>> Kasun.
>>>>>
>>>>>
>>>>> [1] https://wso2.org/jira/browse/IDENTITY-4680
>>>>>
>>>>> [2] [Engineering] Request to merge and release opensaml 2.6.4.wso2v3
>>>>> orbit
>>>>>
>>>>> [3] [Engineering] Security Hackathon to start from tomorrow
>>>>>
>>>>> [4] [Engineering] IS 5.2.0 GA Update
>>>>>
>>>>> On Fri, Jun 24, 2016 at 10:10 AM, Sajith Abeywardhana <
>>>>> saji...@wso2.com> wrote:
>>>>>
>>>>>> Hi IS Team,
>>>>>>
>>>>>> AppM has been updated to the carbon kernel 4.4.6, and also I updated
>>>>>> the IS version to 5.1.1-SNAPSHOT. When I try to login to the publisher
>>>>>> jaggery app I got below exception[1].
>>>>>>
>>>>>> The root cause is for this is, opensaml_2.6.4.wso2v2 haven't
>>>>>> properly imported the required bouncy castle version which is version 
>>>>>> 1.52.0.wso2v1(packed
>>>>>> with kernel 4.4.6), and currently, it's [1.49.0,1.50.0)[2].
>>>>>>
>>>>>> Then I found that there is an opensaml_2.6.4.wso2v3 orbit bundle in
>>>>>> the git repo with the required bouncy castle version[3]. So when you
>>>>>> are planning to release the IS version, which bundles the opensaml_2.
>>>>>> 6.4.wso2v3 into a feature? Currently, we are blocking due to this
>>>>>> issue.
>>>>>>
>>>>>>
>>>>>> [1].  osgi> [2016-06-24 00:18:46,052] ERROR - StandardWrapperValve
>>>>>> Servlet.service() for servlet [bridgeservlet] in context with path [/]
>>>>>> threw exception [Servlet execution threw an exception] with root cause
>>>&g

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

Kasun, this blocks the AppM kernel-4.4.6 upgrade. Is it possible to do this
today ? I thought IS-5.2.0 is already based on kernel 4.4.6.

Regards,
Dinusha.

On Fri, Jun 24, 2016 at 11:38 AM, Kasun Bandara <kas...@wso2.com> wrote:

> Hi Dinusha,
>
> Yes. we will be fixing this issue with once we upgrade the kernel version
> to 4.4.6. The opensaml version of the feature you have mentioned will be
> upgraded to opensaml-2.6.4.wso2v3. The corresponding repository release
> will be done along with the IS 5.2.0 GA release.
>
> Thanks,
> Kasun.
>
> On Fri, Jun 24, 2016 at 11:28 AM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi Kasun,
>>
>> Non of the appmgt features are bundling opensaml. It's comes to AppM
>> product through identity features. Seems through the
>> org.wso2.carbon.identity.xacml.server.feature  [1] and it has still using
>> opensaml-2.6.4.wso2v2 [2]. Could you please fix that. That should resolve
>> this.
>>
>> [1]
>> https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml#L118
>> [2]
>> https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml#L1476
>>
>> Regards,
>> Dinusha.
>>
>> On Fri, Jun 24, 2016 at 10:55 AM, Kasun Bandara <kas...@wso2.com> wrote:
>>
>>> Hi Sajith,
>>>
>>> This issue was identified in [1] and we have fixed the issue with [2].
>>> This issue can be resolve by using the new opensaml orbit. We are planning
>>> to release identity repositories (~50) on top of kernel 4.4.6, after fixing
>>> the security vulnerabilities as stated in [3]. You can refer [4] to get the
>>> latest updates on IS 5.2.0 GA release.
>>>
>>> Thanks,
>>> Kasun.
>>>
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY-4680
>>>
>>> [2] [Engineering] Request to merge and release opensaml 2.6.4.wso2v3
>>> orbit
>>>
>>> [3] [Engineering] Security Hackathon to start from tomorrow
>>>
>>> [4] [Engineering] IS 5.2.0 GA Update
>>>
>>> On Fri, Jun 24, 2016 at 10:10 AM, Sajith Abeywardhana <saji...@wso2.com>
>>> wrote:
>>>
>>>> Hi IS Team,
>>>>
>>>> AppM has been updated to the carbon kernel 4.4.6, and also I updated
>>>> the IS version to 5.1.1-SNAPSHOT. When I try to login to the publisher
>>>> jaggery app I got below exception[1].
>>>>
>>>> The root cause is for this is, opensaml_2.6.4.wso2v2 haven't properly
>>>> imported the required bouncy castle version which is version 
>>>> 1.52.0.wso2v1(packed
>>>> with kernel 4.4.6), and currently, it's [1.49.0,1.50.0)[2].
>>>>
>>>> Then I found that there is an opensaml_2.6.4.wso2v3 orbit bundle in
>>>> the git repo with the required bouncy castle version[3]. So when you
>>>> are planning to release the IS version, which bundles the opensaml_2.
>>>> 6.4.wso2v3 into a feature? Currently, we are blocking due to this
>>>> issue.
>>>>
>>>>
>>>> [1].  osgi> [2016-06-24 00:18:46,052] ERROR - StandardWrapperValve
>>>> Servlet.service() for servlet [bridgeservlet] in context with path [/]
>>>> threw exception [Servlet execution threw an exception] with root cause
>>>> java.lang.ClassNotFoundException: org.bouncycastle.util.encoders.Hex
>>>> cannot be found by opensaml_2.6.4.wso2v2
>>>> at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>>>> at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>>>> at
>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>>>> at
>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>>>> at
>>>> org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:63)
>>>> at
>>>> org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:56)
>>>> at
>>>> org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil.createID(SAMLSSOUtil.java:726)
>>>> at
>>>> org.wso2.carbon.identity.sso.saml.builders.DefaultResponseBuilder.buildResponse(DefaultResponseBuilder.java:57)
>>>

Re: [Dev] [Carbon][IS][AppM] Kernel update to 4.4.6 in AppM gives ClassNotFoundException by opensaml_2.6.4.wso2v2

[Dinusha Senanayaka]

Hi Kasun,

Non of the appmgt features are bundling opensaml. It's comes to AppM
product through identity features. Seems through the
org.wso2.carbon.identity.xacml.server.feature  [1] and it has still using
opensaml-2.6.4.wso2v2 [2]. Could you please fix that. That should resolve
this.

[1]
https://github.com/wso2/carbon-identity-framework/blob/master/features/xacml/org.wso2.carbon.identity.xacml.server.feature/pom.xml#L118
[2]
https://github.com/wso2/carbon-identity-framework/blob/master/pom.xml#L1476

Regards,
Dinusha.

On Fri, Jun 24, 2016 at 10:55 AM, Kasun Bandara  wrote:

> Hi Sajith,
>
> This issue was identified in [1] and we have fixed the issue with [2].
> This issue can be resolve by using the new opensaml orbit. We are planning
> to release identity repositories (~50) on top of kernel 4.4.6, after fixing
> the security vulnerabilities as stated in [3]. You can refer [4] to get the
> latest updates on IS 5.2.0 GA release.
>
> Thanks,
> Kasun.
>
>
> [1] https://wso2.org/jira/browse/IDENTITY-4680
>
> [2] [Engineering] Request to merge and release opensaml 2.6.4.wso2v3 orbit
>
> [3] [Engineering] Security Hackathon to start from tomorrow
>
> [4] [Engineering] IS 5.2.0 GA Update
>
> On Fri, Jun 24, 2016 at 10:10 AM, Sajith Abeywardhana 
> wrote:
>
>> Hi IS Team,
>>
>> AppM has been updated to the carbon kernel 4.4.6, and also I updated the
>> IS version to 5.1.1-SNAPSHOT. When I try to login to the publisher jaggery
>> app I got below exception[1].
>>
>> The root cause is for this is, opensaml_2.6.4.wso2v2 haven't properly
>> imported the required bouncy castle version which is version 
>> 1.52.0.wso2v1(packed
>> with kernel 4.4.6), and currently, it's [1.49.0,1.50.0)[2].
>>
>> Then I found that there is an opensaml_2.6.4.wso2v3 orbit bundle in the
>> git repo with the required bouncy castle version[3]. So when you are
>> planning to release the IS version, which bundles the opensaml_2.6.4.wso2v3
>> into a feature? Currently, we are blocking due to this issue.
>>
>>
>> [1].  osgi> [2016-06-24 00:18:46,052] ERROR - StandardWrapperValve
>> Servlet.service() for servlet [bridgeservlet] in context with path [/]
>> threw exception [Servlet execution threw an exception] with root cause
>> java.lang.ClassNotFoundException: org.bouncycastle.util.encoders.Hex
>> cannot be found by opensaml_2.6.4.wso2v2
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>> at
>> org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:63)
>> at
>> org.opensaml.common.impl.SecureRandomIdentifierGenerator.generateIdentifier(SecureRandomIdentifierGenerator.java:56)
>> at
>> org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil.createID(SAMLSSOUtil.java:726)
>> at
>> org.wso2.carbon.identity.sso.saml.builders.DefaultResponseBuilder.buildResponse(DefaultResponseBuilder.java:57)
>> at
>> org.wso2.carbon.identity.sso.saml.processors.SPInitSSOAuthnRequestProcessor.process(SPInitSSOAuthnRequestProcessor.java:160)
>> at
>> org.wso2.carbon.identity.sso.saml.SAMLSSOService.authenticate(SAMLSSOService.java:164)
>> at
>> org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.handleAuthenticationReponseFromFramework(SAMLSSOProviderServlet.java:702)
>> at
>> org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.handleRequest(SAMLSSOProviderServlet.java:178)
>> at
>> org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.doGet(SAMLSSOProviderServlet.java:95)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at
>> org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
>> at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>> 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
>> 

Re: [Dev] [AppM] [GW] Message body of the response getting dropped in tenant mode

[Dinusha Senanayaka]

Thanks Nuwan/Buddhima. We ll continue with synapse-2.1.7.wso2v3-ALPHA until
the release happens.

Regards,
Dinusha.

On Sun, Jun 19, 2016 at 12:11 PM, Buddhima Wijeweera <buddh...@wso2.com>
wrote:

> Hi Nuwan,
> We expect to release at the end of this month.
> Thanks
>
> - sent via my phone
> On Jun 19, 2016 12:09 PM, "Nuwan Wimalasekara" <nuw...@wso2.com> wrote:
>
>> Hi Dinusha,
>>
>> Yes. This issue[1] has been reported earlier and It is fixed
>> in  synapse-2.1.7.wso2v3-ALPHA.
>>
>> @Buddhima,
>> Have we confirmed the release date of synapse-2.1.7.wso2v3
>>
>> [1] https://wso2.org/jira/browse/ESBJAVA-4512
>>
>> Thanks
>> Nuwanw
>>
>> On Sun, Jun 19, 2016 at 11:02 AM, Dinusha Senanayaka <dinu...@wso2.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> Issue seems to be with synapse-2.1.7.wso2v2. Updating
>>> to synapse-2.1.7.wso2v3-ALPHA dependencies solves the issue.
>>>
>>> @ESB team: can you confirm when is the 2.1.7.wso2v3 getting released ?
>>> Could see only BETA in the public repo.
>>>
>>> Regards,
>>> Dinusha.
>>>
>>> On Sun, Jun 19, 2016 at 9:11 AM, Rushmin Fernando <rush...@wso2.com>
>>> wrote:
>>>
>>>> And even in the tenant mode, everything works fine for POST.
>>>>
>>>> On Sat, Jun 18, 2016 at 3:58 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi ESB team,
>>>>>
>>>>> We are using synapse-2.1.7.wso2v2 dependencies and noticed that
>>>>> message body of the response getting dropped in tenant mode. We deployed
>>>>> two APIs in super-tenant mode and tenant mode without any of our handlers
>>>>> and observed the same behaviour. Refer following wire logs.
>>>>>
>>>>> Appreciate any clue on this to get it resolved.
>>>>>
>>>>>
>>>>> Tenant (Incorrect behaviour)
>>>>> --
>>>>> [2016-06-18 15:37:04,129] DEBUG - wire >> "GET /t/you.com/app2/1.0.0/
>>>>> HTTP/1.1[\r][\n]"
>>>>> [2016-06-18 15:37:04,130] DEBUG - wire >> "Host: 10.216.86.47:8280
>>>>> [\r][\n]"
>>>>> [2016-06-18 15:37:04,130] DEBUG - wire >> "User-Agent:
>>>>> curl/7.43.0[\r][\n]"
>>>>> [2016-06-18 15:37:04,130] DEBUG - wire >> "Accept: */*[\r][\n]"
>>>>> [2016-06-18 15:37:04,131] DEBUG - wire >> "[\r][\n]"
>>>>> [2016-06-18 15:37:04,342] DEBUG - wire << "GET /file/ HTTP/1.1[\r][\n]"
>>>>> [2016-06-18 15:37:04,343] DEBUG - wire << "Accept: */*[\r][\n]"
>>>>> [2016-06-18 15:37:04,343] DEBUG - wire << "Host:
>>>>> localhost:9763[\r][\n]"
>>>>> [2016-06-18 15:37:04,344] DEBUG - wire << "Connection:
>>>>> Keep-Alive[\r][\n]"
>>>>> [2016-06-18 15:37:04,344] DEBUG - wire << "User-Agent:
>>>>> Synapse-PT-HttpComponents-NIO[\r][\n]"
>>>>> [2016-06-18 15:37:04,344] DEBUG - wire << "[\r][\n]"
>>>>> [2016-06-18 15:37:04,345] DEBUG - wire >> "HTTP/1.1 200 OK[\r][\n]"
>>>>> [2016-06-18 15:37:04,345] DEBUG - wire >> "Content-Type:
>>>>> text/html[\r][\n]"
>>>>> [2016-06-18 15:37:04,346] DEBUG - wire >> "Content-Length: 193[\r][\n]"
>>>>> [2016-06-18 15:37:04,346] DEBUG - wire >> "Date: Sat, 18 Jun 2016
>>>>> 10:07:04 GMT[\r][\n]"
>>>>> [2016-06-18 15:37:04,347] DEBUG - wire >> "Server: WSO2 Carbon
>>>>> Server[\r][\n]"
>>>>> [2016-06-18 15:37:04,347] DEBUG - wire >> "[\r][\n]"
>>>>> [2016-06-18 15:37:04,348] DEBUG - wire >> ">>>> action="upload.jag" name="submit" enctype="multipart/form-data">[\n]"
>>>>> [2016-06-18 15:37:04,348] DEBUG - wire >> "  >>>> name="myfile">[\n]"
>>>>> [2016-06-18 15:37:04,348] DEBUG - wire >> "  >>>> name="submit" value="Submit">[\n]"
>>>>> [2016-06-18 15:37:04,349] DEBUG - wire >> ""
>>>>> [2016-06-18 15:37:04,360] DEBUG - wire << "HTTP/1.1 200 OK[\r][\n]"

Re: [Dev] [AppM] [GW] Message body of the response getting dropped in tenant mode

[Dinusha Senanayaka]

Hi All,

Issue seems to be with synapse-2.1.7.wso2v2. Updating
to synapse-2.1.7.wso2v3-ALPHA dependencies solves the issue.

@ESB team: can you confirm when is the 2.1.7.wso2v3 getting released ?
Could see only BETA in the public repo.

Regards,
Dinusha.

On Sun, Jun 19, 2016 at 9:11 AM, Rushmin Fernando <rush...@wso2.com> wrote:

> And even in the tenant mode, everything works fine for POST.
>
> On Sat, Jun 18, 2016 at 3:58 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi ESB team,
>>
>> We are using synapse-2.1.7.wso2v2 dependencies and noticed that message
>> body of the response getting dropped in tenant mode. We deployed two APIs
>> in super-tenant mode and tenant mode without any of our handlers and
>> observed the same behaviour. Refer following wire logs.
>>
>> Appreciate any clue on this to get it resolved.
>>
>>
>> Tenant (Incorrect behaviour)
>> --
>> [2016-06-18 15:37:04,129] DEBUG - wire >> "GET /t/you.com/app2/1.0.0/
>> HTTP/1.1[\r][\n]"
>> [2016-06-18 15:37:04,130] DEBUG - wire >> "Host: 10.216.86.47:8280
>> [\r][\n]"
>> [2016-06-18 15:37:04,130] DEBUG - wire >> "User-Agent:
>> curl/7.43.0[\r][\n]"
>> [2016-06-18 15:37:04,130] DEBUG - wire >> "Accept: */*[\r][\n]"
>> [2016-06-18 15:37:04,131] DEBUG - wire >> "[\r][\n]"
>> [2016-06-18 15:37:04,342] DEBUG - wire << "GET /file/ HTTP/1.1[\r][\n]"
>> [2016-06-18 15:37:04,343] DEBUG - wire << "Accept: */*[\r][\n]"
>> [2016-06-18 15:37:04,343] DEBUG - wire << "Host: localhost:9763[\r][\n]"
>> [2016-06-18 15:37:04,344] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
>> [2016-06-18 15:37:04,344] DEBUG - wire << "User-Agent:
>> Synapse-PT-HttpComponents-NIO[\r][\n]"
>> [2016-06-18 15:37:04,344] DEBUG - wire << "[\r][\n]"
>> [2016-06-18 15:37:04,345] DEBUG - wire >> "HTTP/1.1 200 OK[\r][\n]"
>> [2016-06-18 15:37:04,345] DEBUG - wire >> "Content-Type:
>> text/html[\r][\n]"
>> [2016-06-18 15:37:04,346] DEBUG - wire >> "Content-Length: 193[\r][\n]"
>> [2016-06-18 15:37:04,346] DEBUG - wire >> "Date: Sat, 18 Jun 2016
>> 10:07:04 GMT[\r][\n]"
>> [2016-06-18 15:37:04,347] DEBUG - wire >> "Server: WSO2 Carbon
>> Server[\r][\n]"
>> [2016-06-18 15:37:04,347] DEBUG - wire >> "[\r][\n]"
>> [2016-06-18 15:37:04,348] DEBUG - wire >> "> action="upload.jag" name="submit" enctype="multipart/form-data">[\n]"
>> [2016-06-18 15:37:04,348] DEBUG - wire >> "  > name="myfile">[\n]"
>> [2016-06-18 15:37:04,348] DEBUG - wire >> "  > name="submit" value="Submit">[\n]"
>> [2016-06-18 15:37:04,349] DEBUG - wire >> ""
>> [2016-06-18 15:37:04,360] DEBUG - wire << "HTTP/1.1 200 OK[\r][\n]"
>> [2016-06-18 15:37:04,361] DEBUG - wire << "Content-Type:
>> text/html[\r][\n]"
>> [2016-06-18 15:37:04,362] DEBUG - wire << "Date: Sat, 18 Jun 2016
>> 10:07:04 GMT[\r][\n]"
>> [2016-06-18 15:37:04,362] DEBUG - wire << "Transfer-Encoding:
>> chunked[\r][\n]"
>> [2016-06-18 15:37:04,363] DEBUG - wire << "[\r][\n]"
>> [2016-06-18 15:37:04,363] DEBUG - wire << "0[\r][\n]"
>> [2016-06-18 15:37:04,363] DEBUG - wire << "[\r][\n]"
>>
>>
>>
>> Super-Tenant (Correct behaviour)
>> -
>> [2016-06-18 15:46:33,073] DEBUG - wire >> "GET /App10/1.0.0/
>> HTTP/1.1[\r][\n]"
>> [2016-06-18 15:46:33,074] DEBUG - wire >> "Host: 10.216.86.47:8280
>> [\r][\n]"
>> [2016-06-18 15:46:33,074] DEBUG - wire >> "User-Agent:
>> curl/7.43.0[\r][\n]"
>> [2016-06-18 15:46:33,075] DEBUG - wire >> "Accept: */*[\r][\n]"
>> [2016-06-18 15:46:33,075] DEBUG - wire >> "[\r][\n]"
>> [2016-06-18 15:46:33,303] DEBUG - wire << "GET /file/ HTTP/1.1[\r][\n]"
>> [2016-06-18 15:46:33,304] DEBUG - wire << "Accept: */*[\r][\n]"
>> [2016-06-18 15:46:33,304] DEBUG - wire << "Host: localhost:9763[\r][\n]"
>> [2016-06-18 15:46:33,305] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
>> [2016-06-18 15:46:33,305] DEBUG - wire << "User-Agent:
>> Synapse-PT-Http

[Dev] [AppM] [GW] Message body of the response getting dropped in tenant mode

[Dinusha Senanayaka]

Hi ESB team,

We are using synapse-2.1.7.wso2v2 dependencies and noticed that message
body of the response getting dropped in tenant mode. We deployed two APIs
in super-tenant mode and tenant mode without any of our handlers and
observed the same behaviour. Refer following wire logs.

Appreciate any clue on this to get it resolved.


Tenant (Incorrect behaviour)
--
[2016-06-18 15:37:04,129] DEBUG - wire >> "GET /t/you.com/app2/1.0.0/
HTTP/1.1[\r][\n]"
[2016-06-18 15:37:04,130] DEBUG - wire >> "Host: 10.216.86.47:8280[\r][\n]"
[2016-06-18 15:37:04,130] DEBUG - wire >> "User-Agent: curl/7.43.0[\r][\n]"
[2016-06-18 15:37:04,130] DEBUG - wire >> "Accept: */*[\r][\n]"
[2016-06-18 15:37:04,131] DEBUG - wire >> "[\r][\n]"
[2016-06-18 15:37:04,342] DEBUG - wire << "GET /file/ HTTP/1.1[\r][\n]"
[2016-06-18 15:37:04,343] DEBUG - wire << "Accept: */*[\r][\n]"
[2016-06-18 15:37:04,343] DEBUG - wire << "Host: localhost:9763[\r][\n]"
[2016-06-18 15:37:04,344] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2016-06-18 15:37:04,344] DEBUG - wire << "User-Agent:
Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-06-18 15:37:04,344] DEBUG - wire << "[\r][\n]"
[2016-06-18 15:37:04,345] DEBUG - wire >> "HTTP/1.1 200 OK[\r][\n]"
[2016-06-18 15:37:04,345] DEBUG - wire >> "Content-Type: text/html[\r][\n]"
[2016-06-18 15:37:04,346] DEBUG - wire >> "Content-Length: 193[\r][\n]"
[2016-06-18 15:37:04,346] DEBUG - wire >> "Date: Sat, 18 Jun 2016 10:07:04
GMT[\r][\n]"
[2016-06-18 15:37:04,347] DEBUG - wire >> "Server: WSO2 Carbon
Server[\r][\n]"
[2016-06-18 15:37:04,347] DEBUG - wire >> "[\r][\n]"
[2016-06-18 15:37:04,348] DEBUG - wire >> "[\n]"
[2016-06-18 15:37:04,348] DEBUG - wire >> "  [\n]"
[2016-06-18 15:37:04,348] DEBUG - wire >> "  [\n]"
[2016-06-18 15:37:04,349] DEBUG - wire >> ""
[2016-06-18 15:37:04,360] DEBUG - wire << "HTTP/1.1 200 OK[\r][\n]"
[2016-06-18 15:37:04,361] DEBUG - wire << "Content-Type: text/html[\r][\n]"
[2016-06-18 15:37:04,362] DEBUG - wire << "Date: Sat, 18 Jun 2016 10:07:04
GMT[\r][\n]"
[2016-06-18 15:37:04,362] DEBUG - wire << "Transfer-Encoding:
chunked[\r][\n]"
[2016-06-18 15:37:04,363] DEBUG - wire << "[\r][\n]"
[2016-06-18 15:37:04,363] DEBUG - wire << "0[\r][\n]"
[2016-06-18 15:37:04,363] DEBUG - wire << "[\r][\n]"



Super-Tenant (Correct behaviour)
-
[2016-06-18 15:46:33,073] DEBUG - wire >> "GET /App10/1.0.0/
HTTP/1.1[\r][\n]"
[2016-06-18 15:46:33,074] DEBUG - wire >> "Host: 10.216.86.47:8280[\r][\n]"
[2016-06-18 15:46:33,074] DEBUG - wire >> "User-Agent: curl/7.43.0[\r][\n]"
[2016-06-18 15:46:33,075] DEBUG - wire >> "Accept: */*[\r][\n]"
[2016-06-18 15:46:33,075] DEBUG - wire >> "[\r][\n]"
[2016-06-18 15:46:33,303] DEBUG - wire << "GET /file/ HTTP/1.1[\r][\n]"
[2016-06-18 15:46:33,304] DEBUG - wire << "Accept: */*[\r][\n]"
[2016-06-18 15:46:33,304] DEBUG - wire << "Host: localhost:9763[\r][\n]"
[2016-06-18 15:46:33,305] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2016-06-18 15:46:33,305] DEBUG - wire << "User-Agent:
Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-06-18 15:46:33,306] DEBUG - wire << "[\r][\n]"
[2016-06-18 15:46:33,307] DEBUG - wire >> "HTTP/1.1 200 OK[\r][\n]"
[2016-06-18 15:46:33,307] DEBUG - wire >> "Content-Type: text/html[\r][\n]"
[2016-06-18 15:46:33,308] DEBUG - wire >> "Content-Length: 193[\r][\n]"
[2016-06-18 15:46:33,308] DEBUG - wire >> "Date: Sat, 18 Jun 2016 10:16:33
GMT[\r][\n]"
[2016-06-18 15:46:33,309] DEBUG - wire >> "Server: WSO2 Carbon
Server[\r][\n]"
[2016-06-18 15:46:33,309] DEBUG - wire >> "[\r][\n]"
[2016-06-18 15:46:33,310] DEBUG - wire >> "[\n]"
[2016-06-18 15:46:33,310] DEBUG - wire >> "  [\n]"
[2016-06-18 15:46:33,311] DEBUG - wire >> "  [\n]"
[2016-06-18 15:46:33,312] DEBUG - wire >> ""
[2016-06-18 15:46:33,322] DEBUG - wire << "HTTP/1.1 200 OK[\r][\n]"
[2016-06-18 15:46:33,323] DEBUG - wire << "Content-Type: text/html[\r][\n]"
[2016-06-18 15:46:33,323] DEBUG - wire << "Date: Sat, 18 Jun 2016 10:16:33
GMT[\r][\n]"
[2016-06-18 15:46:33,324] DEBUG - wire << "Transfer-Encoding:
chunked[\r][\n]"
[2016-06-18 15:46:33,324] DEBUG - wire << "[\r][\n]"
[2016-06-18 15:46:33,324] DEBUG - wire << "c1[\r][\n]"
[2016-06-18 15:46:33,325] DEBUG - wire << "[\n]"
[2016-06-18 15:46:33,325] DEBUG - wire << "  [\n]"
[2016-06-18 15:46:33,325] DEBUG - wire << "  [\n]"
[2016-06-18 15:46:33,326] DEBUG - wire << "[\r][\n]"
[2016-06-18 15:46:33,326] DEBUG - wire << "0[\r][\n]"
[2016-06-18 15:46:33,327] DEBUG - wire << "[\r][\n]"

Regards,
Dinusha.


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Releasing carbon-appmgt 1.1.3

[Dinusha Senanayaka]

Thanks Kishanthan.

Done the release perform again. Can you send the new staging URL too?

Regards,
Disnuha.

On Thu, May 12, 2016 at 7:57 PM, Kishanthan Thangarajah <kishant...@wso2.com
> wrote:

> Done
>
> On Thu, May 12, 2016 at 7:54 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> +Kishanthan
>>
>> On Thu, May 12, 2016 at 7:52 PM, Dinusha Senanayaka <dinu...@wso2.com>
>> wrote:
>>
>>> Hi Maheshika,
>>>
>>> Can you please drop the  staging repo again.
>>>
>>>
>>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonappmgt-1001/
>>>
>>> Regards,
>>> Dinusha.
>>>
>>> On Wed, May 11, 2016 at 8:03 PM, Hasunie Adikari <hasu...@wso2.com>
>>> wrote:
>>>
>>>> Hi Thilini,
>>>>
>>>> There was a issue in installing mobile apps from AppStore.I'm getting
>>>> following backend error and INSTALL_APPLICATION operation is also not added
>>>> to the operation table.
>>>>
>>>> [2016-05-11 19:51:35,641] ERROR
>>>> {org.jaggeryjs.jaggery.core.manager.WebAppManager} -
>>>> org.mozilla.javascript.EcmaError: TypeError: Cannot call method "split" of
>>>> undefined 
>>>> (/store/extensions/assets/mobileapp/modules/mod-ent-install.js#31)
>>>> org.jaggeryjs.scriptengine.exceptions.ScriptException:
>>>> org.mozilla.javascript.EcmaError: TypeError: Cannot call method "split" of
>>>> undefined 
>>>> (/store/extensions/assets/mobileapp/modules/mod-ent-install.js#31)
>>>> at
>>>> org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:571)
>>>> at
>>>> org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
>>>> at
>>>> org.jaggeryjs.jaggery.core.manager.WebAppManager.exec(WebAppManager.java:587)
>>>> at
>>>> org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:507)
>>>> at
>>>> org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(JaggeryServlet.java:29)
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>>>> at
>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>>>> at
>>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>>>> at
>>>> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
>>>> at
>>>> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486)
>>>> at
>>>> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:378)
>>>> at
>>>> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338)
>>>> at
>>>> org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21)
>>>> at
>>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>>>> 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.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
>>>> at
>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>>>> at
>>>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
>>>> at
>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
>>>> at
>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
>>>> at
>>>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>>>> at
>>>&

Re: [Dev] Releasing carbon-appmgt 1.1.3

[Dinusha Senanayaka]

+Kishanthan

On Thu, May 12, 2016 at 7:52 PM, Dinusha Senanayaka <dinu...@wso2.com>
wrote:

> Hi Maheshika,
>
> Can you please drop the  staging repo again.
>
> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonappmgt-1001/
>
> Regards,
> Dinusha.
>
> On Wed, May 11, 2016 at 8:03 PM, Hasunie Adikari <hasu...@wso2.com> wrote:
>
>> Hi Thilini,
>>
>> There was a issue in installing mobile apps from AppStore.I'm getting
>> following backend error and INSTALL_APPLICATION operation is also not added
>> to the operation table.
>>
>> [2016-05-11 19:51:35,641] ERROR
>> {org.jaggeryjs.jaggery.core.manager.WebAppManager} -
>> org.mozilla.javascript.EcmaError: TypeError: Cannot call method "split" of
>> undefined (/store/extensions/assets/mobileapp/modules/mod-ent-install.js#31)
>> org.jaggeryjs.scriptengine.exceptions.ScriptException:
>> org.mozilla.javascript.EcmaError: TypeError: Cannot call method "split" of
>> undefined (/store/extensions/assets/mobileapp/modules/mod-ent-install.js#31)
>> at
>> org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:571)
>> at
>> org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
>> at
>> org.jaggeryjs.jaggery.core.manager.WebAppManager.exec(WebAppManager.java:587)
>> at
>> org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:507)
>> at
>> org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(JaggeryServlet.java:29)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:378)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338)
>> at
>> org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> 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.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
>> at
>> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
>> at
>> org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve.invoke(WebappAuthenticationValve.java:44)
>> at
>> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
>> at
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
>> at
>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)

Re: [Dev] Releasing carbon-appmgt 1.1.3

[Dinusha Senanayaka]

ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.mozilla.javascript.EcmaError: TypeError: Cannot call method
> "split" of undefined
> (/store/extensions/assets/mobileapp/modules/mod-ent-install.js#31)
> at
> org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3687)
> at
> org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3665)
> at
> org.mozilla.javascript.ScriptRuntime.typeError(ScriptRuntime.java:3693)
> at
> org.mozilla.javascript.ScriptRuntime.typeError2(ScriptRuntime.java:3712)
> at
> org.mozilla.javascript.ScriptRuntime.undefCallError(ScriptRuntime.java:3731)
> at
> org.mozilla.javascript.ScriptRuntime.getPropFunctionAndThisHelper(ScriptRuntime.java:2258)
> at
> org.mozilla.javascript.ScriptRuntime.getPropFunctionAndThis(ScriptRuntime.java:2251)
> at
> org.jaggeryjs.rhino.store.extensions.assets.mobileapp.modules.c1._c_performAction_1(/store/extensions/assets/mobileapp/modules/mod-ent-install.js:31)
> at
> org.jaggeryjs.rhino.store.extensions.assets.mobileapp.modules.c1.call(/store/extensions/assets/mobileapp/modules/mod-ent-install.js)
> at
> org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
> at
> org.jaggeryjs.rhino.store.extensions.assets.mobileapp.c1._c_anonymous_3(/store/extensions/assets/mobileapp/apis.jag:52)
> at
> org.jaggeryjs.rhino.store.extensions.assets.mobileapp.c1.call(/store/extensions/assets/mobileapp/apis.jag)
> at
> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
> at
> org.jaggeryjs.rhino.store.modules.c12._c_anonymous_13(/store/modules/goose.js:174)
> at org.jaggeryjs.rhino.store.modules.c12.call(/store/modules/goose.js)
> at
> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
> at
> org.jaggeryjs.rhino.store.extensions.assets.mobileapp.c1._c_script_0(/store/extensions/assets/mobileapp/apis.jag:96)
> at
> org.jaggeryjs.rhino.store.extensions.assets.mobileapp.c1.call(/store/extensions/assets/mobileapp/apis.jag)
> at
> org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
> at
> org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
> at
> org.jaggeryjs.rhino.store.extensions.assets.mobileapp.c1.call(/store/extensions/assets/mobileapp/apis.jag)
> at
> org.jaggeryjs.rhino.store.extensions.assets.mobileapp.c1.exec(/store/extensions/assets/mobileapp/apis.jag)
> at
> org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:567)
> ... 42 more
>
>
> On Wed, May 11, 2016 at 1:54 PM, Hasunie Adikari <hasu...@wso2.com> wrote:
>
>> Hi Dinusha,
>>
>> Noted.
>>
>> Thanks
>>
>> On Wed, May 11, 2016 at 1:30 PM, Dinusha Senanayaka <dinu...@wso2.com>
>> wrote:
>>
>>> Thanks Maheshika. @Hasunie: Please note.
>>>
>>> On Wed, May 11, 2016 at 1:20 PM, Maheshika Goonetilleke <
>>> mahesh...@wso2.com> wrote:
>>>
>>>> H Dinusha
>>>>
>>>> Staged;
>>>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonappmgt-1001/
>>>>
>>>> On Wed, May 11, 2016 at 12:27 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Maheshika,
>>>>>
>>>>> Can you stage this again and send the URL.
>>>>>
>>>>> Regards,
>>>>> Dinusha.
>>>>>
>>>>> On Tue, May 10, 2016 at 6:45 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Maheshika, Please drop the staging repo. We will let you know once
>>>>>> issue is fixed and ready to re-stage.
>>>>>>
>>>>>> Regards,
>>>>>> Dinusha.
>>>>>>
>>>>>> On Tue, May 10, 2016 at 6:42 PM, Thilini Shanika <thili...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Hasunie,
>>>>>>>
>>>>>>> The issue is fixed and committed to release-1.1.3 branch [1].
>>>>>>>
>>>>>>> [1] -
>>>>>>> https://github.com/wso2/carbon-appmgt/commit/db32a4d989457066f38f77be16babd3f1926626f
>>>>>>>
>>>>>>> On Tue, May 10, 2016 a

Re: [Dev] Releasing carbon-appmgt 1.1.3

[Dinusha Senanayaka]

Thanks Maheshika. @Hasunie: Please note.

On Wed, May 11, 2016 at 1:20 PM, Maheshika Goonetilleke <mahesh...@wso2.com>
wrote:

> H Dinusha
>
> Staged;
> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonappmgt-1001/
>
> On Wed, May 11, 2016 at 12:27 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi Maheshika,
>>
>> Can you stage this again and send the URL.
>>
>> Regards,
>> Dinusha.
>>
>> On Tue, May 10, 2016 at 6:45 PM, Dinusha Senanayaka <dinu...@wso2.com>
>> wrote:
>>
>>> Maheshika, Please drop the staging repo. We will let you know once issue
>>> is fixed and ready to re-stage.
>>>
>>> Regards,
>>> Dinusha.
>>>
>>> On Tue, May 10, 2016 at 6:42 PM, Thilini Shanika <thili...@wso2.com>
>>> wrote:
>>>
>>>> Hi Hasunie,
>>>>
>>>> The issue is fixed and committed to release-1.1.3 branch [1].
>>>>
>>>> [1] -
>>>> https://github.com/wso2/carbon-appmgt/commit/db32a4d989457066f38f77be16babd3f1926626f
>>>>
>>>> On Tue, May 10, 2016 at 6:23 PM, Inosh Perera <ino...@wso2.com> wrote:
>>>>
>>>>> +Dinusha
>>>>>
>>>>> On Tue, May 10, 2016 at 6:20 PM, Hasunie Adikari <hasu...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Dinusha,
>>>>>>
>>>>>> There was a issue in getting image of the Mobile App icon from get
>>>>>> all assets option in AppStore( /store/assets), but its working properly
>>>>>> while its getting from Mobile apps option( ./store/assets/mobileapp ). It
>>>>>> seems instead of getting image path, it just takes the file name of the
>>>>>> image.
>>>>>>
>>>>>> thanks.
>>>>>>
>>>>>> On Thu, May 5, 2016 at 8:35 AM, Dinusha Senanayaka <dinu...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks Maheshika.
>>>>>>>
>>>>>>> @EMM Team, please verify and confirm.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Dinusha.
>>>>>>>
>>>>>>> On Thu, May 5, 2016 at 8:29 AM, Maheshika Goonetilleke <
>>>>>>> mahesh...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi Dinusha
>>>>>>>>
>>>>>>>> Staged
>>>>>>>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonappmgt-1000/
>>>>>>>>
>>>>>>>> On Wed, May 4, 2016 at 11:37 PM, Dinusha Senanayaka <
>>>>>>>> dinu...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Build team,
>>>>>>>>>
>>>>>>>>> Please stage carbon-appmgt-1.1.3.
>>>>>>>>>
>>>>>>>>> org.wso2.carbon.appmgt
>>>>>>>>> carbon-appmgt
>>>>>>>>> 1.1.3
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Dinusha.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Dinusha Dilrukshi
>>>>>>>>> Associate Technical Lead
>>>>>>>>> WSO2 Inc.: http://wso2.com/
>>>>>>>>> Mobile: +94725255071
>>>>>>>>> Blog: http://dinushasblog.blogspot.com/
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Thanks & Best Regards,
>>>>>>>>
>>>>>>>> Maheshika Goonetilleke
>>>>>>>> Engineering Process Coordinator
>>>>>>>>
>>>>>>>> *WSO2 Inc*
>>>>>>>> *email   : mahesh...@wso2.com <mahesh...@wso2.com>*
>>>>>>>> *mobile : +94 773 596707 <%2B94%20773%20596707>*
>>>>>>>> *www: :http://wso2.com <http://wso2.com/>*lean . enterprise .
>>>>>>>> middleware
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>

Re: [Dev] Releasing carbon-appmgt 1.1.3

[Dinusha Senanayaka]

Hi Maheshika,

Can you stage this again and send the URL.

Regards,
Dinusha.

On Tue, May 10, 2016 at 6:45 PM, Dinusha Senanayaka <dinu...@wso2.com>
wrote:

> Maheshika, Please drop the staging repo. We will let you know once issue
> is fixed and ready to re-stage.
>
> Regards,
> Dinusha.
>
> On Tue, May 10, 2016 at 6:42 PM, Thilini Shanika <thili...@wso2.com>
> wrote:
>
>> Hi Hasunie,
>>
>> The issue is fixed and committed to release-1.1.3 branch [1].
>>
>> [1] -
>> https://github.com/wso2/carbon-appmgt/commit/db32a4d989457066f38f77be16babd3f1926626f
>>
>> On Tue, May 10, 2016 at 6:23 PM, Inosh Perera <ino...@wso2.com> wrote:
>>
>>> +Dinusha
>>>
>>> On Tue, May 10, 2016 at 6:20 PM, Hasunie Adikari <hasu...@wso2.com>
>>> wrote:
>>>
>>>> Hi Dinusha,
>>>>
>>>> There was a issue in getting image of the Mobile App icon from get all
>>>> assets option in AppStore( /store/assets), but its working properly while
>>>> its getting from Mobile apps option( ./store/assets/mobileapp ). It seems
>>>> instead of getting image path, it just takes the file name of the image.
>>>>
>>>> thanks.
>>>>
>>>> On Thu, May 5, 2016 at 8:35 AM, Dinusha Senanayaka <dinu...@wso2.com>
>>>> wrote:
>>>>
>>>>> Thanks Maheshika.
>>>>>
>>>>> @EMM Team, please verify and confirm.
>>>>>
>>>>> Regards,
>>>>> Dinusha.
>>>>>
>>>>> On Thu, May 5, 2016 at 8:29 AM, Maheshika Goonetilleke <
>>>>> mahesh...@wso2.com> wrote:
>>>>>
>>>>>> Hi Dinusha
>>>>>>
>>>>>> Staged
>>>>>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonappmgt-1000/
>>>>>>
>>>>>> On Wed, May 4, 2016 at 11:37 PM, Dinusha Senanayaka <dinu...@wso2.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi Build team,
>>>>>>>
>>>>>>> Please stage carbon-appmgt-1.1.3.
>>>>>>>
>>>>>>> org.wso2.carbon.appmgt
>>>>>>> carbon-appmgt
>>>>>>> 1.1.3
>>>>>>>
>>>>>>> Regards,
>>>>>>> Dinusha.
>>>>>>>
>>>>>>> --
>>>>>>> Dinusha Dilrukshi
>>>>>>> Associate Technical Lead
>>>>>>> WSO2 Inc.: http://wso2.com/
>>>>>>> Mobile: +94725255071
>>>>>>> Blog: http://dinushasblog.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Thanks & Best Regards,
>>>>>>
>>>>>> Maheshika Goonetilleke
>>>>>> Engineering Process Coordinator
>>>>>>
>>>>>> *WSO2 Inc*
>>>>>> *email   : mahesh...@wso2.com <mahesh...@wso2.com>*
>>>>>> *mobile : +94 773 596707 <%2B94%20773%20596707>*
>>>>>> *www: :http://wso2.com <http://wso2.com/>*lean . enterprise .
>>>>>> middleware
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Dinusha Dilrukshi
>>>>> Associate Technical Lead
>>>>> WSO2 Inc.: http://wso2.com/
>>>>> Mobile: +94725255071
>>>>> Blog: http://dinushasblog.blogspot.com/
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "WSO2 Engineering Group" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to engineering-group+unsubscr...@wso2.com.
>>>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Hasunie Adikari*
>>>> Software Engineer
>>>> WSO2 Inc.; http://wso2.com
>>>> lean.enterprise.middleware
>>>> blog http://hasuniea.blogspot.com
>>>> Mobile:+94715139495
>>>>
>>>
>>>
>>>
>>> --
>>> Inosh Perera
>>> Software Engineer, WSO2 Inc.
>>> Tel: 077813 7285, 0785293686
>>>
>>
>>
>>
>> --
>> Thilini Shanika
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>> 20, Palmgrove Avenue, Colombo 3
>>
>> E-mail: tgtshan...@gmail.com
>>
>>
>
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading App Manager to user Carbon Kernel 4.4.5

[Dinusha Senanayaka]

Also, if we update to latest SNAPSHOT versions of identity dependencies
will that compatible with IS-5.1.0 too ? (we are using service calls to add
SP, XACML policies etc).

On Tue, May 10, 2016 at 7:41 PM, Dinusha Senanayaka <dinu...@wso2.com>
wrote:

> Hi Johann,
>
> With the kernel-4.4.5 migration of AppM, we could not used released
> version of identity dependencies due to the issue,  Rushmin has originally
> mentioned. As per the offline discussion had with team, identity repo was
> going to release in a one week of time issue was reported. Hence we updated
> AppM p2-repo to use snapshot versions without requesting for a component
> repo release. But now, identity team has changed the versions of identity
> snapshot versions and it has caused AppManager build failure [1].
>
> We could check and change AppM identity dependencies to the snapshot
> versions that you are currently having, but if the release is not going to
> happen soon and there are considerable active developments going on
> identity repos, this won't be a solution for us. Can we get a separate
> identity component release or other solution for this  ASAP?
>
> [1] https://wso2.org/jenkins/job/product-app-manager/261/
>
> Cannot complete the install because one or more required items could not be 
> found.
>  Software being installed: WSO2 Carbon - APP Publisher Feature 1.1.4.SNAPSHOT 
> (org.wso2.carbon.appmgt.publisher.feature.group 1.1.4.SNAPSHOT)
>  Missing requirement: org.wso2.carbon.appmgt.impl 1.1.4.SNAPSHOT 
> (org.wso2.carbon.appmgt.impl 1.1.4.SNAPSHOT) requires 'package 
> org.wso2.carbon.identity.entitlement.proxy [5.0.7,5.1.0)' but it could not be 
> found
>
>
>
> Regards,
> Dinusha.
>
>
>
> On Tue, Apr 12, 2016 at 10:24 AM, Pushpalanka Jayawardhana <la...@wso2.com
> > wrote:
>
>>
>>
>> On Tue, Apr 12, 2016 at 6:58 AM, Johann Nallathamby <joh...@wso2.com>
>> wrote:
>>
>>> @Pushpalanka: Isn't the repo versions (all the repos, now that we have
>>> 46 IINM maintained by IS team) going to be 5.10.0 since we have backward
>>> compatible API additions ?
>>>
>> Yes my mistake.. Next release version will be *5.1.0.*
>>
>>>
>>> On Mon, Apr 11, 2016 at 3:40 AM, Pushpalanka Jayawardhana <
>>> la...@wso2.com> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Apr 11, 2016 at 1:53 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi IS Team,
>>>>>
>>>>> Do you have release date for identity-5.0.9 ? This fix is critical for
>>>>> App manager release.
>>>>>
>>>> We are working on to release the beta pack tomorrow.  Identity-5.0.9
>>>> release will be done with the RC pack, which will be by 25th in best case.
>>>>
>>>>>
>>>>> Regards,
>>>>> Dinusha.
>>>>>
>>>>> On Mon, Apr 4, 2016 at 10:34 AM, Rushmin Fernando <rush...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Thanks Pulasthi !
>>>>>>
>>>>>> App Manager WIP code can be found in [1] and [2]
>>>>>>
>>>>>> Thanks
>>>>>> Rushmin
>>>>>>
>>>>>> [1] -
>>>>>> https://github.com/wso2/carbon-appmgt/tree/feature/kernel-4.4.5-upgrade
>>>>>>
>>>>>> [2]  -
>>>>>> https://github.com/wso2/product-app-manager/tree/feature/kernel-4.4.5-upgrade
>>>>>>
>>>>>> On Fri, Apr 1, 2016 at 4:52 PM, Pulasthi Mahawithana <
>>>>>> pulast...@wso2.com> wrote:
>>>>>>
>>>>>>> Yes, we no longer use the wso2/carbon-identity repo for development.
>>>>>>> We use the repos in 'wso2-extensions'. However the group ids, artifact 
>>>>>>> ids
>>>>>>> and versions follow the same from carbon-identity.
>>>>>>>
>>>>>>> On Fri, Apr 1, 2016 at 3:56 PM, Rushmin Fernando <rush...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks Supun !
>>>>>>>>
>>>>>>>> So is [1] obsolete now since the connector code resides in
>>>>>>>> 'wso2-extensions' account now ?
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Rushmin
>>>>>>>>
>>>>>>>>

Re: [Dev] Upgrading App Manager to user Carbon Kernel 4.4.5

[Dinusha Senanayaka]

Hi Johann,

With the kernel-4.4.5 migration of AppM, we could not used released version
of identity dependencies due to the issue,  Rushmin has originally
mentioned. As per the offline discussion had with team, identity repo was
going to release in a one week of time issue was reported. Hence we updated
AppM p2-repo to use snapshot versions without requesting for a component
repo release. But now, identity team has changed the versions of identity
snapshot versions and it has caused AppManager build failure [1].

We could check and change AppM identity dependencies to the snapshot
versions that you are currently having, but if the release is not going to
happen soon and there are considerable active developments going on
identity repos, this won't be a solution for us. Can we get a separate
identity component release or other solution for this  ASAP?

[1] https://wso2.org/jenkins/job/product-app-manager/261/

Cannot complete the install because one or more required items could
not be found.
 Software being installed: WSO2 Carbon - APP Publisher Feature
1.1.4.SNAPSHOT (org.wso2.carbon.appmgt.publisher.feature.group
1.1.4.SNAPSHOT)
 Missing requirement: org.wso2.carbon.appmgt.impl 1.1.4.SNAPSHOT
(org.wso2.carbon.appmgt.impl 1.1.4.SNAPSHOT) requires 'package
org.wso2.carbon.identity.entitlement.proxy [5.0.7,5.1.0)' but it could
not be found



Regards,
Dinusha.



On Tue, Apr 12, 2016 at 10:24 AM, Pushpalanka Jayawardhana <la...@wso2.com>
wrote:

>
>
> On Tue, Apr 12, 2016 at 6:58 AM, Johann Nallathamby <joh...@wso2.com>
> wrote:
>
>> @Pushpalanka: Isn't the repo versions (all the repos, now that we have 46
>> IINM maintained by IS team) going to be 5.10.0 since we have backward
>> compatible API additions ?
>>
> Yes my mistake.. Next release version will be *5.1.0.*
>
>>
>> On Mon, Apr 11, 2016 at 3:40 AM, Pushpalanka Jayawardhana <la...@wso2.com
>> > wrote:
>>
>>>
>>>
>>> On Mon, Apr 11, 2016 at 1:53 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>> wrote:
>>>
>>>> Hi IS Team,
>>>>
>>>> Do you have release date for identity-5.0.9 ? This fix is critical for
>>>> App manager release.
>>>>
>>> We are working on to release the beta pack tomorrow.  Identity-5.0.9
>>> release will be done with the RC pack, which will be by 25th in best case.
>>>
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>> On Mon, Apr 4, 2016 at 10:34 AM, Rushmin Fernando <rush...@wso2.com>
>>>> wrote:
>>>>
>>>>> Thanks Pulasthi !
>>>>>
>>>>> App Manager WIP code can be found in [1] and [2]
>>>>>
>>>>> Thanks
>>>>> Rushmin
>>>>>
>>>>> [1] -
>>>>> https://github.com/wso2/carbon-appmgt/tree/feature/kernel-4.4.5-upgrade
>>>>>
>>>>> [2]  -
>>>>> https://github.com/wso2/product-app-manager/tree/feature/kernel-4.4.5-upgrade
>>>>>
>>>>> On Fri, Apr 1, 2016 at 4:52 PM, Pulasthi Mahawithana <
>>>>> pulast...@wso2.com> wrote:
>>>>>
>>>>>> Yes, we no longer use the wso2/carbon-identity repo for development.
>>>>>> We use the repos in 'wso2-extensions'. However the group ids, artifact 
>>>>>> ids
>>>>>> and versions follow the same from carbon-identity.
>>>>>>
>>>>>> On Fri, Apr 1, 2016 at 3:56 PM, Rushmin Fernando <rush...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks Supun !
>>>>>>>
>>>>>>> So is [1] obsolete now since the connector code resides in
>>>>>>> 'wso2-extensions' account now ?
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>> Rushmin
>>>>>>>
>>>>>>> [1] -
>>>>>>> https://github.com/wso2/carbon-identity/blob/master/features/provisioning/org.wso2.carbon.identity.provisioning.connector.salesforce.server.feature
>>>>>>>
>>>>>>> On Fri, Apr 1, 2016 at 3:47 PM, Pulasthi Mahawithana <
>>>>>>> pulast...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi Rushmin,
>>>>>>>>
>>>>>>>> This issue was due to that component being moved from
>>>>>>>> carbon-commons to analytic commons. Isura fixed that issue with [1] and
>>>>>>>> [2]. Can you please try now?

Re: [Dev] Releasing carbon-appmgt 1.1.3

[Dinusha Senanayaka]

Maheshika, Please drop the staging repo. We will let you know once issue is
fixed and ready to re-stage.

Regards,
Dinusha.

On Tue, May 10, 2016 at 6:42 PM, Thilini Shanika <thili...@wso2.com> wrote:

> Hi Hasunie,
>
> The issue is fixed and committed to release-1.1.3 branch [1].
>
> [1] -
> https://github.com/wso2/carbon-appmgt/commit/db32a4d989457066f38f77be16babd3f1926626f
>
> On Tue, May 10, 2016 at 6:23 PM, Inosh Perera <ino...@wso2.com> wrote:
>
>> +Dinusha
>>
>> On Tue, May 10, 2016 at 6:20 PM, Hasunie Adikari <hasu...@wso2.com>
>> wrote:
>>
>>> Hi Dinusha,
>>>
>>> There was a issue in getting image of the Mobile App icon from get all
>>> assets option in AppStore( /store/assets), but its working properly while
>>> its getting from Mobile apps option( ./store/assets/mobileapp ). It seems
>>> instead of getting image path, it just takes the file name of the image.
>>>
>>> thanks.
>>>
>>> On Thu, May 5, 2016 at 8:35 AM, Dinusha Senanayaka <dinu...@wso2.com>
>>> wrote:
>>>
>>>> Thanks Maheshika.
>>>>
>>>> @EMM Team, please verify and confirm.
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>> On Thu, May 5, 2016 at 8:29 AM, Maheshika Goonetilleke <
>>>> mahesh...@wso2.com> wrote:
>>>>
>>>>> Hi Dinusha
>>>>>
>>>>> Staged
>>>>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonappmgt-1000/
>>>>>
>>>>> On Wed, May 4, 2016 at 11:37 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Build team,
>>>>>>
>>>>>> Please stage carbon-appmgt-1.1.3.
>>>>>>
>>>>>> org.wso2.carbon.appmgt
>>>>>> carbon-appmgt
>>>>>> 1.1.3
>>>>>>
>>>>>> Regards,
>>>>>> Dinusha.
>>>>>>
>>>>>> --
>>>>>> Dinusha Dilrukshi
>>>>>> Associate Technical Lead
>>>>>> WSO2 Inc.: http://wso2.com/
>>>>>> Mobile: +94725255071
>>>>>> Blog: http://dinushasblog.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Thanks & Best Regards,
>>>>>
>>>>> Maheshika Goonetilleke
>>>>> Engineering Process Coordinator
>>>>>
>>>>> *WSO2 Inc*
>>>>> *email   : mahesh...@wso2.com <mahesh...@wso2.com>*
>>>>> *mobile : +94 773 596707 <%2B94%20773%20596707>*
>>>>> *www: :http://wso2.com <http://wso2.com/>*lean . enterprise .
>>>>> middleware
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Dinusha Dilrukshi
>>>> Associate Technical Lead
>>>> WSO2 Inc.: http://wso2.com/
>>>> Mobile: +94725255071
>>>> Blog: http://dinushasblog.blogspot.com/
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "WSO2 Engineering Group" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to engineering-group+unsubscr...@wso2.com.
>>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> *Hasunie Adikari*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>> blog http://hasuniea.blogspot.com
>>> Mobile:+94715139495
>>>
>>
>>
>>
>> --
>> Inosh Perera
>> Software Engineer, WSO2 Inc.
>> Tel: 077813 7285, 0785293686
>>
>
>
>
> --
> Thilini Shanika
> Software Engineer
> WSO2, Inc.; http://wso2.com
> 20, Palmgrove Avenue, Colombo 3
>
> E-mail: tgtshan...@gmail.com
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][AppM] Cannot add web application 'Failed to add asset.'

[Dinusha Senanayaka]

Hi Chanuka,

This seems to be a issue with setting permissions to registry resource in
mounted environment [1]. Will provide a patch ASAP.

[1] https://wso2.org/jira/browse/REGISTRY-2214

Regards,
Dinusha.

On Mon, May 2, 2016 at 12:14 PM, Chanuka Dissanayake <chan...@wso2.com>
wrote:

> What is the deployment ? Not a standalone setup of 1.2.0-M3 right ?
>
>
> Yes, not a standalone. I have tried a new app but same error.
>
> Did you check the the permissions section in the resource metadata page in
>> registry browser. Were they properly set?
>>
>> @jithendra, could you check this.
>
> On Mon, May 2, 2016 at 12:02 PM, Denuwanthi De Silva <denuwan...@wso2.com>
> wrote:
>
>> Hi Chanuka,
>>
>> Did you check the the permissions section in the resource metadata page
>> in registry browser. Were they properly set?
>> Check the user core versions as it could be related to issues at [1][2].
>>
>> [1]https://wso2.org/jira/browse/CARBON-15771
>> [2]https://wso2.org/jira/browse/IDENTITY-4291
>>
>> On Mon, May 2, 2016 at 11:52 AM, Dinusha Senanayaka <dinu...@wso2.com>
>> wrote:
>>
>>> Hi Chanuka,
>>>
>>> What is the deployment ? Not a standalone setup of 1.2.0-M3 right ?
>>> Btw, it says web app already exist. May be transaction failed at
>>> intermediate state, if you tried to add it several times. Can you try
>>> adding new app with different name and context too.
>>>
>>> Regards,
>>> Dinusha.
>>>
>>> On Mon, May 2, 2016 at 11:46 AM, Chanuka Dissanayake <chan...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> AppM version : 1.2.0 M3.
>>>> I'm getting the $subject while trying to add an application *[1]* (I
>>>> have the required permission). But when I tried to add the same application
>>>> again, it's mentioning, Message,
>>>>
>>>>
>>>> *Error occurred while adding the WebApp. A duplicate WebApp already
>>>> exists with name - 'MyApp' and version - '1.0.0'*
>>>>
>>>> *[1]*
>>>>
>>>> TID: [-1234] [] [2016-05-02 11:29:55,652]  WARN
>>>> {org.wso2.carbon.registry.core.jdbc.Repository} -  User
>>>> chan...@wso2.com is not authorized to read the resource
>>>> /_system/governance/appmgt/applicationdata/provider/chanuka-AT-wso2.com/MyApp/1.0.0/webapp.
>>>> {org.wso2.carbon.registry.core.jdbc.Repository}
>>>> TID: [-1234] [] [2016-05-02 11:29:55,660] ERROR
>>>> {JAGGERY.assets.default.asset:jag} -
>>>>  org.mozilla.javascript.WrappedException: Wrapped
>>>> org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
>>>> Resource does not exist at path
>>>> /_system/governance/appmgt/applicationdata/provider/chanuka-AT-wso2.com/MyApp/1.0.0/webapp
>>>> (/scripts/registry/registry-osgi.js#268)
>>>> at
>>>> org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
>>>> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
>>>> at
>>>> org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
>>>> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
>>>> at
>>>> org.jaggeryjs.rhino..scripts.registry.c0._c_anonymous_25(/scripts/registry/registry-osgi.js:268)
>>>> at
>>>> org.jaggeryjs.rhino..scripts.registry.c0.call(/scripts/registry/registry-osgi.js)
>>>> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
>>>> at
>>>> org.jaggeryjs.rhino..scripts.registry.c0._c_anonymous_25(/scripts/registry/artifacts.js:360)
>>>> at
>>>> org.jaggeryjs.rhino..scripts.registry.c0.call(/scripts/registry/artifacts.js)
>>>> at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
>>>> at
>>>> org.jaggeryjs.rhino.publisher.modules.ext.scripts.c5._c_anonymous_2(/publisher/modules/ext/scripts/asset.lifecycle.action.save.js:70)
>>>> at
>>>> org.jaggeryjs.rhino.publisher.modules.ext.scripts.c5.call(/publisher/modules/ext/scripts/asset.lifecycle.action.save.js)
>>>> at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
>>>> at
>>>> org.jaggeryjs.rhino.publisher.modules.ext.core.c2._c_anonymous_14(/publisher/modules/ext/core/extension.core.js:235)
>>>> at
>>>> org.jaggeryjs.rhino.publisher.modules.ext.core.c2.call(/publisher/modules/ext/core/extension.core.js)
>>&g

Re: [Dev] [AppM] Response field filter for REST API

[Dinusha Senanayaka]

On Thu, Apr 28, 2016 at 4:28 PM, Lahiru Cooray <lahi...@wso2.com> wrote:

> +1
> since the query param name already indicates it is a field filter, how
> about:
> ?field_filter=basic
> ?field_filter=all
>
+1

>
>
>
> On Thu, Apr 28, 2016 at 3:54 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> As we discussed offline, best option for this is to have a API that user
>> could define fields that he needed (eg: described in [1]). That need some
>> effort we cannot afford with the time fact right now and we know that, most
>> of the use cases can be addressed having two filters like Lahiru suggested.
>> How about following.
>>
>> *?field_filter=basicFields*
>> *?field_filter=allFields*
>>
>> [1]
>> http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api#limiting-fields
>>
>> Regards,
>> Dinusha.
>>
>> On Thu, Apr 28, 2016 at 3:22 PM, Dilshan Edirisuriya <
>> ed.dils...@gmail.com> wrote:
>>
>>> Sorry I didnt get the context initially.
>>>
>>> On 28 April 2016 at 11:06, Lahiru Cooray <lahi...@wso2.com> wrote:
>>>
>>>> Hi Dilshan,
>>>> Yes we have followed the offset/limit approach to limit the response
>>>> length (eg: no of apps returned)
>>>> But here our requirement is to limit the data/field in response (eg:
>>>> attributes of an app)
>>>>
>>>>
>>>> On Thu, Apr 28, 2016 at 11:03 AM, Dilshan Edirisuriya <
>>>> ed.dils...@gmail.com> wrote:
>>>>
>>>>> As in other products[1] why don't you follow the limit offset
>>>>> approach? It has to be consistent among the platform?
>>>>>
>>>>> [1] -
>>>>> https://github.com/wso2/product-emm/blob/master/modules/apps/jax-rs/mdm-admin/src/main/java/org/wso2/carbon/mdm/api/Operation.java
>>>>>
>>>>> Regards,
>>>>>
>>>>> Dilshan
>>>>>
>>>>> On 28 April 2016 at 10:53, Lahiru Cooray <lahi...@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>> We are currently implementing REST API for AppM and we need to
>>>>>> introduce a response field filter to limit the response(fields).
>>>>>> So I propose to use the a query param, *?field_filter=TOUCH*
>>>>>> (returns basic data which is default) and *?field_filter=ALL*
>>>>>> (returns complete dataset).
>>>>>> Please share your thoughts.
>>>>>>
>>>>>> *eg:*
>>>>>> /apps?field_filter=TOUCH (which is default)
>>>>>> {
>>>>>>   "previous": "",
>>>>>>   "next": "",
>>>>>>   "list": [
>>>>>> {
>>>>>>   "name": "app1",
>>>>>>   "context": "/app1",
>>>>>>   "id": "65c8485d-11d9-4f05-a418-17dfb737e165"
>>>>>> },
>>>>>> {
>>>>>>   "name": "app2",
>>>>>>   "context": "/app2",
>>>>>>   "id": "c9ddf00d-c42f-4299-931c-bcda69c68050"
>>>>>> }
>>>>>>   ],
>>>>>>   "count": 2
>>>>>> }
>>>>>>
>>>>>> /apps?field_filter=All
>>>>>> {
>>>>>>   "previous": "",
>>>>>>   "next": "",
>>>>>>   "list": [
>>>>>> {
>>>>>>   "name": "app1",
>>>>>>   "context": "/app1",
>>>>>>   "id": "65c8485d-11d9-4f05-a418-17dfb737e165",
>>>>>>   "provider": "admin",
>>>>>>   "description": " ",
>>>>>>   "version": "1.0",
>>>>>>   "lifecycleState": "CREATED"
>>>>>> },
>>>>>> {
>>>>>>   "name": "app2",
>>>>>>   "context": "/app2",
>>>>>>   "id": "c9ddf00d-c42f-4299-931c-bcda69c68050",
>>>>>>   "provider": "admin",
>>>>>>   "description": " ",
>>>>>>   "version": "1.0",
>>>>>>   "lifecycleState": "CREATED"
>>>>>> }
>>>>>>   ],
>>>>>>   "count": 2
>>>>>> }
>>>>>>
>>>>>> --
>>>>>> *Lahiru Cooray*
>>>>>> Software Engineer
>>>>>> WSO2, Inc.;http://wso2.com/
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> Mobile: +94 715 654154
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Lahiru Cooray*
>>>> Software Engineer
>>>> WSO2, Inc.;http://wso2.com/
>>>> lean.enterprise.middleware
>>>>
>>>> Mobile: +94 715 654154
>>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Dinusha Dilrukshi
>> Associate Technical Lead
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppM] Response field filter for REST API

[Dinusha Senanayaka]

As we discussed offline, best option for this is to have a API that user
could define fields that he needed (eg: described in [1]). That need some
effort we cannot afford with the time fact right now and we know that, most
of the use cases can be addressed having two filters like Lahiru suggested.
How about following.

*?field_filter=basicFields*
*?field_filter=allFields*

[1]
http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api#limiting-fields

Regards,
Dinusha.

On Thu, Apr 28, 2016 at 3:22 PM, Dilshan Edirisuriya 
wrote:

> Sorry I didnt get the context initially.
>
> On 28 April 2016 at 11:06, Lahiru Cooray  wrote:
>
>> Hi Dilshan,
>> Yes we have followed the offset/limit approach to limit the response
>> length (eg: no of apps returned)
>> But here our requirement is to limit the data/field in response (eg:
>> attributes of an app)
>>
>>
>> On Thu, Apr 28, 2016 at 11:03 AM, Dilshan Edirisuriya <
>> ed.dils...@gmail.com> wrote:
>>
>>> As in other products[1] why don't you follow the limit offset approach?
>>> It has to be consistent among the platform?
>>>
>>> [1] -
>>> https://github.com/wso2/product-emm/blob/master/modules/apps/jax-rs/mdm-admin/src/main/java/org/wso2/carbon/mdm/api/Operation.java
>>>
>>> Regards,
>>>
>>> Dilshan
>>>
>>> On 28 April 2016 at 10:53, Lahiru Cooray  wrote:
>>>
 Hi,
 We are currently implementing REST API for AppM and we need to
 introduce a response field filter to limit the response(fields).
 So I propose to use the a query param, *?field_filter=TOUCH* (returns
 basic data which is default) and *?field_filter=ALL* (returns complete
 dataset).
 Please share your thoughts.

 *eg:*
 /apps?field_filter=TOUCH (which is default)
 {
   "previous": "",
   "next": "",
   "list": [
 {
   "name": "app1",
   "context": "/app1",
   "id": "65c8485d-11d9-4f05-a418-17dfb737e165"
 },
 {
   "name": "app2",
   "context": "/app2",
   "id": "c9ddf00d-c42f-4299-931c-bcda69c68050"
 }
   ],
   "count": 2
 }

 /apps?field_filter=All
 {
   "previous": "",
   "next": "",
   "list": [
 {
   "name": "app1",
   "context": "/app1",
   "id": "65c8485d-11d9-4f05-a418-17dfb737e165",
   "provider": "admin",
   "description": " ",
   "version": "1.0",
   "lifecycleState": "CREATED"
 },
 {
   "name": "app2",
   "context": "/app2",
   "id": "c9ddf00d-c42f-4299-931c-bcda69c68050",
   "provider": "admin",
   "description": " ",
   "version": "1.0",
   "lifecycleState": "CREATED"
 }
   ],
   "count": 2
 }

 --
 *Lahiru Cooray*
 Software Engineer
 WSO2, Inc.;http://wso2.com/
 lean.enterprise.middleware

 Mobile: +94 715 654154

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


>>>
>>
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APPM] Having configurable Mobile Application Categories

[Dinusha Senanayaka]

Do we need this further since we having tags for mobile apps now ?

On Wed, Apr 27, 2016 at 3:16 PM, Jenananthan Yogendran  wrote:

>
>
> On Wed, Apr 27, 2016 at 3:06 PM, Thilini Shanika 
> wrote:
>
>> Hi all,
>>
>> In App Manager, we have mobile application categorization based on below
>> four criteria.
>>
>>- Business
>>- Communication
>>- Finance
>>- Productivity
>>
>> But these categories are not available as a configurable option and
>> currently we are having them as fixed values. But there is a requirement of
>> making these categories configurable.
>>
>> I would suggest below options to achieve this.
>>
>>1. Maintaining these categories as a configuration under
>>*MobileAppsConfiguration* in app-manager.xml
>>2. Maintaining categories in a registry resource so that we can
>>maintain different categories for different tenants
>>
>>+1 To have the configuration in registry.
>
>> Any suggestions or comments?
>>
>> Thanks,
>> Thilini
>> --
>> Thilini Shanika
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>> 20, Palmgrove Avenue, Colombo 3
>>
>> E-mail: tgtshan...@gmail.com
>>
>>
>
>
> --
> Jenananthan Yogendran
> *Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppManager] Fully qualified name issue in SAML response

[Dinusha Senanayaka]

Hi Darshana,

On Wed, Apr 27, 2016 at 12:28 PM, Darshana Gunawardana <darsh...@wso2.com>
wrote:

>
>
> On Tue, Apr 26, 2016 at 5:16 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> IS Team,
>>
>> Can you look into this issue please. This has broke the store/publisher
>> tenant login (We are using identity-5.0.9-SNAPSHOT versions).
>>
>> - How to set fully qualified name when registering SP from config file.
>> - Skip sending carbon.super when fully qualified name is enabled.
>>
>
> Why do you want to skip sending super tenant's domain? As I understood,
> app manager is a SaaS app and its ok to send super tenant's domain. It
> won't be an issue if you use correct utils to extract the tenant domain.
>

Issues comes with the store/publisher. In previous versions we did not have
carbon.super prefix in super tenant logged in users. We add subscriber name
to a table based on the logged in user name. Also there are some places
where we construct storage path of .apk files etc (mobile apps) using the
logged in user name. There is data migration effort if we go with the
carbon.super in user name in mentioned places. We could process the user
name and drop carbon.super part from the user name before we add user to
session. But not sure how much effort this required because we have to
check ES modules references too. Therefore, it would be great if we can
have the username without carbo.super prefix with super tenant users.

Regards,
Dinusha.

>
> Thanks,
>
>>
>> Regards,
>> Dinusha.
>>
>> On Mon, Apr 25, 2016 at 4:58 PM, Dinusha Senanayaka <dinu...@wso2.com>
>> wrote:
>>
>>> +Pushpalanka.
>>>
>>> On Mon, Apr 25, 2016 at 4:51 PM, Jenananthan Yogendran <
>>> jenanant...@wso2.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> After migrating the AppManager from kernel 4.2.0 to kernel 4.4.5  ,
>>>> fully qualified name is not working as expected.
>>>>
>>>> We use file based SP configuration for Store app and Publisher
>>>> app(attached sso-idp-config files used in both kernel versions). In kernel
>>>> 4.2.0 , when login to store/publisher app, SAML response has user name with
>>>> tenant domain  as subject for tenants except carbon super tenant.
>>>>
>>>> After migration , SAML response has only user name as subject.Tenant
>>>> domain is missing for tenants.
>>>>
>>>> Also when checked the option "Use tenant domain in local subject
>>>> identifier" under "Local & Outbound Authentication Configuration" for
>>>> SPs created through UI, it appends the "carbon.super" domain for super
>>>> tenant users.
>>>>
>>>> Thanks
>>>> --
>>>> Jenananthan Yogendran
>>>> *Software Engineer,*
>>>> *WSO2 inc., http://wso2.com <http://wso2.com>*
>>>>
>>>>
>>>
>>>
>>> --
>>> Dinusha Dilrukshi
>>> Associate Technical Lead
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94725255071
>>> Blog: http://dinushasblog.blogspot.com/
>>>
>>
>>
>>
>> --
>> Dinusha Dilrukshi
>> Associate Technical Lead
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Senior Software Engineer
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com <darsh...@wso2.com>*
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppManager] Fully qualified name issue in SAML response

[Dinusha Senanayaka]

IS Team,

Can you look into this issue please. This has broke the store/publisher
tenant login (We are using identity-5.0.9-SNAPSHOT versions).

- How to set fully qualified name when registering SP from config file.
- Skip sending carbon.super when fully qualified name is enabled.

Regards,
Dinusha.

On Mon, Apr 25, 2016 at 4:58 PM, Dinusha Senanayaka <dinu...@wso2.com>
wrote:

> +Pushpalanka.
>
> On Mon, Apr 25, 2016 at 4:51 PM, Jenananthan Yogendran <
> jenanant...@wso2.com> wrote:
>
>> Hi All,
>>
>> After migrating the AppManager from kernel 4.2.0 to kernel 4.4.5  , fully
>> qualified name is not working as expected.
>>
>> We use file based SP configuration for Store app and Publisher
>> app(attached sso-idp-config files used in both kernel versions). In kernel
>> 4.2.0 , when login to store/publisher app, SAML response has user name with
>> tenant domain  as subject for tenants except carbon super tenant.
>>
>> After migration , SAML response has only user name as subject.Tenant
>> domain is missing for tenants.
>>
>> Also when checked the option "Use tenant domain in local subject
>> identifier" under "Local & Outbound Authentication Configuration" for
>> SPs created through UI, it appends the "carbon.super" domain for super
>> tenant users.
>>
>> Thanks
>> --
>> Jenananthan Yogendran
>> *Software Engineer,*
>> *WSO2 inc., http://wso2.com <http://wso2.com>*
>>
>>
>
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppManager] Fully qualified name issue in SAML response

[Dinusha Senanayaka]

+Pushpalanka.

On Mon, Apr 25, 2016 at 4:51 PM, Jenananthan Yogendran  wrote:

> Hi All,
>
> After migrating the AppManager from kernel 4.2.0 to kernel 4.4.5  , fully
> qualified name is not working as expected.
>
> We use file based SP configuration for Store app and Publisher
> app(attached sso-idp-config files used in both kernel versions). In kernel
> 4.2.0 , when login to store/publisher app, SAML response has user name with
> tenant domain  as subject for tenants except carbon super tenant.
>
> After migration , SAML response has only user name as subject.Tenant
> domain is missing for tenants.
>
> Also when checked the option "Use tenant domain in local subject
> identifier" under "Local & Outbound Authentication Configuration" for SPs
> created through UI, it appends the "carbon.super" domain for super tenant
> users.
>
> Thanks
> --
> Jenananthan Yogendran
> *Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading App Manager to user Carbon Kernel 4.4.5

[Dinusha Senanayaka]

Hi IS Team,

Do you have release date for identity-5.0.9 ? This fix is critical for App
manager release.

Regards,
Dinusha.

On Mon, Apr 4, 2016 at 10:34 AM, Rushmin Fernando  wrote:

> Thanks Pulasthi !
>
> App Manager WIP code can be found in [1] and [2]
>
> Thanks
> Rushmin
>
> [1] -
> https://github.com/wso2/carbon-appmgt/tree/feature/kernel-4.4.5-upgrade
>
> [2]  -
> https://github.com/wso2/product-app-manager/tree/feature/kernel-4.4.5-upgrade
>
> On Fri, Apr 1, 2016 at 4:52 PM, Pulasthi Mahawithana 
> wrote:
>
>> Yes, we no longer use the wso2/carbon-identity repo for development. We
>> use the repos in 'wso2-extensions'. However the group ids, artifact ids and
>> versions follow the same from carbon-identity.
>>
>> On Fri, Apr 1, 2016 at 3:56 PM, Rushmin Fernando 
>> wrote:
>>
>>> Thanks Supun !
>>>
>>> So is [1] obsolete now since the connector code resides in
>>> 'wso2-extensions' account now ?
>>>
>>>
>>> Thanks
>>> Rushmin
>>>
>>> [1] -
>>> https://github.com/wso2/carbon-identity/blob/master/features/provisioning/org.wso2.carbon.identity.provisioning.connector.salesforce.server.feature
>>>
>>> On Fri, Apr 1, 2016 at 3:47 PM, Pulasthi Mahawithana >> > wrote:
>>>
 Hi Rushmin,

 This issue was due to that component being moved from carbon-commons to
 analytic commons. Isura fixed that issue with [1] and [2]. Can you please
 try now?

 [1] https://github.com/wso2-extensions/identity-extension-parent/pull/6
 [2]
 https://github.com/wso2-extensions/identity-outbound-provisioning-salesforce/pull/6

 On Fri, Apr 1, 2016 at 12:21 PM, Rushmin Fernando 
 wrote:

>
> Hi Devs,
>
> We are in the process of upgrading the Carbon Kernel version to 4.4.5
>
> During this upgrade we found out that
> "org.wso2.carbon.identity.provisioning.connector.salesforce.server" 
> feature
> is dependenct on a non-existing feature version of
> "org.wso2.carbon.databridge.commons.server"
>
> I opened a Jira to track this. [1]
>
> Had a chat with Pulasthi and this will be fixed with IS 5.2.0 release
> which will happen in the next week.
>
> Until this is fixed, I'm proceeding with the identity 5.0.9-SNAPSHOT
> having the issue fixed locally.
>
> Thanks
> Rushmin
>
> [1] - https://wso2.org/jira/browse/IDENTITY-4465
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> email : rush...@wso2.com
> mobile : +94772310855
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Pulasthi Mahawithana*
 Software Engineer
 WSO2 Inc., http://wso2.com/
 Mobile: +94-71-5179022
 Blog: http://blog.pulasthi.org

>>>
>>>
>>>
>>> --
>>> *Rushmin Fernando*
>>> *Technical Lead*
>>>
>>> WSO2 Inc.  - Lean . Enterprise . Middleware
>>>
>>> email : rush...@wso2.com
>>> mobile : +94772310855
>>>
>>>
>>>
>>
>>
>> --
>> *Pulasthi Mahawithana*
>> Software Engineer
>> WSO2 Inc., http://wso2.com/
>> Mobile: +94-71-5179022
>> Blog: http://blog.pulasthi.org
>>
>
>
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . Enterprise . Middleware
>
> email : rush...@wso2.com
> mobile : +94772310855
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] APIM Getting SSLPeerUnverifiedException after upgrading to kernel 4.4.4

[Dinusha Senanayaka]

Hi All,

Getting same exception in App Manager also after updating to kernel-4.4.5.
What is the resolution for this, can we continue with
"-Dorg.opensaml.httpclient.https.disableHostnameVerification=true \" system
property in startup script as Harsha suggested ?

Regards,
Dinusha.

On Tue, Apr 5, 2016 at 7:18 PM, Harsha Kumara  wrote:

> Hi IS Team,
>
> It seems that the issue got resolved with the system property. We will
> needed to add it to our startup scripts. Any concerns on doing that?
>
> Thanks,
> Harsha
>
> On Tue, Apr 5, 2016 at 6:26 PM, Harsha Kumara  wrote:
>
>> Boolean.getBoolean perform system property lookup. I'll try that solution
>> and update.
>>
>> On Tue, Apr 5, 2016 at 6:20 PM, Harsha Kumara  wrote:
>>
>>> I have done some analysis on this. In API Manager initial functionality
>>> works fine. When the access token is generated SAML2BearerGrantHandler
>>> doing DefaultBootstrap.bootstrap(); in opensaml library. With the new
>>> version of the opensaml library they have
>>> perform initializeHttpClient();[1] during the bootstrap. So the underline
>>> commons http client library socket factory has changed
>>> from SSLProtocolSocketFactory to TLSProtocolSocketFactory.
>>> In TLSProtocolSocketFactory it's perform host name verification which cause
>>> this exception. When go through their code, they have tried to disable this
>>> from System property. But implementation is doing Boolean.getBoolean
>>> instead of looking from System.getPropety[2] which seems bug. If this has
>>> worked, we could have set a system property.
>>>
>>> [1]
>>> /**
>>>  *  Initializes the Apache Commons HttpClient library.
>>>  */
>>> protected static void initializeHttpClient() {
>>> if
>>> (!Boolean.getBoolean(SYSPROP_HTTPCLIENT_HTTPS_DISABLE_HOSTNAME_VERIFICATION))
>>> {
>>> ProtocolSocketFactory socketFactory =
>>> new TLSProtocolSocketFactory(null, null, new
>>> StrictHostnameVerifier());
>>> Protocol.registerProtocol("https", new Protocol("https",
>>> socketFactory, 443));
>>> }
>>> }
>>>
>>> [2]
>>> /** System property used to disable global default HTTPS hostname
>>> verification in Apache Commons HttpClient. */
>>> public static final String
>>> SYSPROP_HTTPCLIENT_HTTPS_DISABLE_HOSTNAME_VERIFICATION =
>>> "org.opensaml.httpclient.https.disableHostnameVerification";
>>>
>>> Thanks,
>>> Harsha
>>>
>>>
>>> On Tue, Apr 5, 2016 at 5:48 PM, Nuwan Dias  wrote:
>>>
 IS Team,

 It looks like the TLSProtocolSocketFactory isn't honouring the HostName
 verification parameter. It always tries to do the hostname verification.
 Looks like a buggy behaviour to me.

 This causes problems for API Manager and any other product which has a
 distributed deployment (App Manager, DAS, etc) because it prevents http
 clients within our code from accessing Admin Services of remote nodes. The
 http clients fail since the server cert is by default for localhost and
 whenever we try to access through IPs it fails. The only way to overcome
 this is to create the proper certs and deploy on the server. Which is a
 huge hassle for simple test scenarios.

 The TLSProtocolSocketFactory is being set when the SAMLBearerGrant is
 being initialized. Until then things work fine. We either have to stop it
 being set or use a version of opensaml which supports skipping the host
 name verification (like our transports allow). Otherwise this is going to
 be a huge blocker for our releases.

 Thanks,
 NuwanD.

 On Thu, Mar 17, 2016 at 7:09 PM, Sam Sivayogam  wrote:

> HI All,
>
> Had a offline chat with Pulasthi and got to know that in IS 5.0.8
> there was opensaml upgrade from 2.4.1 to 2.6.4. After going through [1] 
> got
> to know that there is a hostname verification introduced in opensaml 2.6.4
> which is not there in opensaml 2.4.1 and this is why we are getting the
> above issue after moving to carbon identity 5.0.8.
>
> We are using *CommonsHTTPTransportSender * to call key
> manager internally and from what I understood if we set the 
> *HostnameVerifier
> *parameter to *AllowAll *we should be able to get rid of this issue,
> But still we are getting this issue. Does anyone know why HostnameVerifier
> prameter is not working as expected with CommonsHTTPTransportSender ?
>
> [1]
> http://grepcode.com/file_/repo1.maven.org/maven2/org.apache.servicemix.bundles/org.apache.servicemix.bundles.opensaml/2.4.1_2/org/opensaml/ws/soap/client/http/TLSProtocolSocketFactory.java/?v=diff=2.6.4_1
>
> Thanks,
>
> On Thu, Mar 17, 2016 at 11:12 AM, Sam Sivayogam  wrote:
>
>> Hi All,
>>
>> I'm trying to to upgrade APIM's Crabon kernel to 4.4.4. during the
>> kernel upgrade i also upgraded the following
>> carbon 

Re: [Dev] [APPM][UX] Responsive left menu with submenus

[Dinusha Senanayaka]

Thanks Jerad. Monday should be fine.

Regards,
Dinusha.

On Fri, Apr 8, 2016 at 3:43 PM, Jerad Rutnam <je...@wso2.com> wrote:

> Hi Dinusha,
>
> We will finalize the markup by Monday and let you know. We cant get this
> out by today since the team is busy with some other allocated work.
>
> Cheers!
> Jerad
>
>
> On Thu, Apr 7, 2016 at 10:09 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi Jerad,
>>
>> On Thu, Apr 7, 2016 at 12:39 PM, Jerad Rutnam <je...@wso2.com> wrote:
>>
>>> Hi Jenananthan,
>>>
>>> Yes, Its ok to use it. But we have not finalized the markup etc ... yet.
>>> But we can update you about the changes once it's finalized.
>>>
>>
>> This is something critical for AppM new UI. Please let us know  once this
>> is updated.
>>
>> Regards,
>> Dinusha.
>>
>>>
>>> Regards,
>>> Jerad
>>>
>>>
>>> On Wed, Apr 6, 2016 at 10:56 AM, Jenananthan Yogendran <
>>> jenanant...@wso2.com> wrote:
>>>
>>>> Hi UX Team,
>>>>
>>>> In APP Manager we need to have sub menu(my subscription) under left
>>>> column menus(asset types).
>>>> With current markup [1] this is not supported.In the markup of API
>>>> Manager[2]  sub menu support is available. Is this markup  completed ? Can
>>>> we use the same markup for left menus ?
>>>>
>>>> 1. https://github.com/wso2-dev-ux/product-appm
>>>> 2. https://github.com/wso2-dev-ux/product-apim
>>>>
>>>> Thanks
>>>> --
>>>> Jenananthan Yogendran
>>>> *Software Engineer,*
>>>> *WSO2 inc., http://wso2.com <http://wso2.com>*
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Jerad Rutnam*
>>> *Software Engineer*
>>>
>>> WSO2 Inc.
>>> lean | enterprise | middleware
>>> M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com
>>>
>>
>>
>>
>> --
>> Dinusha Dilrukshi
>> Associate Technical Lead
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
> *Jerad Rutnam*
> *Software Engineer*
>
> WSO2 Inc.
> lean | enterprise | middleware
> M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APPM][UX] Responsive left menu with submenus

[Dinusha Senanayaka]

Hi Jerad,

On Thu, Apr 7, 2016 at 12:39 PM, Jerad Rutnam  wrote:

> Hi Jenananthan,
>
> Yes, Its ok to use it. But we have not finalized the markup etc ... yet.
> But we can update you about the changes once it's finalized.
>

This is something critical for AppM new UI. Please let us know  once this
is updated.

Regards,
Dinusha.

>
> Regards,
> Jerad
>
>
> On Wed, Apr 6, 2016 at 10:56 AM, Jenananthan Yogendran <
> jenanant...@wso2.com> wrote:
>
>> Hi UX Team,
>>
>> In APP Manager we need to have sub menu(my subscription) under left
>> column menus(asset types).
>> With current markup [1] this is not supported.In the markup of API
>> Manager[2]  sub menu support is available. Is this markup  completed ? Can
>> we use the same markup for left menus ?
>>
>> 1. https://github.com/wso2-dev-ux/product-appm
>> 2. https://github.com/wso2-dev-ux/product-apim
>>
>> Thanks
>> --
>> Jenananthan Yogendran
>> *Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Jerad Rutnam*
> *Software Engineer*
>
> WSO2 Inc.
> lean | enterprise | middleware
> M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APPM] Mobile application binary file upload REST API

[Dinusha Senanayaka]

On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika  wrote:

> Hi all,
>
> We have a concern regarding the design of mobile application binary/image
> upload API. As per the discussions we had on the new design of the API
> model, we decided to use a separate API to upload mobile binary files(.apk,
> .ipa) including the images. Thus, in order to create a mobile app,  we have
> to initially upload relevant application binary and image files of app
> thumbnail, banner and screenshots and later the application should be
> created with the references to uploaded binaries.
> We have already implemented the REST API for application binary upload.
> But we have few concerns regarding the image file upload. We have two
> options in implementing image upload scenario.
>
>
>1. Reusing the binary upload API for image upload also. But in this
>case, we need to change the API design in order to distinguish the
>uploading file type (Whether is it is an app binary or an image for
>screenshots, thumbnails etc) since we have separate flows of processing the
>files.
>2. Implementing a dedicated API for image upload only. In this case,
>we can implement this API in order to be reused in webapp image upload
>also.
>
>  I'm +1 for option 1. Keep the API as
http://localhost:9763/api/appm/publisher/v1.0/apps/binaries and handle all
binary uploads(apks, images, documents) for web/mobile from this API,
instead introducing API per each binary type.

Regards,
Dinusha.

>
> As per the offline discussion I had with RuwanA, another concern was
> raised regarding the URL for binary upload API. The current URL is '
> http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
> binaries'. But this
> particular URL is mobile application specific. In that case, we cannot
> reuse this API in future, for any other application binary upload, other
> that mobile binary upload. Our suggestion here is to rename the API as
> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
> binaries and making
> the API more generic.
>
> Your suggestions are highly appreciated.
>
> [1] -
> https://docs.google.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit
>
>
> Thanks,
> Thilini
>
> --
> Thilini Shanika
> Software Engineer
> WSO2, Inc.; http://wso2.com
> 20, Palmgrove Avenue, Colombo 3
>
> E-mail: tgtshan...@gmail.com
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Sajith Ariyarathna

[Dinusha Senanayaka]

Hi All,

It is my pleasure to welcome Sajith Ariyarathna as a WSO2 Committer.  @
SajithAR, congratulations and keep up the good work.

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shall we use latest APPM in EMM?

[Dinusha Senanayaka]

On Mon, Mar 21, 2016 at 4:42 PM, Lakshman Udayakantha <lakshm...@wso2.com>
wrote:

> Hi Dinusha,
>
> Updated the pull with your suggestions.
>
Thanks. Merged.

>
> Thanks
>
> On Mon, Mar 21, 2016 at 2:57 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi Lakshman,
>>
>> Thanks for fixing this. Added few comments to PR. Please update.
>>
>> Regards,
>> Dinusha.
>>
>> On Mon, Mar 21, 2016 at 2:40 PM, Lakshman Udayakantha <lakshm...@wso2.com
>> > wrote:
>>
>>> Hi Dinusha,
>>>
>>> I have moved subscriber persisting code [1] to subscription creation
>>> moment from login moment. Could you review and merge it.
>>>
>>> [1] https://github.com/wso2/carbon-appmgt/pull/245/files
>>>
>>> Thanks
>>>
>>>
>>> On Fri, Mar 18, 2016 at 9:30 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> This is something we got from the APIM code and we need to refactor it.
>>>> In their case, users login to store can create oauth app and subscribe to
>>>> APIs. App creation also should be done by a subscriber and that's why user
>>>> is added to SUBSCRIBER table at the login. Then SUBSCRIPTION table is
>>>> populate when the actual subscription happen to API.
>>>>
>>>> Anyway, AppM do not have this app creation concept in the store. Hence
>>>> we could move this SUBSCRIBER, SUBSCRIPTION both table inserts to where
>>>> actual subscription happens.
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>> On Fri, Mar 18, 2016 at 8:33 PM, Lahiru Cooray <lahi...@wso2.com>
>>>> wrote:
>>>>
>>>>> +1 for Ruwan's suggestion.
>>>>> Further in current model, Subscriptions(APM_SUBSCRIPTION) are mapped
>>>>> to a Application(APM_APPLICATION) and Application is bound to a subscriber
>>>>> (APM_SUBSCRIBER)
>>>>>
>>>>> Subscriber should ideally contain the users who are subscribed to an
>>>>> App.
>>>>> But currently APM_SUBSCRIBER table getting updated when an user log in
>>>>> to the store (which is not ideal)
>>>>> This operation should be moved to just before user get subscribed to
>>>>> an App.
>>>>>
>>>>>
>>>>> On Fri, Mar 18, 2016 at 5:12 PM, Ruwan Abeykoon <ruw...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>> I think APM_SUBSCRIBER is used to check subscription on WebApps or
>>>>>> Sites.
>>>>>> I think adding subscriber to this table can be moved to place where
>>>>>> the subscription is added. We might have to revisit and change the SQL
>>>>>> queries which is used to check the subscriptions.
>>>>>>
>>>>>> Cheers,
>>>>>> Ruwan
>>>>>>
>>>>>> On Fri, Mar 18, 2016 at 4:49 PM, Lakshman Udayakantha <
>>>>>> lakshm...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Dinusha,
>>>>>>>
>>>>>>> When user is going to login to store, user will add if does not
>>>>>>> exist, to a table called APM_SUBSCRIBER . This code snippet has removed 
>>>>>>> in
>>>>>>> EMM store (in APPM 1.1.1 version). That's why earlier this problem is 
>>>>>>> not
>>>>>>> raised. Anyway what is the purpose of adding user to the APM_SUBSCRIBER
>>>>>>> table? Note that this table is the only dependant table from APPM to 
>>>>>>> EMM.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Fri, Mar 18, 2016 at 3:01 PM, Prabath Abeysekera <
>>>>>>> praba...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi Dinusha,
>>>>>>>>
>>>>>>>> On Fri, Mar 18, 2016 at 2:54 PM, Dinusha Senanayaka <
>>>>>>>> dinu...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Prabath,
>>>>>>>>>
>>>>>>>>> On Fri, Mar 18, 2016 at 2:34 PM, Prabath Abeysekera <
>>>>>>>>> praba...@wso2.com> wrote:
>>>>>>>>>
>

Re: [Dev] Shall we use latest APPM in EMM?

[Dinusha Senanayaka]

Hi Lakshman,

Thanks for fixing this. Added few comments to PR. Please update.

Regards,
Dinusha.

On Mon, Mar 21, 2016 at 2:40 PM, Lakshman Udayakantha <lakshm...@wso2.com>
wrote:

> Hi Dinusha,
>
> I have moved subscriber persisting code [1] to subscription creation
> moment from login moment. Could you review and merge it.
>
> [1] https://github.com/wso2/carbon-appmgt/pull/245/files
>
> Thanks
>
>
> On Fri, Mar 18, 2016 at 9:30 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi All,
>>
>> This is something we got from the APIM code and we need to refactor it.
>> In their case, users login to store can create oauth app and subscribe to
>> APIs. App creation also should be done by a subscriber and that's why user
>> is added to SUBSCRIBER table at the login. Then SUBSCRIPTION table is
>> populate when the actual subscription happen to API.
>>
>> Anyway, AppM do not have this app creation concept in the store. Hence we
>> could move this SUBSCRIBER, SUBSCRIPTION both table inserts to where actual
>> subscription happens.
>>
>> Regards,
>> Dinusha.
>>
>> On Fri, Mar 18, 2016 at 8:33 PM, Lahiru Cooray <lahi...@wso2.com> wrote:
>>
>>> +1 for Ruwan's suggestion.
>>> Further in current model, Subscriptions(APM_SUBSCRIPTION) are mapped to
>>> a Application(APM_APPLICATION) and Application is bound to a subscriber
>>> (APM_SUBSCRIBER)
>>>
>>> Subscriber should ideally contain the users who are subscribed to an
>>> App.
>>> But currently APM_SUBSCRIBER table getting updated when an user log in
>>> to the store (which is not ideal)
>>> This operation should be moved to just before user get subscribed to an
>>> App.
>>>
>>>
>>> On Fri, Mar 18, 2016 at 5:12 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
>>>
>>>> Hi All,
>>>> I think APM_SUBSCRIBER is used to check subscription on WebApps or
>>>> Sites.
>>>> I think adding subscriber to this table can be moved to place where the
>>>> subscription is added. We might have to revisit and change the SQL queries
>>>> which is used to check the subscriptions.
>>>>
>>>> Cheers,
>>>> Ruwan
>>>>
>>>> On Fri, Mar 18, 2016 at 4:49 PM, Lakshman Udayakantha <
>>>> lakshm...@wso2.com> wrote:
>>>>
>>>>> Hi Dinusha,
>>>>>
>>>>> When user is going to login to store, user will add if does not exist,
>>>>> to a table called APM_SUBSCRIBER . This code snippet has removed in EMM
>>>>> store (in APPM 1.1.1 version). That's why earlier this problem is not
>>>>> raised. Anyway what is the purpose of adding user to the APM_SUBSCRIBER
>>>>> table? Note that this table is the only dependant table from APPM to EMM.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Mar 18, 2016 at 3:01 PM, Prabath Abeysekera <praba...@wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Hi Dinusha,
>>>>>>
>>>>>> On Fri, Mar 18, 2016 at 2:54 PM, Dinusha Senanayaka <dinu...@wso2.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi Prabath,
>>>>>>>
>>>>>>> On Fri, Mar 18, 2016 at 2:34 PM, Prabath Abeysekera <
>>>>>>> praba...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi Dinusha,
>>>>>>>>
>>>>>>>> On Fri, Mar 18, 2016 at 2:19 PM, Dinusha Senanayaka <
>>>>>>>> dinu...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Lakshman,
>>>>>>>>>
>>>>>>>>> On Fri, Mar 18, 2016 at 2:08 PM, Lakshman Udayakantha <
>>>>>>>>> lakshm...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I am looking into this. After changing the APP Manager feature
>>>>>>>>>> versions in EMM, publisher works as expected. It can create and 
>>>>>>>>>> publish
>>>>>>>>>> mobile apps without any issue. But I can't even login to store. 
>>>>>>>>>> According
>>>>>>>>>> to backend error, It seems like EMM wants APP Manager related db 
>>

Re: [Dev] Shall we use latest APPM in EMM?

[Dinusha Senanayaka]

Hi Prabath,

On Fri, Mar 18, 2016 at 2:34 PM, Prabath Abeysekera <praba...@wso2.com>
wrote:

> Hi Dinusha,
>
> On Fri, Mar 18, 2016 at 2:19 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi Lakshman,
>>
>> On Fri, Mar 18, 2016 at 2:08 PM, Lakshman Udayakantha <lakshm...@wso2.com
>> > wrote:
>>
>>> Hi,
>>>
>>> I am looking into this. After changing the APP Manager feature versions
>>> in EMM, publisher works as expected. It can create and publish mobile apps
>>> without any issue. But I can't even login to store. According to backend
>>> error, It seems like EMM wants APP Manager related db tables too. I have
>>> added APP Manager tables to AM datasource and after that I can login to
>>> store without any issue and published apps also shown in there. Anyway is
>>> that ok to add APP Manager tables to AM datasource?
>>>
>>
>> I think it should be fine to include AppM datasource in EMM. Currently we
>> don't need it for mobile apps. But there could be scenarios in future we
>> need AppM db for mobile apps as well.
>>
>
> If "mobile application provisioning plugin" doesn't require persisting
> information, why exactly do we need to add tables, etc just to get the
> store to work?
>

This we need to check. AFAIK, EMM is installing only appm.store,
appm.publisher, appm.mobile features which is not depend on appm.core
feature which provides the db. May be we have installed additional feature ?

Regards,
Dinusha.

>
> Cheers,
> Prabath
>
>
>>
>> Regards,
>> Dinusha.
>>
>>>
>>> Thanks
>>>
>>> On Thu, Mar 17, 2016 at 2:43 PM, Milan Perera <mi...@wso2.com> wrote:
>>>
>>>> Hi Dinusha,
>>>>
>>>> I totally agree to what you said. Its better if we can do this as soon
>>>> as possible.
>>>>
>>>> Regards,
>>>>
>>>> On Thu, Mar 17, 2016 at 2:31 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Milan,
>>>>>
>>>>> IMO, if we have version conflicts we should try to fix it. What we
>>>>> have done so far is not correct. We have created a separate branch of AppM
>>>>> for EMM by manually removing the web app related UIs. We have done it for
>>>>> the time being, but this won't scale when it comes to support/maintenance
>>>>> and feature development. With the feature that Lakshman has done, we could
>>>>> use the same code base for both AppM and EMM.
>>>>>
>>>>> Regards,
>>>>> Dinusha.
>>>>>
>>>>> On Thu, Mar 17, 2016 at 2:11 PM, Milan Perera <mi...@wso2.com> wrote:
>>>>>
>>>>>> Hi Lakshman,
>>>>>>
>>>>>> As I remember, we have tried it before and in the previous attempt of
>>>>>> migrating to the latest APPM feature was failed due to some conflicts in
>>>>>> dependencies that were unable to resolve at that time. If im not 
>>>>>> mistaken,
>>>>>> it had conflicts with the IS version which we use in the EMM 200.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> On Thu, Mar 17, 2016 at 7:25 AM, Lakshman Udayakantha <
>>>>>> lakshm...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Chathura,
>>>>>>>
>>>>>>> Yes. It is not because of asset turning off/on feature. I meant that
>>>>>>> UI has changed a lot in latest APP Manager recently and APPM team didn't
>>>>>>> get much time to resolve all the bugs reported. As per the offline
>>>>>>> discussion with LahiruC lot of mobile features has broken with new UI 
>>>>>>> and
>>>>>>> they are fixing it now. So IMO replacing new features may introduce new
>>>>>>> bugs to existing APP UI in EMM. Anyway if new UI will go to a high 
>>>>>>> stable
>>>>>>> position and APPM release is not going to conflict with EMM release this
>>>>>>> will be possible. right? WDYT?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Thu, Mar 17, 2016 at 12:21 AM, Chathura Dilan <chathu...@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>&g

Re: [Dev] Shall we use latest APPM in EMM?

[Dinusha Senanayaka]

Hi Milan,

IMO, if we have version conflicts we should try to fix it. What we have
done so far is not correct. We have created a separate branch of AppM for
EMM by manually removing the web app related UIs. We have done it for the
time being, but this won't scale when it comes to support/maintenance and
feature development. With the feature that Lakshman has done, we could use
the same code base for both AppM and EMM.

Regards,
Dinusha.

On Thu, Mar 17, 2016 at 2:11 PM, Milan Perera  wrote:

> Hi Lakshman,
>
> As I remember, we have tried it before and in the previous attempt of
> migrating to the latest APPM feature was failed due to some conflicts in
> dependencies that were unable to resolve at that time. If im not mistaken,
> it had conflicts with the IS version which we use in the EMM 200.
>
> Regards,
>
> On Thu, Mar 17, 2016 at 7:25 AM, Lakshman Udayakantha 
> wrote:
>
>> Hi Chathura,
>>
>> Yes. It is not because of asset turning off/on feature. I meant that UI
>> has changed a lot in latest APP Manager recently and APPM team didn't get
>> much time to resolve all the bugs reported. As per the offline discussion
>> with LahiruC lot of mobile features has broken with new UI and they are
>> fixing it now. So IMO replacing new features may introduce new bugs to
>> existing APP UI in EMM. Anyway if new UI will go to a high stable position
>> and APPM release is not going to conflict with EMM release this will be
>> possible. right? WDYT?
>>
>> Thanks
>>
>> On Thu, Mar 17, 2016 at 12:21 AM, Chathura Dilan 
>> wrote:
>>
>>> Hi Lakshman,
>>>
>>> ​​This feature will not introduce any bugs in store or publisher, since
>>> it only on/off assets types.  But we have to test all scenarios of EMM and
>>> AppM integration.
>>>
>>> On Wed, Mar 16, 2016 at 7:03 AM, Lakshman Udayakantha <
>>> lakshm...@wso2.com> wrote:
>>>
 [Adding Dev]

 On Wed, Mar 16, 2016 at 5:40 PM, Prabath Abeysekera 
 wrote:

> Hi Lakshman,
>
> Of course we should. Would you be able to move this discussion to dev@
> so we can discuss about any possible concerns, etc there.
>
> Cheers,
> Prabath
>
> On Wed, Mar 16, 2016 at 2:53 PM, Lakshman Udayakantha <
> lakshm...@wso2.com> wrote:
>
>> Hi EMM Team,
>>
>> It can be turned off asset types which are not in use in latest APP
>> Manager. There is a configuration called EnabledAssetTypeList in which we
>> can provide only mobileapp to enable mobile apps only in publisher and
>> store. So shall we do the $subject, for the sake of getting future
>> improvements and bug fixes in APPM.
>>
>> @APPM Team: Are there any bad consequences of doing $subject like
>> introducing new bugs to existing store and publisher in EMM(APPM feature
>> version 1.1.1)?
>>
>> Thanks
>> --
>> Lakshman Udayakantha
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>> Mobile: *0714388124 <0714388124>*
>>
>>
>
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>



 --
 Lakshman Udayakantha
 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware
 Mobile: *0714388124 <0714388124>*


>>>
>>>
>>> --
>>> Regards,
>>>
>>> Chatura Dilan Perera
>>> *Senior Software Engineer** - WSO2 Inc.*
>>> www.dilan.me
>>>
>>
>>
>>
>> --
>> Lakshman Udayakantha
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>> Mobile: *0714388124 <0714388124>*
>>
>>
>
>
> --
> *Milan Perera *| 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
> 
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shall we use latest APPM in EMM?

[Dinusha Senanayaka]

Hi All,

This is something we got from the APIM code and we need to refactor it. In
their case, users login to store can create oauth app and subscribe to
APIs. App creation also should be done by a subscriber and that's why user
is added to SUBSCRIBER table at the login. Then SUBSCRIPTION table is
populate when the actual subscription happen to API.

Anyway, AppM do not have this app creation concept in the store. Hence we
could move this SUBSCRIBER, SUBSCRIPTION both table inserts to where actual
subscription happens.

Regards,
Dinusha.

On Fri, Mar 18, 2016 at 8:33 PM, Lahiru Cooray <lahi...@wso2.com> wrote:

> +1 for Ruwan's suggestion.
> Further in current model, Subscriptions(APM_SUBSCRIPTION) are mapped to a
> Application(APM_APPLICATION) and Application is bound to a subscriber
> (APM_SUBSCRIBER)
>
> Subscriber should ideally contain the users who are subscribed to an App.
> But currently APM_SUBSCRIBER table getting updated when an user log in to
> the store (which is not ideal)
> This operation should be moved to just before user get subscribed to an
> App.
>
>
> On Fri, Mar 18, 2016 at 5:12 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
>
>> Hi All,
>> I think APM_SUBSCRIBER is used to check subscription on WebApps or
>> Sites.
>> I think adding subscriber to this table can be moved to place where the
>> subscription is added. We might have to revisit and change the SQL queries
>> which is used to check the subscriptions.
>>
>> Cheers,
>> Ruwan
>>
>> On Fri, Mar 18, 2016 at 4:49 PM, Lakshman Udayakantha <lakshm...@wso2.com
>> > wrote:
>>
>>> Hi Dinusha,
>>>
>>> When user is going to login to store, user will add if does not exist,
>>> to a table called APM_SUBSCRIBER . This code snippet has removed in EMM
>>> store (in APPM 1.1.1 version). That's why earlier this problem is not
>>> raised. Anyway what is the purpose of adding user to the APM_SUBSCRIBER
>>> table? Note that this table is the only dependant table from APPM to EMM.
>>>
>>> Thanks
>>>
>>> On Fri, Mar 18, 2016 at 3:01 PM, Prabath Abeysekera <praba...@wso2.com>
>>> wrote:
>>>
>>>> Hi Dinusha,
>>>>
>>>> On Fri, Mar 18, 2016 at 2:54 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Prabath,
>>>>>
>>>>> On Fri, Mar 18, 2016 at 2:34 PM, Prabath Abeysekera <praba...@wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Hi Dinusha,
>>>>>>
>>>>>> On Fri, Mar 18, 2016 at 2:19 PM, Dinusha Senanayaka <dinu...@wso2.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi Lakshman,
>>>>>>>
>>>>>>> On Fri, Mar 18, 2016 at 2:08 PM, Lakshman Udayakantha <
>>>>>>> lakshm...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I am looking into this. After changing the APP Manager feature
>>>>>>>> versions in EMM, publisher works as expected. It can create and publish
>>>>>>>> mobile apps without any issue. But I can't even login to store. 
>>>>>>>> According
>>>>>>>> to backend error, It seems like EMM wants APP Manager related db tables
>>>>>>>> too. I have added APP Manager tables to AM datasource and after that I 
>>>>>>>> can
>>>>>>>> login to store without any issue and published apps also shown in 
>>>>>>>> there.
>>>>>>>> Anyway is that ok to add APP Manager tables to AM datasource?
>>>>>>>>
>>>>>>>
>>>>>>> I think it should be fine to include AppM datasource in EMM.
>>>>>>> Currently we don't need it for mobile apps. But there could be 
>>>>>>> scenarios in
>>>>>>> future we need AppM db for mobile apps as well.
>>>>>>>
>>>>>>
>>>>>> If "mobile application provisioning plugin" doesn't require
>>>>>> persisting information, why exactly do we need to add tables, etc just to
>>>>>> get the store to work?
>>>>>>
>>>>>
>>>>> This we need to check. AFAIK, EMM is installing only appm.store,
>>>>> appm.publisher, appm.mobile features which is not depend on appm.core
>>>>> fea

Re: [Dev] Shall we use latest APPM in EMM?

[Dinusha Senanayaka]

Hi Lakshman,

On Fri, Mar 18, 2016 at 2:08 PM, Lakshman Udayakantha <lakshm...@wso2.com>
wrote:

> Hi,
>
> I am looking into this. After changing the APP Manager feature versions in
> EMM, publisher works as expected. It can create and publish mobile apps
> without any issue. But I can't even login to store. According to backend
> error, It seems like EMM wants APP Manager related db tables too. I have
> added APP Manager tables to AM datasource and after that I can login to
> store without any issue and published apps also shown in there. Anyway is
> that ok to add APP Manager tables to AM datasource?
>

I think it should be fine to include AppM datasource in EMM. Currently we
don't need it for mobile apps. But there could be scenarios in future we
need AppM db for mobile apps as well.

Regards,
Dinusha.

>
> Thanks
>
> On Thu, Mar 17, 2016 at 2:43 PM, Milan Perera <mi...@wso2.com> wrote:
>
>> Hi Dinusha,
>>
>> I totally agree to what you said. Its better if we can do this as soon as
>> possible.
>>
>> Regards,
>>
>> On Thu, Mar 17, 2016 at 2:31 PM, Dinusha Senanayaka <dinu...@wso2.com>
>> wrote:
>>
>>> Hi Milan,
>>>
>>> IMO, if we have version conflicts we should try to fix it. What we have
>>> done so far is not correct. We have created a separate branch of AppM for
>>> EMM by manually removing the web app related UIs. We have done it for the
>>> time being, but this won't scale when it comes to support/maintenance and
>>> feature development. With the feature that Lakshman has done, we could use
>>> the same code base for both AppM and EMM.
>>>
>>> Regards,
>>> Dinusha.
>>>
>>> On Thu, Mar 17, 2016 at 2:11 PM, Milan Perera <mi...@wso2.com> wrote:
>>>
>>>> Hi Lakshman,
>>>>
>>>> As I remember, we have tried it before and in the previous attempt of
>>>> migrating to the latest APPM feature was failed due to some conflicts in
>>>> dependencies that were unable to resolve at that time. If im not mistaken,
>>>> it had conflicts with the IS version which we use in the EMM 200.
>>>>
>>>> Regards,
>>>>
>>>> On Thu, Mar 17, 2016 at 7:25 AM, Lakshman Udayakantha <
>>>> lakshm...@wso2.com> wrote:
>>>>
>>>>> Hi Chathura,
>>>>>
>>>>> Yes. It is not because of asset turning off/on feature. I meant that
>>>>> UI has changed a lot in latest APP Manager recently and APPM team didn't
>>>>> get much time to resolve all the bugs reported. As per the offline
>>>>> discussion with LahiruC lot of mobile features has broken with new UI and
>>>>> they are fixing it now. So IMO replacing new features may introduce new
>>>>> bugs to existing APP UI in EMM. Anyway if new UI will go to a high stable
>>>>> position and APPM release is not going to conflict with EMM release this
>>>>> will be possible. right? WDYT?
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Thu, Mar 17, 2016 at 12:21 AM, Chathura Dilan <chathu...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Lakshman,
>>>>>>
>>>>>> ​​This feature will not introduce any bugs in store or publisher,
>>>>>> since it only on/off assets types.  But we have to test all scenarios of
>>>>>> EMM and AppM integration.
>>>>>>
>>>>>> On Wed, Mar 16, 2016 at 7:03 AM, Lakshman Udayakantha <
>>>>>> lakshm...@wso2.com> wrote:
>>>>>>
>>>>>>> [Adding Dev]
>>>>>>>
>>>>>>> On Wed, Mar 16, 2016 at 5:40 PM, Prabath Abeysekera <
>>>>>>> praba...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi Lakshman,
>>>>>>>>
>>>>>>>> Of course we should. Would you be able to move this discussion to
>>>>>>>> dev@ so we can discuss about any possible concerns, etc there.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Prabath
>>>>>>>>
>>>>>>>> On Wed, Mar 16, 2016 at 2:53 PM, Lakshman Udayakantha <
>>>>>>>> lakshm...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi EMM Team,
>>>>>>>>>
>>>>>>>>> It can be tu

Re: [Dev] [Architecture] [DEV] WSO2 App Manager 1.2.0 Milestone 2 Released

[Dinusha Senanayaka]

Hi Susinda,

On Mon, Mar 14, 2016 at 10:22 AM, Susinda Perera  wrote:

> Hi Lahiru
>
> Is there tooling requirement for AppManager? If so shall we have a chat
> and build a tooling plan.
>

We haven't plan tooling for AppManager immediate release (1.2.0). But, yes
we could have a chat and include it for next release.

Regards,
Dinusha.


>
> Thanks
> Susinda
>
>
> On Thu, Mar 10, 2016 at 1:18 AM, Lahiru Cooray  wrote:
>
>> Hi All,
>>
>> WSO2 App Manager team pleased to announce the WSO2 APP Manager 1.2.0 -
>> Milestone 2 release. It contains following new features, improvements and
>> bug fixes.
>>
>> You can download this distribution from below link.
>> *http://builder1.us1.wso2.org/~appm/release-1.2.0/M2/wso2appm-1.2.0-M2.zip
>> *
>>
>>
>> *New Features *
>> 1. New asset type - sites.
>> 2. Configurable subscription option for Web App and Sites asset types.
>> 3. Multiple version support for Web App and Sites  asset types.
>> 4. Java APIs for all key App Manager functionalities that need to be
>> integrated with device management functionalities.
>> 5. Role based visibility control for mobile apps.
>>
>>
>>
>> *Improvements*1. Navigation improvements in App Store.
>> 2. Add missing functionalities to Store/Publisher REST API and
>> improvements.
>> 3. Responsive store UI by Boostrap3 upgrade.
>> 4. New theme for store UI
>>
>> *Bug Fixes*
>> WSO2 App Manager 1.2.0-M2 resolved issues
>> 
>>
>>
>> Regards,
>> App Manager Team.
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 Engineering Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to engineering-group+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [App Manager] - Service providers are not getting listed in carbon mgt console

[Dinusha Senanayaka]

Any idea on this ?

Regards,
Dinusha.

On Mon, Feb 22, 2016 at 2:40 PM, Dinusha Senanayaka <dinu...@wso2.com>
wrote:

> Hi IS Team,
>
> We are moving AppManager from identity-4.5.3 dependencies to 5.0.7.
>
> Service providers are registered by calling to
> createApplication(serviceProvider) method in
>  "IdentityApplicationManagementService"  service. After migration, SP
> artifact get created in registry but not in identity DB.  SSO works, but SP
> is not listed in UI. We need to get it listed in UI as well. Do we have
> different function in 5.0.7 ?
>
>
> Regards,
> Dinusha.
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Login and Logout error in Store

[Dinusha Senanayaka]

Hi Ayesha,

Issue came with logout operation, but host name was set to localhost.
Anyway, I updated jaggery.js version to latest (0.12.2) and issue seems to
be sorted with that. Thanks for checking.

Regards,
Dinusha.

On Mon, Feb 22, 2016 at 4:49 PM, Ayesha Dissanayaka <aye...@wso2.com> wrote:

> Hi Dinusha,
>
> jaggery 0.12.0 should be fine, since it has pretty much the same jaggery
> code content as of jaggery-0.11.2 which is used in greg-5.1.0.  However, we
> couldn't completely resolve the issues in some edge cases at
> login/logout[2] such as, accessing store/publisher with IP instead of
> domain name (ex:localhost) because of some constrains in identity
> components.
> Are you also getting above error in such scenario?
>
> [1]
> https://github.com/wso2/jaggery/compare/release-0.11.2...release-0.12.1?expand=1
> [2] G-Reg 5.1.0 code freeze keep delaying ? WAS { Re: Login and Logout
> error in Store}
>
> Thanks!
> -Ayesha
>
>
> On Mon, Feb 22, 2016 at 3:07 PM, Dinusha Senanayaka <dinu...@wso2.com>
> wrote:
>
>> Hi Ayesha,
>>
>> Is there a released version available now with the above fix ? Getting
>> same issue in AppM with jaggery.js.feature-0.12.0.
>>
>> Regards,
>> Dinusha.
>>
>> On Wed, Oct 28, 2015 at 11:21 AM, Ayesha Dissanayaka <aye...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> On Tue, Oct 27, 2015 at 5:53 PM, Manuranga Perera <m...@wso2.com> wrote:
>>>
>>>>
>>>> add logic to check if instance of session object and set it to session
>>>> obj if true else set to request obj
>>>>
>>>
>>> Chanaka and myself tested this fix and it works as expected.
>>> Greg team will continue further testing the login/logout scenarios
>>> before releasing jaggery and jaggery-extension.
>>>
>>> Thanks!
>>> -Ayesha
>>>
>>>
>>> --
>>> *Ayesha Dissanayaka*
>>> Software Engineer,
>>> WSO2, Inc : http://wso2.com
>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com=D=1=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
>>> 20, Palmgrove Avenue, Colombo 3
>>> E-Mail: aye...@wso2.com <ayshsa...@gmail.com>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Dinusha Dilrukshi
>> Associate Technical Lead
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com=D=1=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com <ayshsa...@gmail.com>
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Login and Logout error in Store

[Dinusha Senanayaka]

Hi Ayesha,

Is there a released version available now with the above fix ? Getting same
issue in AppM with jaggery.js.feature-0.12.0.

Regards,
Dinusha.

On Wed, Oct 28, 2015 at 11:21 AM, Ayesha Dissanayaka 
wrote:

> Hi,
>
> On Tue, Oct 27, 2015 at 5:53 PM, Manuranga Perera  wrote:
>
>>
>> add logic to check if instance of session object and set it to session
>> obj if true else set to request obj
>>
>
> Chanaka and myself tested this fix and it works as expected.
> Greg team will continue further testing the login/logout scenarios before
> releasing jaggery and jaggery-extension.
>
> Thanks!
> -Ayesha
>
>
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [App Manager] - Service providers are not getting listed in carbon mgt console

[Dinusha Senanayaka]

Hi IS Team,

We are moving AppManager from identity-4.5.3 dependencies to 5.0.7.

Service providers are registered by calling to
createApplication(serviceProvider) method in
 "IdentityApplicationManagementService"  service. After migration, SP
artifact get created in registry but not in identity DB.  SSO works, but SP
is not listed in UI. We need to get it listed in UI as well. Do we have
different function in 5.0.7 ?


Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Sajith Abeywardhana

[Dinusha Senanayaka]

Hi All,

It is my pleasure to welcome Sajith Abeywardhana as a WSO2 Committer.
SajithA, congratulations and keep up the good work.

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Synapse failure while moving App Manager data publisher to new version

[Dinusha Senanayaka]

On Tue, Jan 5, 2016 at 10:40 AM, Nuwan Dias  wrote:

> I guess Visitha is referring to carbon-mediation. There was an effort to
> upgrade the data-publisher dependency version recently on carbon-mediation
> but it had to be stopped due to some issues faced in the process. Jagath
> knowns the context.
>
Yes, this should be carbon-mediation.
@Jagath: What is the status of updating carbon-mediation. Is that blocked
with some issue ?

Regards,
Dinusha.

>
> On Tue, Jan 5, 2016 at 10:37 AM, Isuru Udana  wrote:
>
>> Hi Visitha,
>>
>> Synapse does not depend on data publishers.
>>
>> Thanks.
>>
>> On Tue, Jan 5, 2016 at 10:32 AM, Visitha Wijesinghe 
>> wrote:
>>
>>>
>>> Hi
>>>
>>> When App Manager moving to the new data publisher which is provided by
>>> DAS, we are getting a synapse failure.
>>>
>>>-
>>>
>>>org.wso2.carbon.databridge.commons_4.4.4
>>>-
>>>
>>>org.wso2.carbon.databridge.commons.thrift_4.4.4
>>>-
>>>
>>>org.wso2.carbon.databridge.agent.thrift_4.4.4
>>>
>>> Reason for this failure is above mentioned old version of jar's contains
>>> synapse dependencies which are not supported by the new versions mentioned
>>> bellow.
>>>
>>>-
>>>
>>>org.wso2.carbon.databridge.agent-5.0.6
>>>-
>>>
>>>org.wso2.carbon.databridge.commons.thrift_5.0.6
>>>-
>>>
>>>org.wso2.carbon.databridge.commons_5.0.6
>>>
>>> App Manager – DAS migration blocks due to this. Is there any plans of
>>> migrating synapse to the latest data publisher ? If so can we get time line
>>> for it ? Else do we have any alternative solution?
>>>
>>> --
>>>
>>> *Visitha Wijesinghe*
>>> Software Engineer Trainee.
>>> WSO2 Lanka (pvt) Ltd.
>>>
>>> Mobile - +94772617187
>>>
>>
>>
>>
>> --
>> *Isuru Udana*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nuwan Dias
>
> Technical Lead - 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
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 App Manager 1.1.0 RC1

[Dinusha Senanayaka]

Hi Devs,

This is the first release candidate of WSO2 App Manager 1.1.0.

This release fixes the following issues:
https://wso2.org/jira/browse/APPM-1081?filter=12598

Please download, test and vote.

Source & binary distribution files:
http://builder1.us1.wso2.org/~appm/release-1.1.0/RC1/wso2appm-1.1.0.zip

The tag to be voted upon:
https://github.com/wso2/product-app-manager/tree/v1.1.0


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

Thanks and Regards,
WSO2 App Manager Team.


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] App Manager 1.1.0 latest build pack - 22-12-2015

[Dinusha Senanayaka]

Hi,

Please find $subject in [1].

[1]
http://builder1.us1.wso2.org/~appm/release-1.1.0/22-12-2015/wso2appm-1.1.0-SNAPSHOT-22-12-2015.zip

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] App Manager 1.1.0 latest build pack - 21-12-2015

[Dinusha Senanayaka]

Hi,

Please find $subject in [1].

[1]
http://builder1.us1.wso2.org/~appm/release-1.1.0/21-12-2015/wso2appm-1.1.0-SNAPSHOT-21-12-2015.zip

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Does "securityConstraints" provided in jaggery.conf works for tenant users

[Dinusha Senanayaka]

Hi,

We have some jaggery APIs protected with basic auth as follows [3]. But
when tenant users try to access these APIs it gives following error [1] to
client and warn [2] in backend. In normal web apps, we could enable saas
mode using web.xml. Do we have to do something similar here ?

[1] You do not have permission to login to this application.Please contact
your administrator and request permission.

[2] WARN - CarbonTomcatRealm Illegal access attempt by dinu...@t2.com to
secured resource hosted by tenant carbon.super

[3] jaggery.conf
-

"loginConfig": {
*"authMethod": "BASIC"*
},
"securityConstraints": [
{
"securityConstraint": {
"webResourceCollection": {
"name": "store",
"urlPatterns": [
*"/apis/v1/assets/*"],*
"methods": [
"GET",
"POST",
"PUT",
"DELETE",
"HEAD",
"OPTIONS",
"TRACE",
"CONNECT",
"PATCH"
]
},
"authRoles": [
"store",
"admin"
]
}
}
]


Regards,
Dinusha.


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] App Manager 1.1.0 latest build pack - 18-12-2015

[Dinusha Senanayaka]

Hi,

Please find $subject in [1].

[1].
http://builder1.us1.wso2.org/~appm/release-1.1.0/18-12-2015/wso2appm-1.1.0-SNAPSHOT-18-12-2015.zip

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] App Manager 1.1.0 latest build pack - 16-12-2015

[Dinusha Senanayaka]

Hi,

Please find $subject in [1].

[1]
http://builder1.us1.wso2.org/~appm/release-1.1.0/16-12-2015/wso2appm-1.1.0-SNAPSHOT-16-12-2015.zip

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] App Manager 1.1.0 latest build pack - 11-12-2015

[Dinusha Senanayaka]

Hi,

Please find $subject in [1].

[1]
http://builder1.us1.wso2.org/~appm/release-1.1.0/11-12-2015/wso2appm-1.1.0-SNAPSHOT-11-12-2015.zip

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppManager] Getting an exception when logging into the app store

[Dinusha Senanayaka]

Hi Kasun,

Haven't seen this issue in App Manager released pack which has
'org.jaggeryjs.hostobjects.web_0.9.0.ALPHA4_wso2v4.jar'. But seems EMM pack
is having org.jaggeryjs.hostobjects.web_0.12.0.jar.

This might be the reason as given in this thread.  "[Dev] Login and Logout
error in Store". Can you test the fix provided by Manu there.

Regards,
Dinusha.

On Thu, Dec 10, 2015 at 9:09 PM, Kasun Dananjaya Delgolla 
wrote:

> Hi All,
>
> $subject when logging into the store jaggery app. But it doesn't affect
> the flow of the store or anything. Any idea why I'm getting this? Given
> below is the log trace.
>
> org.mozilla.javascript.WrappedException: Wrapped
> org.jaggeryjs.scriptengine.exceptions.ScriptException: Session Object has
> been reserved and cannot be instantiated by a script.
> (/store/controllers/acs.jag#91)
> at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:392)
> at org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:343)
> at org.mozilla.javascript.Context.newObject(Context.java:1504)
> at
> org.jaggeryjs.jaggery.core.listeners.WebAppSessionListener.sessionDestroyed(WebAppSessionListener.java:113)
> at
> org.apache.catalina.session.StandardSession.expire(StandardSession.java:809)
> at
> org.apache.catalina.session.StandardSession.expire(StandardSession.java:741)
> at
> org.apache.catalina.session.StandardSession.invalidate(StandardSession.java:1277)
> at
> org.apache.catalina.session.StandardSessionFacade.invalidate(StandardSessionFacade.java:188)
> at
> org.jaggeryjs.hostobjects.web.SessionHostObject.jsFunction_invalidate(SessionHostObject.java:155)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
> at
> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)
> at
> org.jaggeryjs.rhino.store.controllers.c1._c_anonymous_1(/store/controllers/acs.jag:91)
> at
> org.jaggeryjs.rhino.store.controllers.c1.call(/store/controllers/acs.jag)
> at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)
> at
> org.jaggeryjs.rhino.store.controllers.c1._c_script_0(/store/controllers/acs.jag:6)
> at
> org.jaggeryjs.rhino.store.controllers.c1.call(/store/controllers/acs.jag)
> at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
> at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
> at
> org.jaggeryjs.rhino.store.controllers.c1.call(/store/controllers/acs.jag)
> at
> org.jaggeryjs.rhino.store.controllers.c1.exec(/store/controllers/acs.jag)
> at
> org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:567)
> at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
> at
> org.jaggeryjs.jaggery.core.manager.WebAppManager.exec(WebAppManager.java:587)
> at
> org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:507)
> at org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(JaggeryServlet.java:29)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
> at
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486)
> at
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:378)
> at
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338)
> at org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> 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.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
> at
> 

[Dev] App Manager 1.1.0 latest build pack - 09-12-2015

[Dinusha Senanayaka]

Hi,

Please find $subject in [1].

[1]
http://builder1.us1.wso2.org/~appm/release-1.1.0/09-12-2015/wso2appm-1.1.0-SNAPSHOT-09-12-2015.zip

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] App Manager 1.1.0 latest build pack - 04-12-2015

[Dinusha Senanayaka]

Please use following pack instead of previously shared pack. This contains
few SSO related issue fixes.

[1]
http://builder1.us1.wso2.org/~appm/release-1.1.0/07-12-2015/wso2appm-1.1.0-SNAPSHOT-07-12-2015.zip

Regards,
Dinusha.

On Fri, Dec 4, 2015 at 9:48 PM, Dinusha Senanayaka <dinu...@wso2.com> wrote:

> Hi All,
>
> Please find $subject in [1].
>
> [1].
> http://builder1.us1.wso2.org/~appm/release-1.1.0/04-12-2015/wso2appm-1.1.0-SNAPSHOT-04-12-2015.zip
>
>
> Regards,
> Dinusha
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] App Manager 1.1.0 latest build pack - 04-12-2015

[Dinusha Senanayaka]

Hi All,

Please find $subject in [1].

[1].
http://builder1.us1.wso2.org/~appm/release-1.1.0/04-12-2015/wso2appm-1.1.0-SNAPSHOT-04-12-2015.zip


Regards,
Dinusha

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] App Manager 1.1.0 latest build pack - 02-12-2015

[Dinusha Senanayaka]

Hi All,

Please find @subject in [1].

[1]
http://builder1.us1.wso2.org/~appm/release-1.1.0/02-12-2015/wso2appm-1.1.0-SNAPSHOT-02-12-2015.zip

Regards,
Dinusha.


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Ruwan Abeykoon

[Dinusha Senanayaka]

Hi All,

It is my pleasure to welcome Ruwan Abeykoon as a WSO2 Committer.  Ruwan,
congratulations and keep up the good work.

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Releasing carbon-appmgt 1.1.1

[Dinusha Senanayaka]

Adding Supun/ Maheshika.

On Tue, Nov 17, 2015 at 6:21 PM, Dinusha Senanayaka <dinu...@wso2.com>
wrote:

> Hi Kasun,
>
> Can you please close the repo [1] and send the staging url.
>
> [1] -
> http://maven.wso2.org/nexus/service/local/staging/deploy/maven2/org/wso2/
> carbon/appmgt
>
> Regards,
> Dinusha.
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Releasing carbon-appmgt 1.1.1

[Dinusha Senanayaka]

Hi Kasun,

Can you please close the repo [1] and send the staging url.

[1] -
http://maven.wso2.org/nexus/service/local/staging/deploy/maven2/org/wso2/
carbon/appmgt

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Releasing carbon-appmgt 1.1.1

[Dinusha Senanayaka]

Thanks Maheshika.

@MDM team: Can you update to use staging repo and confirm that it's good to
go.

Regards,
Dinusha.

On Wed, Nov 18, 2015 at 9:02 AM, Maheshika Goonetilleke <mahesh...@wso2.com>
wrote:

> Hi Dinusha
>
> Staged :
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonappmgt-129/
>
> On Wed, Nov 18, 2015 at 12:04 AM, Rushmin Fernando <rush...@wso2.com>
> wrote:
>
>>
>> On Tue, Nov 17, 2015 at 4:04 PM, Dinusha Senanayaka <dinu...@wso2.com>
>> wrote:
>>
>>> Adding Supun/ Maheshika.
>>>
>>> On Tue, Nov 17, 2015 at 6:21 PM, Dinusha Senanayaka <dinu...@wso2.com>
>>> wrote:
>>>
>>>> Hi Kasun,
>>>>
>>>> Can you please close the repo [1] and send the staging url.
>>>>
>>>> [1] -
>>>> http://maven.wso2.org/nexus/service/local/staging/deploy/maven2/org/wso2/
>>>> carbon/appmgt
>>>>
>>>> Regards,
>>>> Dinusha.
>>>>
>>>> --
>>>> Dinusha Dilrukshi
>>>> Associate Technical Lead
>>>> WSO2 Inc.: http://wso2.com/
>>>> Mobile: +94725255071
>>>> Blog: http://dinushasblog.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Dinusha Dilrukshi
>>> Associate Technical Lead
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94725255071
>>> Blog: http://dinushasblog.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Rushmin Fernando*
>> *Technical Lead*
>>
>> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware
>>
>> email : rush...@wso2.com
>> mobile : +94772310855
>>
>>
>>
>
>
> --
>
> Thanks & Best Regards,
>
> Maheshika Goonetilleke
> Engineering Process Coordinator
>
> *WSO2 Inc*
> *email   : mahesh...@wso2.com <mahesh...@wso2.com>*
> *mobile : +94 773 596707 <%2B94%20773%20596707>*
> *www: :http://wso2.com <http://wso2.com/>*lean . enterprise . middleware
>
>
>
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] App Manager integration with MDM(EMM)

[Dinusha Senanayaka]

Hi Ruwan,

Need some help to figure out, OSGi based MDM integration.

Found this commit relate to this "[carbon-appmgt] Added OSGI based MDM
integration. (#103)"

But not sure EMM has merged this to their repo. Do you have any idea ?

@Chathura:  How do we get consumer/secret key from MDM with JAX-RS
integration ? (EMM doesn't have provided UI for this).

Regards,
Dinusha



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] "carbon-appmgt" has classes named as "APIM*"?

[Dinusha Senanayaka]

Hi Prabath,

Yeah, this is something we already doing in the master with the refactoring
we are doing.

Regards,
Dinusha.

On Wed, Oct 28, 2015 at 11:40 AM, Prabath Abeysekera 
wrote:

> Folks,
>
> Shouldn't these be renamed? Or completely removed and use appropriate
> utilities available in "carbon-apimgt", instead?
>
> Cheers,
> Prabath
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Redundant properties in "carbon-appmgt" parent POM

[Dinusha Senanayaka]

Hi Prabath,

Thanks for reporting. Will check them.

Regards,
Dinusha.

On Wed, Oct 28, 2015 at 11:20 AM, Prabath Abeysekera 
wrote:

> Folks,
>
> I can see the following two properties defined in the parent POM of
> "carbon-appmgt" repository, which appear to be redundant.
>
> 4.4.2 - This has to be
> replaced with "carbon.kernel.version" for better maintainability.
>
> 4.4.1 - This needs to
> be removed as none of the components seems to use it.
>
> Please fix.
>
> Cheers,
> Prabath
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Lahiru Cooray

[Dinusha Senanayaka]

Hi All,

Its my pleasure to welcome Lahiru Cooray as a WSO2 Committer.

Lahiru, welcome aboard and keep up the good work ..

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Content repository for App Manager

[Dinusha Senanayaka]

Hi,

For the mobile apps we need to store the .apk files. Currently we use the
file system based storage which has used in EMM-1.0.0 (Stored in
repository/resources/).  In a cluster environment we need to have a shared
file system. This become difficult in a could deployment like AWS.

Also in future we might need to have a content repository with the other
types of app support like desktop application etc. One option is to extend
and use the DepSync. Do we have any other suggestions here ?

Regards,
Dinusha.


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev