421 results found

1. Auto-admin password complexity settings

   For the auto-admin password generation done by SimpleMDM, it'd be preferable to be able to manage the level of password complexity when the password is generated. Environments can have different password policy rules that all accounts, including MDM generated, need to abide by. The Dude abides.

   Password storage apps like 1Password and Keeper offer, at minimum, password length, use of numbers, and use of special characters. See attached.

   •  

   •  

   9 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Nested Custom Attributes

   Description: It would be extremely useful to have the ability to nest custom attributes in SimpleMDM. This feature would allow administrators to create custom attributes that reference or depend on other custom attributes, enabling dynamic and interconnected data management.

   Use Case: For instance, suppose an organization has a custom attribute called "munkimanifestdepartement" that is a dropdown value in the DEP (Device Enrollment Program) welcome screen. The organization also wants to create another custom attribute called "munkimanifest" that includes the department value selected in "munkimanifestdepartement" along with additional static text. By nesting the custom attribute "munkimanifestdepartement" within the "munkimanifest" attribute, the organization can automatically generate the munki manifest value based on the selected department.

   Benefits:
   1. Automation: Nesting custom attributes would automate the process of generating complex values by dynamically incorporating data from other attributes.
   2. Data Consistency: By linking attributes together, administrators can ensure that related data remains consistent and up to date.
   3. Simplified Management: Instead of manually updating multiple attributes, nested custom attributes would allow for easier management and maintenance of interconnected data.

   Implementation: The addition of a feature to nest custom attributes in SimpleMDM could be achieved by introducing a syntax or placeholder system that references other custom attributes within the attribute value. Administrators could use placeholders or variables to dynamically include the value of other attributes when defining the value of a custom attribute.

   Overall, the ability to nest custom attributes in SimpleMDM would enhance data management capabilities by enabling automation, ensuring data consistency, and simplifying attribute management.

   Description: It would be extremely useful to have the ability to nest custom attributes in SimpleMDM. This feature would allow administrators to create custom attributes that reference or depend on other custom attributes, enabling dynamic and interconnected data management.

   Use Case: For instance, suppose an organization has a custom attribute called "munkimanifestdepartement" that is a dropdown value in the DEP (Device Enrollment Program) welcome screen. The organization also wants to create another custom attribute called "munkimanifest" that includes the department value selected in "munkimanifestdepartement" along with additional static text. By nesting the custom attribute "munki… more

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Regex Rules for Custom Attribute Validation

   Description: It would be highly beneficial to have the ability to use regular expressions (regex) to validate user-defined custom attributes in SimpleMDM. This feature would allow administrators to set specific rules and patterns that user inputs must adhere to, ensuring data accuracy and consistency.

   Use Case: For example, suppose an organization has a custom attribute for employee IDs. By implementing regex rules, the administrator can define that the employee ID must follow a specific format, such as a combination of letters and numbers. Any user input that does not match the defined regex pattern would be flagged as invalid, preventing incorrect or inconsistent data from being entered.

   Benefits:
   1. Data Accuracy: Regex rules will help enforce consistent data entry by ensuring that user inputs meet the specified patterns or formats.
   2. Prevent Errors: By validating user inputs against regex rules, potential errors or typos can be caught and corrected before they cause issues downstream.
   3. Customization: Administrators can tailor regex rules to match their organization's specific requirements, enabling greater flexibility and control over data validation.

   Implementation: The addition of a regex rule field within the custom attribute settings would allow administrators to define the pattern that user inputs must match. SimpleMDM could then validate the input against the regex rule and provide immediate feedback if the input is invalid.

   Overall, the inclusion of regex rules for custom attribute validation would enhance the data integrity and usability of SimpleMDM, providing administrators with greater control over user or admin inputs.

   Description: It would be highly beneficial to have the ability to use regular expressions (regex) to validate user-defined custom attributes in SimpleMDM. This feature would allow administrators to set specific rules and patterns that user inputs must adhere to, ensuring data accuracy and consistency.

   Use Case: For example, suppose an organization has a custom attribute for employee IDs. By implementing regex rules, the administrator can define that the employee ID must follow a specific format, such as a combination of letters and numbers. Any user input that does not match the defined regex pattern would be flagged as invalid, preventing… more

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Devices API - Create - Extend method to include optional params for DEP device ID and device name

   When creating a device using the Devices API create method (https://api.simplemdm.com/#devices), there are only two parameters that can be passed to it, 'name' and 'group_id'.

   It would be very helpful, especially for devices that are expected to go through automated device enrolment, if we could pass a DEP device ID parameter to it so that a DEP device that is not yet enrolled will automatically be assigned to the nominated device group.
   If the DEP device id parameter is assigned, then the response probably shouldn't include an enrolment URL, as this param should indicate the device is expected to automatically enrol.

   Additionally, it would be helpful if we could also pass a device name parameter to the create method so that when the device does enrol through automated enrolment, the device name will be assigned to it.

   These same params should also be extended to the update method.

   When creating a device using the Devices API create method (https://api.simplemdm.com/#devices), there are only two parameters that can be passed to it, 'name' and 'group_id'.

   It would be very helpful, especially for devices that are expected to go through automated device enrolment, if we could pass a DEP device ID parameter to it so that a DEP device that is not yet enrolled will automatically be assigned to the nominated device group.
   If the DEP device id parameter is assigned, then the response probably shouldn't include an enrolment URL, as this param should indicate the device is expected… more

   •  

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Device Groups API - add methods

   The Device Groups API does not have the following methods:
   create, update, remove/delete, it would be very helpful if this endpoint could have those methods added, along with various options such as:

   create: parameters "name" (required), "lock_screen_message" (optional), and "track_device_location" (optional, default False)

   update: parameters "name" (optional), "lock_screen_message" (optional), and "track_device_location" (optional)

   delete: parameters: "device_group_id"

   Also, the clone method does not currently take any parameters that would allow device group settings to be configured, it would be helpful if the clone method was updated to allow the use of these parameters:

   "name" (required), "lock_screen_message" (optional), and "track_device_location" (optional, default False)

   25 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Add blackmagic Resolve

   Add DaVinci aka BlackMagic Resolve

   https://homebysix.github.io/autopkg-dupe-tracker/timsutton-recipes/Blackmagic/DaVinciResolve18.munki.recipe.html

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Add username field to `device.enrolled` webhook event

   The goal is to have a username field in the device.enrolled webhook event.

   This field would be populated using the the custom attribute defined in the "Username custom attribute" setting in the Automated Enrollment Authentication section.

   In our use case, a user will be prompted to auth using Okta during Automated Device Enrollment (ADE). The username that is returned by Okta would be part of the webhook event payload. We use the username and device serial number to help with automating other internal processes to help determine which user is assigned to which device.

   This could be covered by https://suggestions.simplemdm.com/forums/204404-suggestions/suggestions/46831099-control-webhook-data, but I wanted to call this out more specifically.

   The goal is to have a username field in the device.enrolled webhook event.

   This field would be populated using the the custom attribute defined in the "Username custom attribute" setting in the Automated Enrollment Authentication section.

   In our use case, a user will be prompted to auth using Okta during Automated Device Enrollment (ADE). The username that is returned by Okta would be part of the webhook event payload. We use the username and device serial number to help with automating other internal processes to help determine which user is assigned to which device.

   This could be covered by https://suggestions.simplemdm.com/forums/204404-suggestions/suggestions/46831099-control-webhook-data… more

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. More granularity on the SimpleMDM menu bar icon...

   So, we've just rolled out Nudge and have used the SimpleMDM agent to do so. And now I'm being grumbled at about the Managed Software Centre Icon taking up valuable menu bar space...

   I appreciate I can kill it via the UI - but it's a bit all or nothing, and when we start adding apps to self-service, the menu bar app seems as good a place as any to direct our end users.

   So - can we set icon visibility per assignment group?

   I think what I'm basically saying is if all apps are managed, and there's no self-service then hiding the menu bar icon totally makes sense, but allowing it to appear when you DO have self-service items makes sense (to me)

   So, we've just rolled out Nudge and have used the SimpleMDM agent to do so. And now I'm being grumbled at about the Managed Software Centre Icon taking up valuable menu bar space...

   I appreciate I can kill it via the UI - but it's a bit all or nothing, and when we start adding apps to self-service, the menu bar app seems as good a place as any to direct our end users.

   So - can we set icon visibility per assignment group?

   I think what I'm basically saying is if all apps are managed, and there's no self-service… more

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Add reMarkable to shared apps

   DMG file available publicly here:
   https://downloads.remarkable.com/

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Add notification option for when enterprise certificate is expiring

    Currently when an enterprise certificate is expiring, the only place to see that is on the SimpleMDM site at the top of the Devices page.

    We develop custom apps and push them to SimpleMDM with the API, so we don't log in that often which means we could easily miss these alerts. This could lead to lost productivity for our internal users.

    Please allow us to send notifications to specified user(s) when an enterprise certificate is about to expire.

    It would be nice if one or more time intervals could be selected as well, like you can for VPN and DEP token notification options.

    Currently when an enterprise certificate is expiring, the only place to see that is on the SimpleMDM site at the top of the Devices page.

    We develop custom apps and push them to SimpleMDM with the API, so we don't log in that often which means we could easily miss these alerts. This could lead to lost productivity for our internal users.

    Please allow us to send notifications to specified user(s) when an enterprise certificate is about to expire.

    It would be nice if one or more time intervals could be selected as well, like you can for VPN and… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Add Support for Munki Conditionals to SimpleMDM's Munki Implementation

    Munki includes the ability to set "conditionals" for items in specific manifests to provide granular controls over the installation or appearance of items.

    For example, if I have a multi-site organization, I can set a conditional on a NOPKG item that installs a printer so that the printer install NOPKG only shows up if the device user is connecting to Munki from a specific subnet. This allows me to refine the view of available self-service printers so that, for example, the printers available at Site A only show up if the user's local IP address matches the subnet at Site A. This results in me being able to pile all of my printers into a single Manifest/Assignment Group, and prevent users from seeing an overly polluted view of the printers available.

    Other uses for conditionals include defining installs as only taking place on portable computers (such as a VPN client).

    Please see the Munki documentation for Conditonals in Manifests at https://github.com/munki/munki/wiki/Conditional-Items for more information.

    Munki includes the ability to set "conditionals" for items in specific manifests to provide granular controls over the installation or appearance of items.

    For example, if I have a multi-site organization, I can set a conditional on a NOPKG item that installs a printer so that the printer install NOPKG only shows up if the device user is connecting to Munki from a specific subnet. This allows me to refine the view of available self-service printers so that, for example, the printers available at Site A only show up if the user's local IP address matches the subnet at Site… more

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Add TeamViewer QuickSupport and SplashTop SOS tools to the Shared Application catalog for Munki-based installation.

    Just requests for common user-driven support/screen sharing applications:

    TeamViewer QuickSupport
    SplashTop SOS

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Make logging more detailed for MDM commands

    While I appreciate how detailed SimpleMDM logs can be, especially with raw responses from MDM, sometimes they need to provide more detail. For example, when sending an OS update command the log only contains...

    "Log Details
    Full ID E7B0DBE9-A7C1-4EC8-8CB8-BFA4AB990C59
    Created At 2023-08-17 3:34 PM
    Namespace device
    Type os.update.idle
    Level info
    Device redacted
    UDID F405AA51-FF04-4B71-900F-9C09F0515398
    Serial Number redacted

    Metadata
    {
    "update_version": "13.5.1"
    }
    "

    With OS updates in particular, it's useful to know what mode was used as well. 'downloadonly', 'notifyonly', 'installasap', or 'forceupdate' are all options, but there's no associated data. For some basic commands like Bluetooth enable/disable there's not as much need, but for more complex commands with many possible settings, having that detail is useful. Even more so when a command is queue via API, with no confirmation the passed arguments worked.

    Please consider adding more data to logs.

    While I appreciate how detailed SimpleMDM logs can be, especially with raw responses from MDM, sometimes they need to provide more detail. For example, when sending an OS update command the log only contains...

    "Log Details
    Full ID E7B0DBE9-A7C1-4EC8-8CB8-BFA4AB990C59
    Created At 2023-08-17 3:34 PM
    Namespace device
    Type os.update.idle
    Level info
    Device redacted
    UDID F405AA51-FF04-4B71-900F-9C09F0515398
    Serial Number redacted

    Metadata
    {
    "update_version": "13.5.1"
    }
    "

    With OS updates in particular, it's useful to know what mode was used as well. 'downloadonly', 'notifyonly', 'installasap', or 'forceupdate' are all options, but there's no associated data. For some basic commands like… more

    9 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Improve API docs with examples for each endpoint

    SimpleMDM's API documentation (https://api.simplemdm.com/) is inconsistent in what information is included per endpoint. For example, https://api.simplemdm.com/#custom-configuration-profiles shows the response body for a GET call, but the POST (create) section has no usage information. It's up to the user to intuit from other endpoints the format in which those arguments should be.

    https://api.simplemdm.com/#custom-attributes shows how to set a value for a device, but not create a new custom attribute globally.

    We (the customer) end up making assumptions about API formats which are usually true, but only able to confirm through guessing. It would help to ensure the official docs are correct and up to date.

    I'm asking for two improvements...
    1.100% example code coverage for every endpoint and action (GET, PUT, PATCH, DELETE)
    2. Provide examples in multiple languages - shell, Python, Ruby, Go, JavaScript, and Swift.

    SimpleMDM's API documentation (https://api.simplemdm.com/) is inconsistent in what information is included per endpoint. For example, https://api.simplemdm.com/#custom-configuration-profiles shows the response body for a GET call, but the POST (create) section has no usage information. It's up to the user to intuit from other endpoints the format in which those arguments should be.

    https://api.simplemdm.com/#custom-attributes shows how to set a value for a device, but not create a new custom attribute globally.

    We (the customer) end up making assumptions about API formats which are usually true, but only able to confirm through guessing. It would help to ensure the official docs… more

    24 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Make the `app_usage_data` portion of Munki optional

    Having just confirmed with Eric and others in the Slack channel that SimpleMDM's Munki instance doesn't make use of the app_usage_data feature in Munki - would it be possible to create a toggle to turn it off?

    Additionally there are some global regions where tracking this kind of stuff falls foul of local privacy laws...

    ...and it's upset my privacy focused end users.

    Thanks in advance

    14 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Customize Self Service Kiosk

    I want to be able to change text and icon for the kiosk

    https://kb.filewave.com/attachments/16?open=true

    Doesn't have to be this complete but simple changes so it says <company name> software kiosk

    •  

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Add description as argument for creating/updating custom configuration profiles

    When modifying custom configuration profiles in the web UI, there's an optional field for "Description (Optional description presented to the end user.)", which isn't exposed via the API.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Add support for additional com.apple.MCX keys in FileVault profile type

    The current FileVault profile builder in the admin GUI only has options included in com.apple.MCX.FileVault2, the escrow payload, and dontAllowFDEDisable. Please add support for dontAllowFDEEnable and DestroyFVKeyOnStandby from com.apple.MCX as well.

    Apple docs here: https://developer.apple.com/documentation/devicemanagement/fdefilevaultoptions

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Support SCIM provisioning and de-provisioning for admin accounts

    SCIM (System for Cross-domain Identity Management) is a REST/JSON protocol defined in RFC 7644 that allows identity providers to direct service providers to make account create, update, and delete actions. It is generally used to pre-provision access for new accounts and de-provision access for accounts that no longer require it.

    Please add support for SimpleMDM to work with the SCIM protocol for administrator accounts. A minimum implementation for our purposes would be to create administrator accounts using SCIM at the default permission level, and have the delete function revoke access on the given account. In a perfect world, the SCIM API would also be able to map users to defined roles to keep permissions low - this would apply both at creation time and updating existing admin accounts to use a different role than they currently are assigned.

    SCIM (System for Cross-domain Identity Management) is a REST/JSON protocol defined in RFC 7644 that allows identity providers to direct service providers to make account create, update, and delete actions. It is generally used to pre-provision access for new accounts and de-provision access for accounts that no longer require it.

    Please add support for SimpleMDM to work with the SCIM protocol for administrator accounts. A minimum implementation for our purposes would be to create administrator accounts using SCIM at the default permission level, and have the delete function revoke access on the given account. In a perfect world, the SCIM… more

    17 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. iPhone parts and service history information

    Please add information about whether the device has been repaired and equipped with genuine parts to the device information API.

    Please refer to the URL below.
    https://support.apple.com/en-us/HT212878

    Thanks

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating