leave the setting for MIAUTH as default - so do not set it!
Your user request has nothing to do with MIAUTH - your user is the sync user in a SyncBO - that is the user that started the sync.
What MIAUTH is doing is for the device handling with several users. This is not the same thing and so leave it as it is.
The BO is usually not filled with live - meaning there is no bapi assigned to it by default. So it is triggered by MI itself - but does not get any return and so it is not effecting your App. By the way it is not triggere with every sync - but just with every sync after a client reset or new installation.
MIAUTH syncBO in waiting status will not affect your normal applcation because it uses different mobileID and not the appliacation mobile ID. The reason its in waiting status is either you don't have the MIAUTH syncBO or you didn't 'enabled' it in merep_pd.
if your application doesn't use authorization concepts, you don't need MIAUTH sycnBO. You can disable it from the client and save some valuable sync time. Add the following parameter to MobileEngine.config file
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.