Re: [Dev] Cannot generate P2 metadata: P2 publisher return code was 13

2016-04-17 Thread Damith Wickramasinghe
Hi Lasantha,

I have checked the log file. It does not have any information other than
the same thing mention in the above log One or more certificates rejected.
Cannot proceed with installation. After installing the Java again solved
the issue.

Regards,
Damith.


On Mon, Apr 18, 2016 at 8:12 AM, Lasantha Fernando 
wrote:

> Hi Damith,
>
> Were you able to get any more information from the log file mentioned in
> the above stack trace?
>
> log file location: /home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-
> runtime/0.13.0/eclipse/configuration/1460895093502.log
>
> Can you post any error information in that log file as well?
>
> Thanks,
> Lasantha
>
> On 17 April 2016 at 22:47, Damith Wickramasinghe  wrote:
>
>> Hi Mohan,
>>
>> Maven version is 3.0.5. and java is 1.7 .Following is the complete trace
>> i got.
>>
>>  Command line:
>> /bin/sh -c cd
>> /home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen
>> && /usr/lib/jvm/java-7-oracle/jre/bin/java -jar
>> /home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
>> -nosplash -application org.eclipse.equinox.p2.director -metadataRepository
>> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/p2-repo
>> -artifactRepository
>> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/p2-repo
>> -installIU carbon.product.id -profileProperties
>> org.eclipse.update.install.features=true -profile worker -bundlepool
>> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components
>> -shared
>> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components/p2
>> -destination
>> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components/worker
>> -p2.os linux -p2.ws gtk -p2.arch x86 -roaming
>> Installing carbon.product.id 4.4.3.
>> Installation failed.
>> One or more certificates rejected. Cannot proceed with installation.
>> Application failed, log file location:
>> /home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1460895093502.log
>>
>> [INFO]
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] WSO2 CEP - Parent . SUCCESS
>> [0.972s]
>> [INFO] WSO2 CEP - Style Parent ... SUCCESS
>> [0.040s]
>> [INFO] WSO2 CEP - Styles . SUCCESS
>> [1.216s]
>> [INFO] WSO2 Stratos CEP - Styles . SUCCESS
>> [0.185s]
>> [INFO] WSO2 CEP - Samples Parent . SUCCESS
>> [0.023s]
>> [INFO] WSO2 CEP - Samples Producers .. SUCCESS
>> [0.046s]
>> [INFO] WSO2 CEP - Producer - WSO2 Event Client ... SUCCESS
>> [8.591s]
>> [INFO] WSO2 CEP - Publisher - HTTP Client  SUCCESS
>> [0.336s]
>> [INFO] WSO2 CEP - Publisher - JMS Client . SUCCESS
>> [2.722s]
>> [INFO] WSO2 CEP - Publisher - MQTT Client  SUCCESS
>> [0.171s]
>> [INFO] WSO2 CEP - Publisher - Kafka Client ... SUCCESS
>> [11.891s]
>> [INFO] WSO2 CEP - Publisher - SOAP Client  SUCCESS
>> [0.551s]
>> [INFO] WSO2 CEP - Producer - Websocket Publisher . SUCCESS
>> [4.295s]
>> [INFO] WSO2 CEP - Producer - Performance Test  SUCCESS
>> [0.475s]
>> [INFO] WSO2 CEP - Publisher - HTTP Performance Client  SUCCESS
>> [0.166s]
>> [INFO] WSO2 CEP - Publisher - Kafka Producer . SUCCESS
>> [0.174s]
>> [INFO] WSO2 CEP - Publisher - JMS Performance Client . SUCCESS
>> [0.150s]
>> [INFO] WSO2 CEP - Sample Consumers ... SUCCESS
>> [0.035s]
>> [INFO] WSO2 CEP - Consumer - WSO2 Event Server ... SUCCESS
>> [1.061s]
>> [INFO] WSO2 CEP - Consumer - JMS Consumer  SUCCESS
>> [0.145s]
>> [INFO] WSO2 CEP - Consumer - MQTT Consumer ... SUCCESS
>> [0.103s]
>> [INFO] WSO2 CEP - Consumer - Axis2 Log Service ... SUCCESS
>> [0.090s]
>> [INFO] WSO2 CEP - Consumer - Generic Log Service . SUCCESS
>> [1.271s]
>> [INFO] WSO2 CEP - Consumer - Dashboard Service ... SUCCESS
>> [0.117s]
>> [INFO] WSO2 CEP - Consumer - Websocket Consumer .. SUCCESS
>> [0.294s]
>> [INFO] WSO2 CEP - Consumer - WSO2 Event Server ... SUCCESS
>> [0.788s]
>> [INFO] WSO2 CEP - Consumer - HTTP Performance Service  SUCCESS
>> [0.146s]
>> [INFO] WSO2 CEP - Consumer - Kafka Consumer .. SUCCESS
>> [0.143s]
>> [INFO] WSO2 CEP - Consumer - JMS Performance Consumer  SUCCESS
>> [0.108s]
>> [INFO] Siddhi Extension - Geo Event Fuser  SUCCESS
>> [0.679s]
>> [INFO] Siddhi Extension - Geo Event 

Re: [Dev] product-mss hangs after deploying a (faulty) service

2016-04-17 Thread Hasitha Aravinda
Hi Kernel team,

This is happening due to an issue in msf4j 1.0.0 component and solution is
to move latest msf4j version. But still msf4j master branch is set to
1.0.0-SNAPSHOT. Since MSF4J 1.0.0 is released, Jenkins is not publishing
snapshot artifacts to nexus. Could you please fix this ?

[1] - https://github.com/wso2/msf4j/tree/master

Thanks,
Hasitha.

On Fri, Apr 8, 2016 at 5:35 PM, Hasitha Aravinda  wrote:

> I have updated kernel version to 5.1.0-SNAPSHOT and now I am getting
> following error. What could be the issue. ?
>
> [2016-04-08 17:24:26,865]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
> Startup component netty-transports-mgt from
> bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
> state until Capability
> org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
> from bundle(msf4j-core:1.0.0) is available
> [2016-04-08 17:24:26,866]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
> Startup component netty-transports-mgt from
> bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
> state until Capability
> org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
> from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available
> [2016-04-08 17:24:26,866]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
> Startup component carbon-transport-mgt from
> bundle(org.wso2.carbon.core:5.1.0.SNAPSHOT) will be in the pending state
> until Capability
> org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent
> from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available
>
>
> Thanks,
> Hasitha.
>
> On Thu, Apr 7, 2016 at 6:57 PM, Rasika Perera  wrote:
>
>> Hi Himasha,
>>
>> This usually happens when MSF4J is waiting for its required capabilities.
>> MSF4J has cardinality of AT_LEAST_ONE as required capabilities for the Carbon
>> Transport. Which means server is waiting on the startup for at least one
>> OSGi service implementing CarbonTransport.class interface[1]. As Aruna
>> mentioned can you verify whether you are packing carbon transport.
>>
>> However one issue found on your pom file.
>>
>> 
>> org.wso2.carbon.bpmn.rest.**,*
>> version=${carbon.business-process.exp.pkg.version},
>> 
>>
>> should be corrected as;
>>
>> 
>> org.wso2.carbon.bpmn.rest.**;*
>> version=${carbon.business-process.exp.pkg.version},
>> 
>>
>> [1]
>> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/MicroservicesServerSC.java#L74
>>
>> Thanks
>> ~Rasika
>>
>>
>> On Thu, Apr 7, 2016 at 2:47 PM, Aruna Karunarathna 
>> wrote:
>>
>>> Have you guys added the carbon-transport-mgt?
>>>
>>> On Thu, Apr 7, 2016 at 1:57 PM, Hasitha Aravinda 
>>> wrote:
>>>
 Hi Manu,

 were you able to solve this issue, I am getting the same error.

 Thanks,
 Hasitha.

 On Wed, Feb 10, 2016 at 1:42 PM, Manuranga Perera 
 wrote:

