[Dev] [IS] WSO2 IS 5.1.0-SNAPSHOT is not starting up

[Akila Ravihansa Perera]

Hi,

While testing out the latest IS pack I noticed the $subject. It hangs after
printing environment properties from CarbonCoreActivator. After debugging
in OSGi console mode I noticed that rampart-core_1.6.1.wso2v15 and
rampart-trust_1.6.1.wso2v15 dependency bundles are in INSTALLED state which
is blocking some of the core identity bundles from going to ACTIVE state.

Running the diagnose OSGi command on ramport-core gave me the following;

reference:file:../plugins/rampart-core_1.6.1.wso2v15.jar [377]
  Package uses conflict: Import-Package: org.apache.ws.security;
version="[1.5.11.wso2v9,2.0.0)"
  Package uses conflict: Import-Package:
org.apache.ws.security.components.crypto; version="[1.5.11.wso2v9,2.0.0)"
  Package uses conflict: Import-Package: org.apache.ws.security.handler;
version="[1.5.11.wso2v9,2.0.0)"
  Package uses conflict: Import-Package: org.apache.ws.security.message;
version="[1.5.11.wso2v9,2.0.0)"
  Package uses conflict: Import-Package:
org.apache.ws.security.message.token; version="[1.5.11.wso2v9,2.0.0)"
  Package uses conflict: Import-Package: org.apache.ws.security.saml;
version="[1.5.11.wso2v9,2.0.0)"
  Package uses conflict: Import-Package: org.apache.ws.security.util;
version="[1.5.11.wso2v9,2.0.0)"


Looks like wss4j dependency version has been upgraded with this commit [1]
to 1.5.11.wso2v11 but rampart v1.6.1-wso2v15 release is still referring to
wss4j 1.5.11.wso2v9 [2].

Appreciate if IS team can look into this.

[1]
https://github.com/wso2/carbon-identity/commit/7f2e8271ed5d3e82606f4be1b991c82a621e
[2] https://github.com/wso2/wso2-rampart/blob/v1.6.1-wso2v15/pom.xml#L558

Thanks.

-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

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

Re: [Dev] [ESB - 4.8.1] Clarification regarding message processor

[Isuru Udana]

Hi Shafreen,

On Sun, Aug 2, 2015 at 10:11 AM, Shafreen Anfar  wrote:

> Hi Tishan,
>
> We haven't tested for each and every status code. But ideally, it should
> retry for most of the non 200 series status codes.
>
AFAIK, by default we are retrying only for connection errors/timeouts etc.
but not for business level faults of the backend. But we have the option to
retry for business level errors also by specifying retry codes, non-retry
codes.

Thanks.

>
> On Fri, Jul 31, 2015 at 2:37 PM, Tishan Dahanayakage 
> wrote:
>
>> Hi,
>>
>> What HTTP status codes will be retried by default when using message
>> processor?
>>
>> Thanks
>> Tishan
>>
>> --
>> Tishan Dahanayakage
>> Software Engineer
>> WSO2, Inc.
>> Mobile:+94 716481328
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, re-transmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>
>
>
> --
> Regards,
> *Shafreen*
> Software Engineer
> WSO2 Inc
> Mobile : 077-556-395-1
>



-- 
*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

Re: [Dev] [ESB - 4.8.1] Clarification regarding message processor

[Shafreen Anfar]

Hi Tishan,

We haven't tested for each and every status code. But ideally, it should
retry for most of the non 200 series status codes.

On Fri, Jul 31, 2015 at 2:37 PM, Tishan Dahanayakage 
wrote:

> Hi,
>
> What HTTP status codes will be retried by default when using message
> processor?
>
> Thanks
> Tishan
>
> --
> Tishan Dahanayakage
> Software Engineer
> WSO2, Inc.
> Mobile:+94 716481328
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, re-transmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>



-- 
Regards,
*Shafreen*
Software Engineer
WSO2 Inc
Mobile : 077-556-395-1
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Stack Overflow Question [WSO2 EMM - WIFI operation not working]

[Zahra Alimadadi]

Hi,

I am testing device management operation, but wifi setting is not working.
The difference between wifi set using emm and defualt is security type
which is WPA PSK and EMM device management set it to WEP. How can I modify
the security type?

More info:

server : windows 7 (wso2 v : 1.1.0),client : galaxy note 10.1 (android),
database : mysql

Here is the link to my question in stackoverflow:

