Any other idea? Anything else I can look into to see why the clientkey uri
is not getting resolved?
On Sun, Jul 6, 2014 at 6:55 PM, Mir Islam mis...@mirislam.com wrote:
Thanks Chan. Still the same 404. So the url is not resolving to a service
that client is looking for. Below from access_log
192.168.10.102 - - [06/Jul/2014:18:50:51 -0700] POST
/emm/api/devices/clientkey HTTP/1.1 *404* - - Mozilla/5.0 (
compatible ), Android
On Sun, Jul 6, 2014 at 5:46 PM, Chan duli...@wso2.com wrote:
Hi Islam,
I have commented on the StackOverflow issue. Also please note that you
can run the EMM server without any configurations and enroll an android
device. As for configurations to host on an IP - please do change the sso
idp config file as well [1]
[1] - https://docs.wso2.com/display/EMM110/General+Server+Configurations
(step 2)
Cheers~
On Mon, Jul 7, 2014 at 4:57 AM, Mir Islam mis...@mirislam.com wrote:
Hi everyone, just started to look into wso2, specifically the emm
server. Got a question regarding installation and registration of device.
If this not the right list, please let me know where I can post. I have
posted on StackOverFlow as well.
http://stackoverflow.com/questions/24600830/wso2-android-agent-getting-404-from-emm
Basically the agent is getting a 404 error when agent is POSTing to
/emm/api/devices/clientkey URL. I am wondering if I have configured
something wrong on server side. I have tried with latest GIT src and built
the agent.
Thanks
Mir
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Chan (Dulitha Wijewantha)
Software Engineer - Mobile Development
WSO2 Inc
Lean.Enterprise.Mobileware
* ~Email duli...@wso2.com duli...@wso2mobile.com*
* ~Mobile +94712112165 %2B94712112165*
* ~Website dulitha.me http://dulitha.me*
* ~Twitter @dulitharw https://twitter.com/dulitharw*
*~Github @dulichan https://github.com/dulichan*
*~SO @chan http://stackoverflow.com/users/813471/chan*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