> MSS product hangs when I deploy my service, but fat-jar mode works.
>
> prints
> Waiting on pending capability registration. Capability:
> org.wso2.msf4j.Interceptor
>
> how to proceed debugging?
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 --
 Hasitha Aravinda,
 Senior Software Engineer,
 WSO2 Inc.
 Email: hasi...@wso2.com
 Mobile : +94 718 210 200

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


>>>
>>>
>>> --
>>>
>>> *Aruna Sujith Karunarathna *
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.wso2.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software Engineer
>> M: +94 71 680 9060 E: rasi...@wso2.com
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> --
> Hasitha Aravinda,
> Senior Software Engineer,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile : +94 718 210 200
>



-- 
--
Hasitha Aravinda,
Senior Software Engineer,
WSO2 Inc.
Email: hasi...@wso2.com
Mobile : +94 718 210 200
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Clarification about OSGi Bundle Picking

2016-04-17 Thread Aruna Karunarathna
On Sun, Apr 17, 2016 at 11:09 PM, Chamila Wijayarathna 
wrote:

> Hi all,
>
> So myself and Malithi dig this issue little bit and observed following.
>
> As I mentioned earlier by default we had opensaml2.6.4wasov2.jar in
> plugins directory and I removed it. But there were an entry in
> /repository/components/default/configuration/org.eclipse.equinox.simpleconfigurator/
> bundles.info file corresponding to that jar file as following.
>
> opensaml,2.6.4.wso2v2,../plugins/opensaml_2.6.4.wso2v2.jar,4,true
>
> Until this entry is there in bundle.info, server is not picking up 
> opensaml_2.6.4.wso2v2.jar
> that I am putting into dropins.
>
> Then I deleted this entry in bundle.info file, and restarted the server.
> Now its picking the v2 jar file in dropins and also in bundle.info file,
> I observed following new entry.
>
> opensaml,2.6.4.wso2v2,../dropins/opensaml_2.6.4.wso2v2.jar,4,true
>
> So what I assumed is, at startup, server is writing an entry at
> bundle.info for every jar in dropins, but since there were the previous
> entry which was also for same jar 'opensaml,2.6.4.wso2v2' it failed to
> write new entry for the jar in the dropins.
>
> Any way these are only observations and If anyone can explain the theory
> behind this, that would be very helpful.
>

The priority is given to the bundles.info file, if you added bundles to the
dropins folder with the same symbolic name and version, it will be ignored,
and if it's not there in bundles.info file new entry will be added.


> Thanks!
>
> On Sun, Apr 17, 2016 at 10:23 PM, Malithi Edirisinghe 
> wrote:
>
>> Hi Chamila,
>>
>> We have specified a version range which is [2.6.0,3.0.0). Both v1 and v2
>> versions get included for this range. Since we have not exactly specified
>> that a particular bundle should pick only v2 version, the bundle could be
>> wired to either v1 or v2 at runtime as per the availability.
>>
>> Thanks,
>> Malithi.
>>
>> On Sun, Apr 17, 2016 at 9:59 PM, Thusitha Thilina Dayaratne <
>> thusit...@wso2.com> wrote:
>>
>>> Hi Chamila,
>>>
>>> Did you export and import the correct versions ?
>>>
>>> Thanks
>>> Thusitha
>>>
>>> On Sat, Apr 16, 2016 at 1:11 PM, Chamila Wijayarathna 
>>> wrote:
>>>
 Hi all,

 IS-5.2.0-Beta uses opensaml2.6.4wasov2. I extracted a pack and
 deleted opensaml2.6.4wasov2.jar from its repository/components/plugins
 folder and then copied opensaml2.6.4wasov1.jar into
 repository/components/dropins folder. Here it worked properly where IS got
 started without any issue and I could reproduced an issue which was there
 in v1 but fixed in v2.

 Then I copied opensaml2.6.4wasov2.jar into
 repository/components/dropins folder and restarted IS again. But now also I
 could reproduced the earlier mentioned error which implies that IS is still
 picking v1 not v2. According to my understanding about OSGi, here IS should
 pick v2 instead of v1.

 Am I doing anything wrong here. What could be the reason for this issue?

 Thank You!

 --
 *Chamila Dilshan Wijayarathna,*
 Software Engineer
 Mobile:(+94)788193620
 WSO2 Inc., http://wso2.com/

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


>>>
>>>
>>> --
>>> Thusitha Dayaratne
>>> Software Engineer
>>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>>
>>> Mobile  +94712756809
>>> Blog  alokayasoya.blogspot.com
>>> Abouthttp://about.me/thusithathilina
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Malithi Edirisinghe*
>> Senior Software Engineer
>> WSO2 Inc.
>>
>> Mobile : +94 (0) 718176807
>> malit...@wso2.com
>>
>
>
>
> --
> *Chamila Dilshan Wijayarathna,*
> Software Engineer
> Mobile:(+94)788193620
> WSO2 Inc., http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Aruna Sujith Karunarathna *
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [App Cloud] Custom Applications on AppCloud

2016-04-17 Thread Nishadi Kirielle
Hi,
With the implemented feature we can input the above docker image url with
the ports that should be exposed (http port and https port). Then the
procedure is to pull the docker image and push it to the docker registry.
Then it will follow the standard procedure in to deploy it in AppCloud.

Thanks
Nishadi

On Tue, Apr 12, 2016 at 8:18 PM, Kasun De Silva  wrote:

> Hi Nishadi,
>
> As for now this feature is expected to be exposed only to internal users
>> by updating the configuration file.
>
>
> How did we do this? what is the config file used ?
>
> Can you provide some example how can we use this feature. Say I have an
> image "kasun/af_tomcat" how can I deploy this in AppCloud using this
> feature?
>
> Thanks,
> Kasun
>



-- 
*Nishadi Kirielle*
*Software Engineering Intern*
Mobile : +94 (0) 714722148
Blog : http://nishadikirielle.blogspot.com/
nish...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] How to exchange a SAML2 bearer token with OAuth2 token

2016-04-17 Thread Geesara Prathap
This is the issue[1] I am facing right now. Also, there is similar issue[2]
 which was encountered in
APIM 1.10

1. https://gist.github.com/GPrathap/2326db6be8fcfeb09755abb136b4564a
2. https://wso2.org/jira/browse/APIMANAGER-4554


Thanks,
Geesara

2016-04-18 7:52 GMT+05:30 Geesara Prathap :