WSO2 EMM - WIFI operation not working
http://stackoverflow.com/q/31766344/3933607?sem=2

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

Re: [Dev] Pre-packaged IS 5.0 server creating invalid XACML

[John Hawkins]

Hmm, Hi Tharindu, thanks for looking at this so quickly !!
I just downloaded it and then bin/wso2server.sh then go to the policy page
and try to create a policy. This fails whether I have done the additional
steps to connect the API-M up to it or not.

It seems to be a validation thing - where is the validation done - on the
server or in the client ? Maybe there are some clues there - perhaps Java
versions or some such? I'm on a  mac too ?

John Hawkins
Director: Solutions Architecture


On Sat, Aug 1, 2015 at 7:16 AM, Tharindu Dharmarathna 
wrote:

> Hi John,
>
> I have setup the Pre-packaged IS  according to the documentaion [1]. I
> couldn't get any issue on creating policy on Identity server.
>
> Can you please send us the steps you are done in order to reproduce this
> issue.
>
> [1] -
> https://docs.wso2.com/display/CLUSTER420/Configuring+the+Pre-Packaged+Identity+Server+5.0.0+with+API+Manager+1.9.0
>
>
> Thanks
> Tharindu
>
>
> On Fri, Jul 31, 2015 at 3:50 PM, John Hawkins  wrote:
>
>> Hi Folks,
>>
>> I've created a JIRA for this [1]. I couldn't see any JIRA that looked
>> like this one but I apologise if it's a dupe.
>>
>> The UI appears unable to create any policies using the wizards. This only
>> happens in the pre-packaged Identity server package when you're trying to
>> connect IS and API-M.
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-3473
>>
>>
>> best regards,
>> John.
>>
>>
>>
>> John Hawkins
>> Director: Solutions Architecture
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Tharindu Dharmarathna*Associate Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091 <%2B94779109091>*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stack Overflow Question - WSO2 EMM - operation not working

[Zahra Alimadadi]

Thanks

On Sat, Aug 1, 2015 at 6:27 PM, Milan Perera  wrote:

> Hi Zahra,
>
>
>> Can I change the notifier typ without unregistering the device?
>>
> ​As I mentioned earlier, notification method is being pushed to the device
> at the time of enrolment. So you have
> to re-register the device.
>
> Regards,​
> --
> Milan Harindu Perera
> Software Engineer
> *WSO2, Inc*
> (+94) 77 309 7088
> lean . enterprise . middleware
> 
>



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

Re: [Dev] Stack Overflow Question - WSO2 EMM - operation not working

[Milan Perera]

Hi Zahra,


> Can I change the notifier typ without unregistering the device?
>
​As I mentioned earlier, notification method is being pushed to the device
at the time of enrolment. So you have
to re-register the device.

Regards,​
-- 
Milan Harindu Perera
Software Engineer
*WSO2, Inc*
(+94) 77 309 7088
lean . enterprise . middleware

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

Re: [Dev] Stack Overflow Question - WSO2 EMM - operation not working

[Zahra Alimadadi]

Hi Milan,

The enrollment was without any issue.

I unregistered the device and set the notifier type to local and registered
again. I test some of the operation and now they work.
Can I change the notifier typ without unregistering the device?

Thanks,

On Sat, Aug 1, 2015 at 5:52 PM, Milan Perera  wrote:

> Hi Zahra,
>
> It seems to me that device is not polling. Were you able to enrol your
> device to the system without any issue?
>
> I set notifier type to be both local and GCM, but nothing happen on device.
>>
> Since notification method is being pushed to the device at the time of
> enrolment, when you change
> the notification type (to GCM or Local), you should have to re-enroll the
> ​device to the system.
> Have you tried that as well?
>
> ​Other thing is do you use ADB (Android Debug Bridge) to debug the Android
> device?
> If so, will you be able to read the debugging messages of the android
> agent and
> check whether if there are any issues being logged there?
>
> Regards,​
>
> Milan Harindu Perera
> Software Engineer
> *WSO2, Inc*
> (+94) 77 309 7088
> lean . enterprise . middleware
> 
>



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

Re: [Dev] Stack Overflow Question - WSO2 EMM - operation not working

[Milan Perera]

Hi Zahra,

It seems to me that device is not polling. Were you able to enrol your
device to the system without any issue?

I set notifier type to be both local and GCM, but nothing happen on device.
>
Since notification method is being pushed to the device at the time of
enrolment, when you change
the notification type (to GCM or Local), you should have to re-enroll the
​device to the system.
Have you tried that as well?

