wso2-emm

WSo2 EMM - App Management Database Bug

可紊 提交于 2019-12-02 05:51:44
问题 Running WSo2 EMM 1.1.0, everything has been working just fine except for one big issue. From the moment I first click on an app in the App Management tab, the WSO2EMM_DB.h2.db file starts to steadily grow as long as the server is running, even with absolutely no changes. Eventually, it gets so big that clicking an app on that tab takes a ridiculously long time to load the list of devices using the app. We're talking 5+ minutes, it becomes completely unusable. I have checked the error logs and

WSO2 signing system service app

£可爱£侵袭症+ 提交于 2019-12-02 05:46:56
I want to setup all my devices as COPE. WSO2 EMM setup is complete and working fine. Only thing is left is to sign the system service application with the firmware key. I am using Google devices only (Android one, Motorola G2). From where I can find the key and password to sign the application. Is there any other alternative way to get the application signed? As per documentation, "Sign the application via the device firmware signing key. If you don’t have access to the firmware signing key, you have to get the system application signed via your device vendor." But I am not able to find the

WSo2 EMM - App Management Database Bug

穿精又带淫゛_ 提交于 2019-12-02 02:24:49
Running WSo2 EMM 1.1.0, everything has been working just fine except for one big issue. From the moment I first click on an app in the App Management tab, the WSO2EMM_DB.h2.db file starts to steadily grow as long as the server is running, even with absolutely no changes. Eventually, it gets so big that clicking an app on that tab takes a ridiculously long time to load the list of devices using the app. We're talking 5+ minutes, it becomes completely unusable. I have checked the error logs and found no errors at all, every time. Restarting the server does nothing to correct the issue. Even if I

Sending Content-Type application/x-www-form-urlencoded WSO2 ESB

北慕城南 提交于 2019-12-01 08:40:49
I have been working in a service chaining that answers me with a Bearer Token using in WSO2 EMM. I made a proxy in ESB and then I passed to a new sequence that makes the next call but this one receives a Content-Type application/x-www-form-urlencoded. I have been looking for some help so that I can find anything interesting. This is my proxy <?xml version="1.0" encoding="UTF-8"?> <proxy name="TokenService" startOnLoad="true" statistics="enable" trace="enable" transports="http https" xmlns="http://ws.apache.org/ns/synapse"> <target> <inSequence> <!--Aggregate incoming responses --> <log level=

wso2-emm app management version bug

∥☆過路亽.° 提交于 2019-11-28 14:09:19
i encounter the bug EMM-686 and i've seen the answer by Nira pointing to the jira and the github, but i don' find how i can apply the fix on my production (downloaded binaries from the website), is there a documentation for that ? I don't understand why the binaries on the website don't include an up to date version of wso2-emm is there somewhere where i can found that ? Obvisiously i already tried to apply manually the changes in the 2 files mentioned, and restart the server but no luck. This is how you apply the update they included in the patch attached to EMM-686 : Open an explorer window

wso2-emm app management version bug

假如想象 提交于 2019-11-27 08:34:09
问题 i encounter the bug EMM-686 and i've seen the answer by Nira pointing to the jira and the github, but i don' find how i can apply the fix on my production (downloaded binaries from the website), is there a documentation for that ? I don't understand why the binaries on the website don't include an up to date version of wso2-emm is there somewhere where i can found that ? Obvisiously i already tried to apply manually the changes in the 2 files mentioned, and restart the server but no luck. 回答1