We support variables in the Policy. So you can specify variables such as %email% or %username% or %userPrincipalName% or %domain% etc.

If the users are local users, We will replace the variables with user’s details and send it to the device. If the users are from Active Directory or any other Directory Services we will replace that with corresponding LDAP attributes and send it to the devices.

For Password, you want to send a value as a password then you can add that. If you leave blank, we will prompt the user to type the password and you do not need to specify anything in that box.

We are expanding this module in our upcoming releases, so you can send any of your LDAP (or your directory service) attributes and send it to them.

That was what I was considered doing. However, what I noticed when I did this was:

1. Email settings were pushed to device, email password was prompted for on device (fine)

2. Once email password is input on device, email setup goes fine. However, if subsequent policy changes (not related to email) are made, when these are pushed to the device, the email settings will be again be pushed to the device. This is not necessary and causes the email client on the phone to attempt to setup a duplicate email account.

First off, I am very glad to hear about any LDAP attributes being able to be used in future, that would be ideal for me. Do you support OpenLDAP as well as Microsoft AD?

Anyway, I think I have discovered a solution that will work for me (basically I am using a large policy for 99% of config and a small user specific policy just for email, then associating both with a given user – this seems to give better results than an empty password).

Same: {“detail”:”Sorry, Something went wrong, An unexpected condition was encountered while the server was attempting to fullfill the request”}

Am I doing something wrong or is this a limitation of a trial account I am not aware of? One thing I did notice with latter two was: while they did not edit the policy settings specified in the JSON, they did +1 increase the policies version numbers.

Retrieving info about policies worked fine using the API, just editing via API was the issue.

(i) We do not support Open LDAP or Azure AD currently. But it will be available in the future.

(ii) The issue in email policy you mentioned is not something that is supposed to happen. We tried to recreate the issue here, but we didn’t find any problem. In fact, it worked perfectly. However, we are curious to know why this happened to you. It would be great if you could share some more information about the policy. You can drop a mail to our support or we can contact you. Just let us know what time works for you.

(iii) The error in the API has been fixed and updated. You will not find the issue anymore.

Hope this helps. We do have instant chat, email and phone support available.