logo
down
shadow

wso2 emm add new device operation


wso2 emm add new device operation

By : Michael Janke
Date : November 15 2020, 06:54 AM
this will help To which platform you need to add operations? Its not straight forward but should be able to add by adding some records in to the DB as well as the source code. Check the feature table in DB and handle the feature code properly in the source code.
code :


Share : facebook icon twitter icon
WSO2 EMM - operation not working

WSO2 EMM - operation not working


By : kdawg493
Date : March 29 2020, 07:55 AM
I hope this helps . 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, please check the debugging messages of the android agent to check whether if there are any issues being logged there.
SearhEntry operation in LDAP wso2 esb

SearhEntry operation in LDAP wso2 esb


By : Gökhan Soğancı
Date : March 29 2020, 07:55 AM
Any of those help I got it working by setting below parameters for anonymous connection to ldap.
code :
"securityPrincipal":"",
   "securityCredentials":"",
   "secureConnection":"true",
   "disableSSLCertificateChecking":"true",
Not able to access WSO2 IoTS Device Management Console in wso2-iot-3.3.0 when logged in 'admin'

Not able to access WSO2 IoTS Device Management Console in wso2-iot-3.3.0 when logged in 'admin'


By : user1609456
Date : March 29 2020, 07:55 AM
hop of those help? You need to check Java version, All wso2 Products have issues with the latest version of Java, if you are using java version "1.8.0_151" then that's a problem, try using java version "1.8.0_144". If you cannot change java version then you need to change the compression parameter to off in catalina-server.xml file
Authentication Error when Trying to Log into WSO2 IoT Server - Device Management Console in wso2-iot-3.3.0

Authentication Error when Trying to Log into WSO2 IoT Server - Device Management Console in wso2-iot-3.3.0


By : ToughMan
Date : March 29 2020, 07:55 AM
wish help you to fix your issue This is related to the issue mentioned in the github issue mentioned below and it seems, it is already fixed in latest master.
As a quick workaround you could try to modify the startup script files (bat files in this case) and add the changes mentioned in the above git issue.
code :
FOR %%D in ("%CARBON_HOME%\wso2\lib\commons-lang*.jar") DO set CARBON_CLASSPATH=!CARBON_CLASSPATH!;".\wso2\lib\%%~nD%%~xD"
WSO2 EMM: Delete device from Device Management

WSO2 EMM: Delete device from Device Management


By : Drishya Chhetri
Date : March 29 2020, 07:55 AM
I wish this help you We cann't replace the old device object with the new one because it might cause issues in shared-device scenarios (mostly COPE devices) where several users have access to the same device. So current user of the device must be able to login to EMM without removing the other owners' data. However I think this behavior must be changed to detect the Active device instance / owner from the same device instances and show it instead of showing multiple instances of the same device.
You can not delete the device from the EMM server by removing the registration from the client side. Only way to remove it would be manually removing the database table entry in the "devices" table of EMM database.
shadow
Privacy Policy - Terms - Contact Us © ourworld-yourmove.org