> Hi All,
>
> As an example, I enabled SSO in Dashboard Server and registered the portal
> app with the Identity Server by creating a service provider. So I was able
> to get SAML bearer assertion in SAML response. Then created an application
> in API Manager and  combined the consumer key and consumer secret keys as
> consumer-key:consumer-secret then encoded the combined string using base64.
> After that filtered out SAML bearer assertion from SAML response and
> encoded into base64-URL.
>
> SAML  bearer assertion
>
>  IssueInstant="2016-04-17T15:31:00.991Z" Version="2.0"
> xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion"> Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity">localhost xmlns:ds="http://www.w3.org/2000/09/xmldsig#;> Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> URI="#iddkjncialbbnlpfjhmkjhebojbpkhfppjglhfga"> Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>fk3OExA6WC93w7o7ckZudmP4N3Q=UJyh3pYatemvZVMnLM0CZKb3HWWeCGD2AXJtY+zme4cQXNVtzi+ugHW0dHz+ZbpUykPFdCspYA1K1g/15x4yEH2MY6zPACvqVcfxEgqcrlDVTUSTeKtr+8+4zoYBtJb0usSEui+22vpzlEv3f++7eVAFwWLDODS0QPChpF39hxs7s1l+9zBR4rciSh5hQW5n/Ww56dgS1pzn4DY+slIdBCme7fSRozVEhiihotqEZ+Oa7CSvSZzPycDLEFXfeJDmRp+JD1vE9KIoygHtOr3BFL9H1RIXm+3rO7128XChPL2ZP1zfwBfwmGzRb7mC2iPXw3TTV9pcl9HzQJLFtiyywnFcN0kAbkY0N3mJQgARDbCKf4v2zG7x4MqXroPYAishe3bStkwgkO63xGiMI4XhaQCMGCcQB6TDVpvd7bb9zyYPyXMrqBLMQg4X6jZTOgpRfEUyQEItquEjvjRyV0yPgO9ULBUK5qhmZYOVn5ef7c8kk/ceh4diVoOFdyuYdw7KmLw3RjFgxMzbm8QOyfwhn0f75wiDt7ctokpRSwf3PBkIP7al6cEs3d6aHM9N94NY5ZGSHij+fV5dRZieZMv3zkYcEj90o8eRJk8nDgO5zpo40k/mbfWnAkpEwXdGyMFnK6CWW6oPGbY0qnoLPio4gytdEW+DBIdK+lTFbyzhafM=MIIFkzCCA3sCBAKkVfcwDQYJKoZIhvcNAQEFBQAwgY0xCzAJBgNVBAYTAlNMMRAwDgYDVQQIEwdXZXN0ZXJuMRAwDgYDVQQHEwdDb2xvbWJvMQ0wCwYDVQQKEwRXU08yMRQwEgYDVQQLEwtFbmdpbmVlcmluZzESMBAGA1UEAxMJbG9jYWxob3N0MSEwHwYJKoZIhvcNAQkBFhJpb3RzZXJ2ZXJAd3NvMi5jb20wHhcNMTUxMjE3MTMxMTA0WhcNMTcxMjE2MTMxMTA0WjCBjTELMAkGA1UEBhMCU0wxEDAOBgNVBAgTB1dlc3Rlcm4xEDAOBgNVBAcTB0NvbG9tYm8xDTALBgNVBAoTBFdTTzIxFDASBgNVBAsTC0VuZ2luZWVyaW5nMRIwEAYDVQQDEwlsb2NhbGhvc3QxITAfBgkqhkiG9w0BCQEWEmlvdHNlcnZlckB3c28yLmNvbTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBALkiGVQ9tZOKIi/gD/toV+enq+neqOBGYQ8Fq/ABOWnK2QpGWm81+Rets5GbQ6W//D8C5TOBGqK7z+LAgdmILr1XLkvrXWoan0GPdDJ1wpc2/6XDZvM5f7Y8cmRqVPJv7AF+ImgF9dqv97gYCiujy+nNHd5Nk/60pco2LBV5SyLqqrzKXEnSGrS4zoYWpPeJ9YrXPEkW7A6AxTQK0yU9Ej4TktgafbTueythrLomKiZJj4wPxm2lA2lAZscDdws9NWrI5z/LUVLbUMxrY10Nig1liX5b1mrUk5bb1d2tqwkPrpRILKoOBJtI674SQS3GziiUiCJGIO/EGGRn1AJsC/SvnnEez3WKY/DgJ6102MWK/yWtY8NYHUX2anwMBS7UpT5A4BXdsfBz3R+iPF99FxdAGGsS4GQuuPocZaycLqoPCxpTSSxBsKMUcKpn3yaiQRd6uDuiTNt7odDOQj0Tno7uokh/HILgbzvj9EExDOsdwLVvqYmUHBPeLmiICWXfi4kyH/twPOZtV9eVnfWYx5Kwg+2Y4fIb3q4ABr0hzxaMYHQo6NOukSH1BcdAWiQIXbSFFaTZD8p6OfiZpHcQ59HT/Z8GBlCFL2xkYJFmOhXI/Cu+xrcwqEIInv7d8w3eiNQ7MneomEptLbBk9+kMsP0ubo34oOGHR9qk3Lj580c/AgMBAAEwDQYJKoZIhvcNAQEFBQADggIBADw70g2/wrgzrAM8OXBlthGbCEaXZpKwq9IJN0qu+/l+PNwF7csQhj+qW+zMrWaH1DGWJroaei1+NFFrj/pvp61rF/ZeTPGVJd7puCq++SevqIrzKyAEBtwtpXmcFhBpV/FrQAv3ODOJ3bN2wSRPZHUvARTBB3RaUI06g1jCaBzjDEGoMfSxdr5/Ty2WxTI9u9RlIs3Q52AiOmROtLPiEQZQIqfNO3cxCEWojHxPqVEZA/kQYy+rryj4H0zzSrj7QFlQhsMDw5j8bv9AcvTEGmwp29avsgnceDWinI6lwtd8zqh0ZW9QJdH0BRNCM/EkTlTUHeEg04/sOgOrlWcvEfVxDqNEtbUzU9UFxl0lkQkuRn1UdxZlvhWaFnel5iRC9b7OZvi2mkVujLyxEWlJB1tuyMLQxu6PfabBVODP5V8/+uyiiK/gwrB5rYl8RHxGoznJnI1Y3HVzKlA849CrMBaY5vnhE03cNja7QroPzLmmuXBLk2LbI1lu5nJAqKpBUPMI/IU3pF4Q7VTD2ZANI+ktGgGlM8AK4OJHWOhj8W289pWTHVjG8syPLTsaYkhgLjzZl/g9cUwn/96NJNvzd3dkT+7VgE+BJOLofq25CjZcN1M7MhWdl3vbWNj9vzL0+FCnwca8UecfvFS39PIekIvqbtP+Gw8NiYOUGIllZ0JH Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">admin@carbon.super Method="urn:oasis:names:tc:SAML:2.0:cm:bearer"> InResponseTo="ghmnopmcckmfdgkbncdbfaddoablkleedohalfib"
> NotOnOrAfter="2016-04-17T15:36:00.991Z" Recipient="
> https://localhost:9443/portal/acs"/> Method="urn:oasis:names:tc:SAML:2.0:cm:bearer"> InResponseTo="ghmnopmcckmfdgkbncdbfaddoablkleedohalfib"
> NotOnOrAfter="2016-04-17T15:36:00.991Z" Recipient="
> https://localhost:9443/oauth2/token"/> NotBefore="2016-04-17T15:31:00.991Z"
> NotOnOrAfter="2016-04-17T15:36:00.991Z">portal
> https://localhost:9443/oauth2/tokencarbonServer AuthnInstant="2016-04-17T15:31:00.992Z"
> SessionIndex="2211a42e-d554-4e94-a59a-5269b920a3e7">urn:oasis:names:tc:SAML:2.0:ac:classes:Password
>
>
> To exchange the SAML2 bearer token for an OAuth2.0 access token, this is
> the command I used.
>
> curl -k -d
> 

Re: [Dev] Cannot generate P2 metadata: P2 publisher return code was 13

2016-04-17 Thread Lasantha Fernando
Hi Damith,

Were you able to get any more information from the log file mentioned in
the above stack trace?

log file location: /home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-
runtime/0.13.0/eclipse/configuration/1460895093502.log

Can you post any error information in that log file as well?

Thanks,
Lasantha

On 17 April 2016 at 22:47, Damith Wickramasinghe  wrote:

> Hi Mohan,
>
> Maven version is 3.0.5. and java is 1.7 .Following is the complete trace i
> got.
>
>  Command line:
> /bin/sh -c cd
> /home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen
> && /usr/lib/jvm/java-7-oracle/jre/bin/java -jar
> /home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
> -nosplash -application org.eclipse.equinox.p2.director -metadataRepository
> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/p2-repo
> -artifactRepository
> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/p2-repo
> -installIU carbon.product.id -profileProperties
> org.eclipse.update.install.features=true -profile worker -bundlepool
> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components
> -shared
> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components/p2
> -destination
> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components/worker
> -p2.os linux -p2.ws gtk -p2.arch x86 -roaming
> Installing carbon.product.id 4.4.3.
> Installation failed.
> One or more certificates rejected. Cannot proceed with installation.
> Application failed, log file location:
> /home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1460895093502.log
>
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 CEP - Parent . SUCCESS [0.972s]
> [INFO] WSO2 CEP - Style Parent ... SUCCESS [0.040s]
> [INFO] WSO2 CEP - Styles . SUCCESS [1.216s]
> [INFO] WSO2 Stratos CEP - Styles . SUCCESS [0.185s]
> [INFO] WSO2 CEP - Samples Parent . SUCCESS [0.023s]
> [INFO] WSO2 CEP - Samples Producers .. SUCCESS [0.046s]
> [INFO] WSO2 CEP - Producer - WSO2 Event Client ... SUCCESS [8.591s]
> [INFO] WSO2 CEP - Publisher - HTTP Client  SUCCESS [0.336s]
> [INFO] WSO2 CEP - Publisher - JMS Client . SUCCESS [2.722s]
> [INFO] WSO2 CEP - Publisher - MQTT Client  SUCCESS [0.171s]
> [INFO] WSO2 CEP - Publisher - Kafka Client ... SUCCESS
> [11.891s]
> [INFO] WSO2 CEP - Publisher - SOAP Client  SUCCESS [0.551s]
> [INFO] WSO2 CEP - Producer - Websocket Publisher . SUCCESS [4.295s]
> [INFO] WSO2 CEP - Producer - Performance Test  SUCCESS [0.475s]
> [INFO] WSO2 CEP - Publisher - HTTP Performance Client  SUCCESS [0.166s]
> [INFO] WSO2 CEP - Publisher - Kafka Producer . SUCCESS [0.174s]
> [INFO] WSO2 CEP - Publisher - JMS Performance Client . SUCCESS [0.150s]
> [INFO] WSO2 CEP - Sample Consumers ... SUCCESS [0.035s]
> [INFO] WSO2 CEP - Consumer - WSO2 Event Server ... SUCCESS [1.061s]
> [INFO] WSO2 CEP - Consumer - JMS Consumer  SUCCESS [0.145s]
> [INFO] WSO2 CEP - Consumer - MQTT Consumer ... SUCCESS [0.103s]
> [INFO] WSO2 CEP - Consumer - Axis2 Log Service ... SUCCESS [0.090s]
> [INFO] WSO2 CEP - Consumer - Generic Log Service . SUCCESS [1.271s]
> [INFO] WSO2 CEP - Consumer - Dashboard Service ... SUCCESS [0.117s]
> [INFO] WSO2 CEP - Consumer - Websocket Consumer .. SUCCESS [0.294s]
> [INFO] WSO2 CEP - Consumer - WSO2 Event Server ... SUCCESS [0.788s]
> [INFO] WSO2 CEP - Consumer - HTTP Performance Service  SUCCESS [0.146s]
> [INFO] WSO2 CEP - Consumer - Kafka Consumer .. SUCCESS [0.143s]
> [INFO] WSO2 CEP - Consumer - JMS Performance Consumer  SUCCESS [0.108s]
> [INFO] Siddhi Extension - Geo Event Fuser  SUCCESS [0.679s]
> [INFO] Siddhi Extension - Geo Event Notifier . SUCCESS [0.261s]
> [INFO] WSO2 CEP - Feature Parent . SUCCESS [0.013s]
> [INFO] WSO2 CEP - Features ... SUCCESS [0.014s]
> [INFO] WSO2 CEP - Styles Features  SUCCESS [0.290s]
> [INFO] WSO2 Stratos CEP - Features ... SUCCESS [0.014s]
> [INFO] WSO2 Stratos CEP - Styles Features  SUCCESS [0.058s]
> [INFO] WSO2 Stratos CEP - Dashboard UI ... SUCCESS [7.802s]
> [INFO] 

[Dev] How to exchange a SAML2 bearer token with OAuth2 token

2016-04-17 Thread Geesara Prathap
Hi All,

As an example, I enabled SSO in Dashboard Server and registered the portal
app with the Identity Server by creating a service provider. So I was able
to get SAML bearer assertion in SAML response. Then created an application
in API Manager and  combined the consumer key and consumer secret keys as
consumer-key:consumer-secret then encoded the combined string using base64.
After that filtered out SAML bearer assertion from SAML response and
encoded into base64-URL.

SAML  bearer assertion

localhosthttp://www.w3.org/2000/09/xmldsig#;>http://www.w3.org/2001/10/xml-exc-c14n#"/>http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>http://www.w3.org/2001/10/xml-exc-c14n#"/>http://www.w3.org/2000/09/xmldsig#sha1"/>fk3OExA6WC93w7o7ckZudmP4N3Q=UJyh3pYatemvZVMnLM0CZKb3HWWeCGD2AXJtY+zme4cQXNVtzi+ugHW0dHz+ZbpUykPFdCspYA1K1g/15x4yEH2MY6zPACvqVcfxEgqcrlDVTUSTeKtr+8+4zoYBtJb0usSEui+22vpzlEv3f++7eVAFwWLDODS0QPChpF39hxs7s1l+9zBR4rciSh5hQW5n/Ww56dgS1pzn4DY+slIdBCme7fSRozVEhiihotqEZ+Oa7CSvSZzPycDLEFXfeJDmRp+JD1vE9KIoygHtOr3BFL9H1RIXm+3rO7128XChPL2ZP1zfwBfwmGzRb7mC2iPXw3TTV9pcl9HzQJLFtiyywnFcN0kAbkY0N3mJQgARDbCKf4v2zG7x4MqXroPYAishe3bStkwgkO63xGiMI4XhaQCMGCcQB6TDVpvd7bb9zyYPyXMrqBLMQg4X6jZTOgpRfEUyQEItquEjvjRyV0yPgO9ULBUK5qhmZYOVn5ef7c8kk/ceh4diVoOFdyuYdw7KmLw3RjFgxMzbm8QOyfwhn0f75wiDt7ctokpRSwf3PBkIP7al6cEs3d6aHM9N94NY5ZGSHij+fV5dRZieZMv3zkYcEj90o8eRJk8nDgO5zpo40k/mbfWnAkpEwXdGyMFnK6CWW6oPGbY0qnoLPio4gytdEW+DBIdK+lTFbyzhafM=MIIFkzCCA3sCBAKkVfcwDQYJKoZIhvcNAQEFBQAwgY0xCzAJBgNVBAYTAlNMMRAwDgYDVQQIEwdXZXN0ZXJuMRAwDgYDVQQHEwdDb2xvbWJvMQ0wCwYDVQQKEwRXU08yMRQwEgYDVQQLEwtFbmdpbmVlcmluZzESMBAGA1UEAxMJbG9jYWxob3N0MSEwHwYJKoZIhvcNAQkBFhJpb3RzZXJ2ZXJAd3NvMi5jb20wHhcNMTUxMjE3MTMxMTA0WhcNMTcxMjE2MTMxMTA0WjCBjTELMAkGA1UEBhMCU0wxEDAOBgNVBAgTB1dlc3Rlcm4xEDAOBgNVBAcTB0NvbG9tYm8xDTALBgNVBAoTBFdTTzIxFDASBgNVBAsTC0VuZ2luZWVyaW5nMRIwEAYDVQQDEwlsb2NhbGhvc3QxITAfBgkqhkiG9w0BCQEWEmlvdHNlcnZlckB3c28yLmNvbTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBALkiGVQ9tZOKIi/gD/toV+enq+neqOBGYQ8Fq/ABOWnK2QpGWm81+Rets5GbQ6W//D8C5TOBGqK7z+LAgdmILr1XLkvrXWoan0GPdDJ1wpc2/6XDZvM5f7Y8cmRqVPJv7AF+ImgF9dqv97gYCiujy+nNHd5Nk/60pco2LBV5SyLqqrzKXEnSGrS4zoYWpPeJ9YrXPEkW7A6AxTQK0yU9Ej4TktgafbTueythrLomKiZJj4wPxm2lA2lAZscDdws9NWrI5z/LUVLbUMxrY10Nig1liX5b1mrUk5bb1d2tqwkPrpRILKoOBJtI674SQS3GziiUiCJGIO/EGGRn1AJsC/SvnnEez3WKY/DgJ6102MWK/yWtY8NYHUX2anwMBS7UpT5A4BXdsfBz3R+iPF99FxdAGGsS4GQuuPocZaycLqoPCxpTSSxBsKMUcKpn3yaiQRd6uDuiTNt7odDOQj0Tno7uokh/HILgbzvj9EExDOsdwLVvqYmUHBPeLmiICWXfi4kyH/twPOZtV9eVnfWYx5Kwg+2Y4fIb3q4ABr0hzxaMYHQo6NOukSH1BcdAWiQIXbSFFaTZD8p6OfiZpHcQ59HT/Z8GBlCFL2xkYJFmOhXI/Cu+xrcwqEIInv7d8w3eiNQ7MneomEptLbBk9+kMsP0ubo34oOGHR9qk3Lj580c/AgMBAAEwDQYJKoZIhvcNAQEFBQADggIBADw70g2/wrgzrAM8OXBlthGbCEaXZpKwq9IJN0qu+/l+PNwF7csQhj+qW+zMrWaH1DGWJroaei1+NFFrj/pvp61rF/ZeTPGVJd7puCq++SevqIrzKyAEBtwtpXmcFhBpV/FrQAv3ODOJ3bN2wSRPZHUvARTBB3RaUI06g1jCaBzjDEGoMfSxdr5/Ty2WxTI9u9RlIs3Q52AiOmROtLPiEQZQIqfNO3cxCEWojHxPqVEZA/kQYy+rryj4H0zzSrj7QFlQhsMDw5j8bv9AcvTEGmwp29avsgnceDWinI6lwtd8zqh0ZW9QJdH0BRNCM/EkTlTUHeEg04/sOgOrlWcvEfVxDqNEtbUzU9UFxl0lkQkuRn1UdxZlvhWaFnel5iRC9b7OZvi2mkVujLyxEWlJB1tuyMLQxu6PfabBVODP5V8/+uyiiK/gwrB5rYl8RHxGoznJnI1Y3HVzKlA849CrMBaY5vnhE03cNja7QroPzLmmuXBLk2LbI1lu5nJAqKpBUPMI/IU3pF4Q7VTD2ZANI+ktGgGlM8AK4OJHWOhj8W289pWTHVjG8syPLTsaYkhgLjzZl/g9cUwn/96NJNvzd3dkT+7VgE+BJOLofq25CjZcN1M7MhWdl3vbWNj9vzL0+FCnwca8UecfvFS39PIekIvqbtP+Gw8NiYOUGIllZ0JHadmin@carbon.superhttps://localhost:9443/portal/acs"/>https://localhost:9443/oauth2/token"/>portal
https://localhost:9443/oauth2/tokencarbonServerurn:oasis:names:tc:SAML:2.0:ac:classes:Password


To exchange the SAML2 bearer token for an OAuth2.0 access token, this is
the command I used.

curl -k -d

Re: [Dev] Clarification about OSGi Bundle Picking

2016-04-17 Thread Danushka Fernando
Sorry I misread your first email. All the jars inside the plugins folder
are installed as features. So yes definitely there will be a entry in
bundles.info for each. That's why we use patches folder to patch jars in
plugins folder. When you deleted a jar this bundles.info entry would not go
away. If you try some osgi commands in osgi console ATM you will find
issues in there (import). I guess this is just for testing. If you want to
patch the jar use the patches folder.

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Sun, Apr 17, 2016 at 11:09 PM, Chamila Wijayarathna 
wrote:

> Hi all,
>
> So myself and Malithi dig this issue little bit and observed following.
>
> As I mentioned earlier by default we had opensaml2.6.4wasov2.jar in
> plugins directory and I removed it. But there were an entry in
> /repository/components/default/configuration/org.eclipse.equinox.simpleconfigurator/
> bundles.info file corresponding to that jar file as following.
>
> opensaml,2.6.4.wso2v2,../plugins/opensaml_2.6.4.wso2v2.jar,4,true
>
> Until this entry is there in bundle.info, server is not picking up 
> opensaml_2.6.4.wso2v2.jar
> that I am putting into dropins.
>
> Then I deleted this entry in bundle.info file, and restarted the server.
> Now its picking the v2 jar file in dropins and also in bundle.info file,
> I observed following new entry.
>
> opensaml,2.6.4.wso2v2,../dropins/opensaml_2.6.4.wso2v2.jar,4,true
>
> So what I assumed is, at startup, server is writing an entry at
> bundle.info for every jar in dropins, but since there were the previous
> entry which was also for same jar 'opensaml,2.6.4.wso2v2' it failed to
> write new entry for the jar in the dropins.
>
> Any way these are only observations and If anyone can explain the theory
> behind this, that would be very helpful.
>
> Thanks!
>
> On Sun, Apr 17, 2016 at 10:23 PM, Malithi Edirisinghe 
> wrote:
>
>> Hi Chamila,
>>
>> We have specified a version range which is [2.6.0,3.0.0). Both v1 and v2
>> versions get included for this range. Since we have not exactly specified
>> that a particular bundle should pick only v2 version, the bundle could be
>> wired to either v1 or v2 at runtime as per the availability.
>>
>> Thanks,
>> Malithi.
>>
>> On Sun, Apr 17, 2016 at 9:59 PM, Thusitha Thilina Dayaratne <
>> thusit...@wso2.com> wrote:
>>
>>> Hi Chamila,
>>>
>>> Did you export and import the correct versions ?
>>>
>>> Thanks
>>> Thusitha
>>>
>>> On Sat, Apr 16, 2016 at 1:11 PM, Chamila Wijayarathna 
>>> wrote:
>>>
 Hi all,

 IS-5.2.0-Beta uses opensaml2.6.4wasov2. I extracted a pack and
 deleted opensaml2.6.4wasov2.jar from its repository/components/plugins
 folder and then copied opensaml2.6.4wasov1.jar into
 repository/components/dropins folder. Here it worked properly where IS got
 started without any issue and I could reproduced an issue which was there
 in v1 but fixed in v2.

 Then I copied opensaml2.6.4wasov2.jar into
 repository/components/dropins folder and restarted IS again. But now also I
 could reproduced the earlier mentioned error which implies that IS is still
 picking v1 not v2. According to my understanding about OSGi, here IS should
 pick v2 instead of v1.

 Am I doing anything wrong here. What could be the reason for this issue?

 Thank You!

 --
 *Chamila Dilshan Wijayarathna,*
 Software Engineer
 Mobile:(+94)788193620
 WSO2 Inc., http://wso2.com/

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