​Other thing is do you use ADB (Android Debug Bridge) to debug the Android
device?
If so, will you be able to read the debugging messages of the android agent
and
check whether if there are any issues being logged there?

Regards,​

Milan Harindu Perera
Software Engineer
*WSO2, Inc*
(+94) 77 309 7088
lean . enterprise . middleware

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

Re: [Dev] Issue when using secure vault with ESB 4.9.0

[Jagath Sisirakumara Ariyarathne]

Hi Niranjan,

Both issues were solved with your suggestions. Thanks a lot for the prompt
reply.

Thanks.

On Thu, Jul 30, 2015 at 11:31 PM, Niranjan Karunanandham 
wrote:

> Hi Jagath,
>
> On Thu, Jul 30, 2015 at 9:03 PM, Jagath Sisirakumara Ariyarathne <
> jaga...@wso2.com> wrote:
>
>> Hi Niranjan,
>>
>> I followed below steps to secure passwords in axis2.xml keystores with
>> ESB 4.9.0-BETA-SNAPSHOT built with cipher tool 1.0.0-wso2v3.
>>
>> 1. Added axis2 configuration entries to cipher-tool.properties file.
>>
>>
>> Axis2.Https.Listener.TrustStore.Password=repository/conf/axis2/axis2.xml//axisconfig/transportReceiver[@name='https']/parameter[@name='truststore']/TrustStore/Password,false
>>
>> Axis2.Https.Listener.KeyStore.Password=repository/conf/axis2/axis2.xml//axisconfig/transportReceiver[@name='https']/parameter[@name='keystore']/KeyStore/Password,false
>>
>> 2. Executed cipher text configuration command ./ciphertool.sh
>> -Dconfigure. It updated axis2.xml with given aliases.
>>
>> 
>>
>> 
>>
>>
>> repository/resources/security/client-truststore.jks
>>
>> JKS
>>
>> > svns:secretAlias="Axis2.Https.Listener.TrustStore.Password">password
>>
>> 
>> 
>>
>> 3. But encrypted keys updated in cipher-text.properties file only for
>> existing entries. Not for the new axis2 entries configured above.
>>
> You need to add the alias followed by the password in square brackets into
> the cipher-text.properties file and then run ./ciphertool.sh -Dconfigure.
> Only then it will encrypt the password entered inside square brackets in
> the cipher-text.properties.
>
>
>
>> 4. Also ESB gives error "java.io.IOException: Keystore was tampered with,
>> or password was incorrect" at startup.
>>
>> Is there any missing in my procedure?
>>
>> Also I experienced below error when running integration tests in ESB
>> 4.9.0 with kernel 4.4.1 RC1. It did not occur with kernel 4.4.0. Would it
>> be due to any missing information in catalina-server.xml?
>>
>> INFO
>>  [org.wso2.carbon.integration.common.extensions.utils.ServerLogReader] -
>> org.w3c.dom.DOMException: NOT_FOUND_ERR: An attempt is made to reference a
>> node in a context where it does not exist.
>> INFO
>>  [org.wso2.carbon.integration.common.extensions.utils.ServerLogReader] - at
>> org.apache.xerces.dom.AttributeMap.internalRemoveNamedItem(Unknown Source)
>> INFO
>>  [org.wso2.carbon.integration.common.extensions.utils.ServerLogReader] - at
>> org.apache.xerces.dom.AttributeMap.removeNamedItem(Unknown Source)
>> INFO
>>  [org.wso2.carbon.integration.common.extensions.utils.ServerLogReader] - at
>> org.wso2.carbon.tomcat.internal.ServerManager.init(ServerManager.java:85)
>>
>>
>> In the Carbon 4.2.0, the certificate in the Primary Keystore (in
> carbon.xml) was used as the SSL certificate, but in Carbon 4.4.0 this has
> been moved to the catalina-server.xml. Therefore you will need to encrypt
> the password of the JKS in catalina-server.xml also when you run the
> cipher-tool. In-order to do that you need to add the following values [1]
> and [2] into cipher-tool.properties and cipher-text.properties of the
> product respectively. This issue is happening since after running the
> ciphertool, this value is not encrypted as the keys are not added to
> cipher-text.properties and cipher-tool.properties. Can you please add a
> JIRA in kernel this, .i.e., issue after running the ciphertool without
> encrypting the Keystore password in catalina-server.xml. This is not a
> blocker for you since the recommended approach when you run the ciphertool
> is to encrypt the JKS password in catalina-server.xml
>
>
> [1] -
> https://github.com/wso2/cipher-tool/blob/master/features/org.wso2.ciphertool.feature/resources/conf/cipher-tool.properties#L12
> [2] -
> https://github.com/wso2/cipher-tool/blob/master/features/org.wso2.ciphertool.feature/resources/conf/cipher-text.properties#L9
>
>
>
>> Thanks.
>> --
>> Jagath Ariyarathne
>> Technical Lead
>> WSO2 Inc.  http://wso2.com/
>> Email: jaga...@wso2.com
>> Mob  : +94 77 386 7048
>>
>>
> Regards,
> Nira
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>



