mdm

Error when combining scep and mdm payloads - enrollment server did not provision valid identity certificate

ぃ、小莉子 提交于 2019-12-09 06:27:32
问题 I'm working on rolling my own MDM service, and I'm trying to combine the SCEP and MDM payloads as the MDM protocol document from Apple suggests. I created my own SCEP web service in C# .Net and I know that the device can get a valid certificate when I just send the SCEP payload. However when I also include an MDM payload that points to the SCEP payload's UUID via the IdentityCertificateUUID key, I get the following error, " The enrollment server did not provision a valid identity certificate.

Install Apps from unknown sources inside work profile in Android Lollipop 5.0.1

僤鯓⒐⒋嵵緔 提交于 2019-12-08 03:56:41
问题 Question is related to Work Profile in " Android for work " . I have written a sample app that creates a managed work profile and sets itself as the profile owner . I will need to push some enterprise applications through the profile owner . So when i try to install , it says "Install blocked" , Cannot install from unknown sources . If i toggle the button ( Setting->security->Unknown Source ) on and off , settings are not getting reflected in the work profile. Is there a way to install the

Fail to enroll IOS device in WSO2 2.0.1

二次信任 提交于 2019-12-07 21:50:48
问题 Trying to enroll IOS device (IPhone 6s, ios 9.3) in WSO2 but unfortunately failing. I am using registered csr file and Apple MDM certificate. Followed instructions mentioned in document. Failing at step 2 on IOS device after entering Domain, username and password. On UI, below is the error "An unexpected error occured. Please try again." In Logs I see below errors: [2016-05-06 11:54:22,746] ERROR {org.wso2.carbon.device.mgt.ios.util.OAuthUtils} - Error occurred while sending 'Post' request

Wiping data on Android: Device Admin versus Profile Owner

十年热恋 提交于 2019-12-07 19:21:27
问题 Android 5.0 introduces a new concept of Profile Owner. In my understanding Profile Owner is an advanced version of Device Admin (exists in Android since 2.2). Both Device Admin and Profile Owner can wipe data via DevicePolicyManager.wipeData(0) . I would like to know if there is a difference in behaviour of such a call for Device Admin and Profile Owner. I guess for a pure Device Admin it should wipe entire device (factory reset), and for a Profile Owner it should only wipe data for the

How to share data across an organization

故事扮演 提交于 2019-12-07 14:42:44
问题 What are some good ways for an organization to share key data across many deparments and applications? To give an example, let's say there is one primary application and database to manage customer data. There are ten other applications and databases in the organization that read that data and relate it to their own data. Currently this data sharing is done through a mixture of database (DB) links, materialized views, triggers, staging tables, re-keying information, web services, etc. Are

iOS MDM service and MDM agent app

半城伤御伤魂 提交于 2019-12-06 23:40:03
问题 I'm researching about MDM in iOS, and find out information about Apple’s native iOS mobile device management. Once the device is enrolled into a MDM server, server can manage the device by sending commands. I tested on a MDM server and saw that without installing MDM agent app on device, server can still send profiles and apply policies to the device. Could anyone help me to address: Is Apple’s native iOS mobile device management built inside the iOS itself? Can MDM server manage device

iOS MDM Enrollment Profile Request of /profile to sign the certificate using java

我们两清 提交于 2019-12-06 23:34:27
Hello we are trying to create an iOS MDM server using java. I am stuck at the very first point where we have to sign the certificate and send an SCEP. I have first sent the enroll plist file to the ios device. In response to which I receive a HttpServletRequest from the ios device when we click on "Install" from the device. It the uses the URL which contains the profile request url and a request is obtained for the same in java. After reading the request.getInputStream i got to know that the request has two parts within. One is a plist another is the certificate of the device. printing the

iOS 8 MDM: managed app configuration doesn't work

安稳与你 提交于 2019-12-06 10:41:41
问题 In our custom mobile device management (MDM) solution we use managed app configuration: MDM server pushes InstallApplication payload with Configuration dictionary. The app uses [[NSUserDefaults standardUserDefaults] dictionaryForKey:@"com.apple.configuration.managed"]; Everything worked fine. Due to changes in iOS 8.1.3 we resigned the application as it's described here. After that the app can be installed and it launches well on iOS 8.1.3+. But it cannot read the configuration using

Generate a CSR request in java via SCEP

那年仲夏 提交于 2019-12-06 09:39:36
I am trying to send a Certificate Signing Request from an Android device to a server. The server is working properly with iOS devices and follows a SCEP procedure with OpenSSL . So here is my problem : I can send the signed enveloped CSR but the server can't read the enveloped CSR. I have the following error from the server : pki.rb:26:in initialize: Could not parse the PKCS7: header too long (ArgumentError) Related ruby server code : #receive object and put it in object data [...] # Verify Input Data p7sign = OpenSSL::PKCS7.new(data) store = OpenSSL::X509::Store.new p7sign.verify(nil, store,

Google EMM APIs return The caller is not registered as an MDM

折月煮酒 提交于 2019-12-06 08:14:17
I'm now testing the Google EMM Apis and I'm trying to generate a signup url for enrolling an enterprise. scopes = ['https://www.googleapis.com/auth/androidenterprise'] credentials = ServiceAccountCredentials.from_json_keyfile_name( 'my_key.json', scopes) http_auth = credentials.authorize(Http()) API = 'androidenterprise' VERSION = 'v1' SERVICE = discovery.build(API, VERSION, http=http_auth) response = SERVICE.enterprises().generateSignupUrl(callbackUrl='http://www.my_site.com').execute() However, I'm getting as a response a forbidden 403 response code with the following message: "The caller is