>>>
>>>
>>> --
>>> Thusitha Dayaratne
>>> Software Engineer
>>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>>
>>> Mobile  +94712756809
>>> Blog  alokayasoya.blogspot.com
>>> Abouthttp://about.me/thusithathilina
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Malithi Edirisinghe*
>> Senior Software Engineer
>> WSO2 Inc.
>>
>> Mobile : +94 (0) 718176807
>> malit...@wso2.com
>>
>
>
>
> --
> *Chamila Dilshan Wijayarathna,*
> Software Engineer
> Mobile:(+94)788193620
> WSO2 Inc., http://wso2.com/
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Secure vault for C5 ?

2016-04-17 Thread Niranjan Karunanandham
Hi Thilina,

On Wed, Mar 30, 2016 at 12:19 PM, Thilina Piyasundara 
wrote:

> Yes we can't use C4 approach.
> We try to do it in docker environments but somehow we need to send the
> password-tmp in to the dokcer (via puppet or environment variables).
>
> If we us docker volumes or if we store the password-tmp in the image there
> is a possibility that anyone can get that root/main password if they have
> access to the containers. Isn't it ?
>
You can write your own implement for this by writing a new Secret Callback
Handler class as mentioned in [1] [2].


>
> Thanks and regards,
>
> Thilina Piyasundara
> Systems Engineer
> ​
> ​
> Blog: thilina.piyasundara.org
> Linkedin: linkedin.com/in/thilinapiyasundara
>
> WSO2, Inc.
> ​
> ​ 
> lean . enterprise . middleware
> https://cloud.wso2.com
>
> On Wed, Mar 30, 2016 at 12:12 PM, Afkham Azeez  wrote:
>
>> In the container world, the sec vault files will get packed into the
>> containers, and if there are changes to those files, you will need to
>> create a new version of the container image. This is true for the rest of
>> the configuration files as well. This goes with the concept of immutable
>> servers.
>>
>> Azeez
>>
>> On Wed, Mar 30, 2016 at 11:54 AM, Sameera Jayasoma 
>> wrote:
>>
>>> I believe we cannot apply the same thing we had in C4. We have to think
>>> about how we can apply this for containers as well. Lets have a quick chat
>>> on this.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> On Wed, Mar 30, 2016 at 11:51 AM, Hasitha Aravinda 
>>> wrote:
>>>
 I think we have to target this for Hamming platform ? Because we have
 some configuration files like (*-datasource.xml) with passwords.

 Apart from securing passwords in configuration files, I think we will
 need secure vault support for runtime as well. In products like GW, ESB and
 BPS do secure services invocations, (i.e BasicAuth) and we will need a
 central place to store encrypted credentials.

 Thanks,
 Hasitha.

 On Wed, Mar 30, 2016 at 11:33 AM, Afkham Azeez  wrote:

> Simply porting the existing sec vault to work with C5 should be
> sufficient.
>
> On Wed, Mar 30, 2016 at 11:03 AM, Hasitha Aravinda 
> wrote:
>
>> Hi team,
>>
>> How are we going to use $Subject in C5. Can we use existing secure
>> vault implementation for this.
>>
>> Thanks,
>> Hasitha.
>>
>> --
>> --
>> Hasitha Aravinda,
>> Senior Software Engineer,
>> WSO2 Inc.
>> Email: hasi...@wso2.com
>> Mobile : +94 718 210 200
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



 --
 --
 Hasitha Aravinda,
 Senior Software Engineer,
 WSO2 Inc.
 Email: hasi...@wso2.com
 Mobile : +94 718 210 200

>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma,
>>> Software Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://blog.sameera.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>> ___
>> 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
>
>
[1] -
https://docs.wso2.com/display/Carbon420/Carbon+Secure+Vault+Implementation#CarbonSecureVaultImplementation-CreatecustomSecureVaultconfiguration
[2] -
http://xacmlinfo.org/2012/08/12/secure-plain-text-passwords-in-wso2-carbon-configuration-files

Regards,
Nira

-- 

*Niranjan Karunanandham*
Senior Software Engineer 

Re: [Dev] Clarification about OSGi Bundle Picking

2016-04-17 Thread Chamila Wijayarathna
Hi all,

So myself and Malithi dig this issue little bit and observed following.

As I mentioned earlier by default we had opensaml2.6.4wasov2.jar in plugins
directory and I removed it. But there were an entry in
/repository/components/default/configuration/org.eclipse.equinox.simpleconfigurator/
bundles.info file corresponding to that jar file as following.

opensaml,2.6.4.wso2v2,../plugins/opensaml_2.6.4.wso2v2.jar,4,true

Until this entry is there in bundle.info, server is not picking up
opensaml_2.6.4.wso2v2.jar
that I am putting into dropins.

Then I deleted this entry in bundle.info file, and restarted the server.
Now its picking the v2 jar file in dropins and also in bundle.info file, I
observed following new entry.

opensaml,2.6.4.wso2v2,../dropins/opensaml_2.6.4.wso2v2.jar,4,true

So what I assumed is, at startup, server is writing an entry at bundle.info
for every jar in dropins, but since there were the previous entry which was
also for same jar 'opensaml,2.6.4.wso2v2' it failed to write new entry for
the jar in the dropins.

Any way these are only observations and If anyone can explain the theory
behind this, that would be very helpful.

Thanks!

On Sun, Apr 17, 2016 at 10:23 PM, Malithi Edirisinghe 
wrote:

> Hi Chamila,
>
> We have specified a version range which is [2.6.0,3.0.0). Both v1 and v2
> versions get included for this range. Since we have not exactly specified
> that a particular bundle should pick only v2 version, the bundle could be
> wired to either v1 or v2 at runtime as per the availability.
>
> Thanks,
> Malithi.
>
> On Sun, Apr 17, 2016 at 9:59 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Chamila,
>>
>> Did you export and import the correct versions ?
>>
>> Thanks
>> Thusitha
>>
>> On Sat, Apr 16, 2016 at 1:11 PM, Chamila Wijayarathna 
>> wrote:
>>
>>> Hi all,
>>>
>>> IS-5.2.0-Beta uses opensaml2.6.4wasov2. I extracted a pack and
>>> deleted opensaml2.6.4wasov2.jar from its repository/components/plugins
>>> folder and then copied opensaml2.6.4wasov1.jar into
>>> repository/components/dropins folder. Here it worked properly where IS got
>>> started without any issue and I could reproduced an issue which was there
>>> in v1 but fixed in v2.
>>>
>>> Then I copied opensaml2.6.4wasov2.jar into repository/components/dropins
>>> folder and restarted IS again. But now also I could reproduced the earlier
>>> mentioned error which implies that IS is still picking v1 not v2. According
>>> to my understanding about OSGi, here IS should pick v2 instead of v1.
>>>
>>> Am I doing anything wrong here. What could be the reason for this issue?
>>>
>>> Thank You!
>>>
>>> --
>>> *Chamila Dilshan Wijayarathna,*
>>> Software Engineer
>>> Mobile:(+94)788193620
>>> WSO2 Inc., http://wso2.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thusitha Dayaratne
>> Software Engineer
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Malithi Edirisinghe*
> Senior Software Engineer
> WSO2 Inc.
>
> Mobile : +94 (0) 718176807
> malit...@wso2.com
>



-- 
*Chamila Dilshan Wijayarathna,*
Software Engineer
Mobile:(+94)788193620
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Cannot generate P2 metadata: P2 publisher return code was 13

2016-04-17 Thread Damith Wickramasinghe
Hi Mohan,

Maven version is 3.0.5. and java is 1.7 .Following is the complete trace i
got.

 Command line:
/bin/sh -c cd
/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen
&& /usr/lib/jvm/java-7-oracle/jre/bin/java -jar
/home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
-nosplash -application org.eclipse.equinox.p2.director -metadataRepository
file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/p2-repo
-artifactRepository
file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/p2-repo
-installIU carbon.product.id -profileProperties
org.eclipse.update.install.features=true -profile worker -bundlepool
file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components
-shared
file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components/p2
-destination
file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components/worker
-p2.os linux -p2.ws gtk -p2.arch x86 -roaming
Installing carbon.product.id 4.4.3.
Installation failed.
One or more certificates rejected. Cannot proceed with installation.
Application failed, log file location:
/home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1460895093502.log

[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 CEP - Parent . SUCCESS [0.972s]
[INFO] WSO2 CEP - Style Parent ... SUCCESS [0.040s]
[INFO] WSO2 CEP - Styles . SUCCESS [1.216s]
[INFO] WSO2 Stratos CEP - Styles . SUCCESS [0.185s]
[INFO] WSO2 CEP - Samples Parent . SUCCESS [0.023s]
[INFO] WSO2 CEP - Samples Producers .. SUCCESS [0.046s]
[INFO] WSO2 CEP - Producer - WSO2 Event Client ... SUCCESS [8.591s]
[INFO] WSO2 CEP - Publisher - HTTP Client  SUCCESS [0.336s]
[INFO] WSO2 CEP - Publisher - JMS Client . SUCCESS [2.722s]
[INFO] WSO2 CEP - Publisher - MQTT Client  SUCCESS [0.171s]
[INFO] WSO2 CEP - Publisher - Kafka Client ... SUCCESS [11.891s]
[INFO] WSO2 CEP - Publisher - SOAP Client  SUCCESS [0.551s]
[INFO] WSO2 CEP - Producer - Websocket Publisher . SUCCESS [4.295s]
[INFO] WSO2 CEP - Producer - Performance Test  SUCCESS [0.475s]
[INFO] WSO2 CEP - Publisher - HTTP Performance Client  SUCCESS [0.166s]
[INFO] WSO2 CEP - Publisher - Kafka Producer . SUCCESS [0.174s]
[INFO] WSO2 CEP - Publisher - JMS Performance Client . SUCCESS [0.150s]
[INFO] WSO2 CEP - Sample Consumers ... SUCCESS [0.035s]
[INFO] WSO2 CEP - Consumer - WSO2 Event Server ... SUCCESS [1.061s]
[INFO] WSO2 CEP - Consumer - JMS Consumer  SUCCESS [0.145s]
[INFO] WSO2 CEP - Consumer - MQTT Consumer ... SUCCESS [0.103s]
[INFO] WSO2 CEP - Consumer - Axis2 Log Service ... SUCCESS [0.090s]
[INFO] WSO2 CEP - Consumer - Generic Log Service . SUCCESS [1.271s]
[INFO] WSO2 CEP - Consumer - Dashboard Service ... SUCCESS [0.117s]
[INFO] WSO2 CEP - Consumer - Websocket Consumer .. SUCCESS [0.294s]
[INFO] WSO2 CEP - Consumer - WSO2 Event Server ... SUCCESS [0.788s]
[INFO] WSO2 CEP - Consumer - HTTP Performance Service  SUCCESS [0.146s]
[INFO] WSO2 CEP - Consumer - Kafka Consumer .. SUCCESS [0.143s]
[INFO] WSO2 CEP - Consumer - JMS Performance Consumer  SUCCESS [0.108s]
[INFO] Siddhi Extension - Geo Event Fuser  SUCCESS [0.679s]
[INFO] Siddhi Extension - Geo Event Notifier . SUCCESS [0.261s]
[INFO] WSO2 CEP - Feature Parent . SUCCESS [0.013s]
[INFO] WSO2 CEP - Features ... SUCCESS [0.014s]
[INFO] WSO2 CEP - Styles Features  SUCCESS [0.290s]
[INFO] WSO2 Stratos CEP - Features ... SUCCESS [0.014s]
[INFO] WSO2 Stratos CEP - Styles Features  SUCCESS [0.058s]
[INFO] WSO2 Stratos CEP - Dashboard UI ... SUCCESS [7.802s]
[INFO] WSO2 Stratos CEP - Dashboard UI Features .. SUCCESS [1.707s]
[INFO] WSO2 CEP - P2 Profile Generation .. FAILURE
[2:24.889s]
[INFO] WSO2 Stratos CEP - Login User Interface ... SKIPPED
[INFO] WSO2 CEP - Storm Dependencies Jar . SKIPPED
[INFO] WSO2 CEP - Distribution ... SKIPPED
[INFO] WSO2 CEP - Integration Tests .. SKIPPED
[INFO] WSO2 CEP - Integration Admin Client Module  SKIPPED
[INFO] CEP Integration Test UI Pages 

Re: [Dev] Clarification about OSGi Bundle Picking

2016-04-17 Thread Malithi Edirisinghe
Hi Chamila,

We have specified a version range which is [2.6.0,3.0.0). Both v1 and v2
versions get included for this range. Since we have not exactly specified
that a particular bundle should pick only v2 version, the bundle could be
wired to either v1 or v2 at runtime as per the availability.

Thanks,
Malithi.

On Sun, Apr 17, 2016 at 9:59 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Chamila,
>
> Did you export and import the correct versions ?
>
> Thanks
> Thusitha
>
> On Sat, Apr 16, 2016 at 1:11 PM, Chamila Wijayarathna 
> wrote:
>
>> Hi all,
>>
>> IS-5.2.0-Beta uses opensaml2.6.4wasov2. I extracted a pack and
>> deleted opensaml2.6.4wasov2.jar from its repository/components/plugins
>> folder and then copied opensaml2.6.4wasov1.jar into
>> repository/components/dropins folder. Here it worked properly where IS got
>> started without any issue and I could reproduced an issue which was there
>> in v1 but fixed in v2.
>>
>> Then I copied opensaml2.6.4wasov2.jar into repository/components/dropins
>> folder and restarted IS again. But now also I could reproduced the earlier
>> mentioned error which implies that IS is still picking v1 not v2. According
>> to my understanding about OSGi, here IS should pick v2 instead of v1.
>>
>> Am I doing anything wrong here. What could be the reason for this issue?
>>
>> Thank You!
>>
>> --
>> *Chamila Dilshan Wijayarathna,*
>> Software Engineer
>> Mobile:(+94)788193620
>> WSO2 Inc., http://wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Malithi Edirisinghe*
Senior Software Engineer
WSO2 Inc.

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


Re: [Dev] Clarification about OSGi Bundle Picking

2016-04-17 Thread Thusitha Thilina Dayaratne
Hi Chamila,

Did you export and import the correct versions ?

Thanks
Thusitha

On Sat, Apr 16, 2016 at 1:11 PM, Chamila Wijayarathna 
wrote:

> Hi all,
>
> IS-5.2.0-Beta uses opensaml2.6.4wasov2. I extracted a pack and
> deleted opensaml2.6.4wasov2.jar from its repository/components/plugins
> folder and then copied opensaml2.6.4wasov1.jar into
> repository/components/dropins folder. Here it worked properly where IS got
> started without any issue and I could reproduced an issue which was there
> in v1 but fixed in v2.
>
> Then I copied opensaml2.6.4wasov2.jar into repository/components/dropins
> folder and restarted IS again. But now also I could reproduced the earlier
> mentioned error which implies that IS is still picking v1 not v2. According
> to my understanding about OSGi, here IS should pick v2 instead of v1.
>
> Am I doing anything wrong here. What could be the reason for this issue?
>
> Thank You!
>
> --
> *Chamila Dilshan Wijayarathna,*
> Software Engineer
> Mobile:(+94)788193620
> WSO2 Inc., http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thusitha Dayaratne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Clarification about OSGi Bundle Picking

2016-04-17 Thread Danushka Fernando
To make it pick v2 you need to import v2 from the bundle using it.
Otherwise osgi will pick the first available version AFAIK.

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Sun, Apr 17, 2016 at 1:41 AM, Chamila Wijayarathna 
wrote:

> Hi all,
>
> IS-5.2.0-Beta uses opensaml2.6.4wasov2. I extracted a pack and
> deleted opensaml2.6.4wasov2.jar from its repository/components/plugins
> folder and then copied opensaml2.6.4wasov1.jar into
> repository/components/dropins folder. Here it worked properly where IS got
> started without any issue and I could reproduced an issue which was there
> in v1 but fixed in v2.
>
> Then I copied opensaml2.6.4wasov2.jar into repository/components/dropins
> folder and restarted IS again. But now also I could reproduced the earlier
> mentioned error which implies that IS is still picking v1 not v2. According
> to my understanding about OSGi, here IS should pick v2 instead of v1.
>
> Am I doing anything wrong here. What could be the reason for this issue?
>
> Thank You!
>
> --
> *Chamila Dilshan Wijayarathna,*
> Software Engineer
> Mobile:(+94)788193620
> WSO2 Inc., http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [BPS] Any idea to differentiate BPMN form property we should generate as text field and a textarea?

2016-04-17 Thread Firzhan Naqash
Hi Amalka,

Well I can think of two ways to achieve this.


   1. Check for the size of the string data and if it exceeds more than a
   predefined size, then you can define the text field of that property as
   text area.
   2. Or you can define a custom property for the fields that you want to
   define as text area. If the property is a custom property type then you can
   define the text area [1]

[1]
http://www.jorambarrez.be/blog/2013/03/13/creating-a-new-form-property-in-activiti/


Regards,
Firzhan


-- 
*Firzhan Naqash*
Senior Software Engineer - Integration Platform Team
WSO2 Inc. http://wso2.com

email: firz...@wso2.com
mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
blog: http://firzhanblogger.blogspot.com/
  *
*twitter: https://twitter.com/firzhan007  |
linked-in: **https://www.linkedin.com/in/firzhan
*

On Sun, Apr 17, 2016 at 7:58 AM, Amalka Subasinghe  wrote:

> Hi,
>
> When implementing BPMN User Task I want to generate a form (from the form
> properties I define in User Task) with a *Textarea*.
>
> When going through the BPMN explorer code I found that, if the form
> property type is string then it generates the form as text field, if it is
> enum then it generates as list box, etc... via a JavaScript code.
> How can I generate a Textarea using the form property we defined in BPMN ?
>
> As I know Activiti supports string, long, boolean, enum and date property
> types only.
> Any idea to differentiate a property defined in form section in BPMN as a
> textarea?
>
> Thanks
> Amalka
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Cannot generate P2 metadata: P2 publisher return code was 13

2016-04-17 Thread Mohanadarshan Vivekanandalingam
Hi Damith,

I can see few mail threads related to this.. Seems like a maven version
issue.. What is the maven version you are using here ? and can you add the
complete error log please ?

Thanks,
Mohan


On Sun, Apr 17, 2016 at 5:52 PM, Damith Wickramasinghe 
wrote:

> Hi,
>
> I'm trying to build product CEP in a clean m2 repo. I have successfully
> built siddhi,carbon-event-processing,carbon-analytics-common and
> carbon-dashboards. But When building product CEP I'm getting below
> exception. Any idea what may be the cause of it ?
>
> [ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5.4:materialize-product
> (creating-worker-profile) on project wso2cep-profile-gen: Cannot generate
> P2 metadata: P2 publisher return code was 13
>
> Thanks,
> Damith.
>
> --
> Software Engineer
> WSO2 Inc.; http://wso2.com
> 
> lean.enterprise.middleware
>
> mobile: *+94728671315 <%2B94728671315>*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*V. Mohanadarshan*
*Senior Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [BPS] Any idea to differentiate BPMN form property we should generate as text field and a textarea?

2016-04-17 Thread Amalka Subasinghe
Hi,

When implementing BPMN User Task I want to generate a form (from the form
properties I define in User Task) with a *Textarea*.

When going through the BPMN explorer code I found that, if the form
property type is string then it generates the form as text field, if it is
enum then it generates as list box, etc... via a JavaScript code.
How can I generate a Textarea using the form property we defined in BPMN ?

As I know Activiti supports string, long, boolean, enum and date property
types only.
Any idea to differentiate a property defined in form section in BPMN as a
textarea?

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


[Dev] Cannot generate P2 metadata: P2 publisher return code was 13

2016-04-17 Thread Damith Wickramasinghe
Hi,

I'm trying to build product CEP in a clean m2 repo. I have successfully
built siddhi,carbon-event-processing,carbon-analytics-common and
carbon-dashboards. But When building product CEP I'm getting below
exception. Any idea what may be the cause of it ?

[ERROR] Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.5.4:materialize-product
(creating-worker-profile) on project wso2cep-profile-gen: Cannot generate
P2 metadata: P2 publisher return code was 13

Thanks,
Damith.

-- 
Software Engineer
WSO2 Inc.; http://wso2.com

lean.enterprise.middleware

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