-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Stack Overflow Question - WSO2 EMM - operation not working

[Zahra Alimadadi]

Hi,

I want to test device management operation on my registered device, I set
notifier type to be both local and GCM, but nothing happen on device. also
I change notifier type to be just local and check operation again, nothing
this time. Also application list, device battery, ram and location not
shown in this  page How can I fix these
issues.

More info:

server : windows 7 (wso2 v : 1.1.0),client : galaxy note 10.1 (android),
database : mysql

Here is the link to my question in stackoverflow:
WSO2 EMM - operation not working
http://stackoverflow.com/q/31760207/3933607?sem=2

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

Re: [Dev] WSO2 Committers += CD Athuraliya

[Ashen Weerathunga]

Congratulations!!! :)

On Sat, Aug 1, 2015 at 6:21 AM, Sinnathamby Mahesan 
wrote:

> Congratulations CD!
>
> Best Wishes
> Mahesan
>
> On 31 July 2015 at 14:04, Nirmal Fernando  wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce *CD Athuraliya* as a *WSO2 Committer*. He
>> has been a key contributor to the *WSO2 Machine Learner *Product and in
>> recognition of his excellent work, he had been voted as a WSO2 Committer.
>>
>> Congratulations CD and keep up the good work!
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> ~~
> Sinnathamby Mahesan
>
>
>
> ~~
> ~~
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ashen Weerathunga*
Software Engineer - Intern
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

Email: as...@wso2.com
Mobile: +94 716042995 <94716042995>
LinkedIn:
*http://lk.linkedin.com/in/ashenweerathunga
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] How to define the streams with same stream name with different versions for data publishing (Versioning streams)???

[Isuru Wijesinghe]

Hi All,

I already designed a front end component which provides the configuration
to select set of attributes which belongs to the both process and task
instances to create two steams for publishing  the attributes as events to
DAS. (One stream for task instance attributes and the other is for process
instance attributes)

Here it has predefined set of check boxes with attribute names and user can
able to select attributes separately for both task and process instances.
Once a user selected some attributes to initialize the two streams those
are automatically disabled from the UI and stored in the configuration
registry as properties. From the back-end side read those properties and
create streams to publish data as events to DAS.

In this case according to the selection of attributes by the user the
stream definitions are different because the user can select additional
attributes in later publishes(through the selection of check-boxes).

According to the above scenario how can I define the stream with the
different version and with the same stream name (In this case the generated
streamId will be different from the earlier one.)???
Any help will be appreciated.

(I already implemented the back-end component to publish the predefined set
of attributes through both two types of streams).

-- 
Isuru Wijesinghe
*Software Engineer*
Mobile: 0710933706
isur...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESBJAVA-2497: HTTP Endpoint GET with URL POST FIX not behave as expected or need better documentation

[Senduran Balasubramaniyam]

Hi Dushan,

I reproduced the issue[1]. Since I am trying with ESB 490 beta pre pack. I
had to modify the uri-template as
"*legacy-encoding:*http://
{uri.var.host}:{uri.var.port}/{uri.var.context1}/services/{uri.var.context2}{uri.var.postfix}"

The uri.var.postfix is replace with api's uri-template, in this sample the
uri-template starts with slash, so the uri.var.postfix also starts with a
slash. so that the slash between ur.var.context2 and uri.var.postfix is
redundant in this case.
Is this behavior incorrect  or am I missing something ? Also I couldn't
find any documentation specific to this.

Could you please suggest me a way to proceed this issue further.

[1]https://wso2.org/jira/browse/ESBJAVA-2497

Thanks
Senduran

-- 
*Senduran *
Software Engineer,
WSO2, Inc.;  http://wso2.com/ 
Mobile: +94 77 952 6548
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev