FAQ

OnTime for Microsoft

Category
Category
Administration
Administration
Interfaces
Interfaces
Symptom When accessing OnTime for Microsoft with domain(SSO) login enabled the server reports “HttpStatus Code 400 Bad Request – RequestUrl/Field to Long” during the domain logon redirect on the OnTim...
The web application requires a HTTPS authorisation. Check if you are using the correct authorisation setup in the Admin Client.
Central roll-out: Usually OnTime® Mobile is delivered to the whole organisation from a central place, this would usually be through Mobile Device Management Solutions, and therefore it shouldn’t be up...
It has been reported that the Microsoft Domain controller has a vulnerability called ‘KrbRelayUp’ when using standard LDAP requests. This vulnerability can be removed in the domain controller by chang...
The OnTime client uses the Token to verify the users identity when communicating with the OnTime server. What is the Token used by OnTime? The Token consists of the identity of the connecting user and...
The user makes a login request from the client to the OnTime server. The OnTime servers passes the login as an Authentication request to the Exchange server. In turn the user gets a token, valid for t...
For information on how to install the OnTime Outlook add-in, please refer to the OnTime Installation & Configuration manual available for download here
The license for OnTime requires the USERDOMAIN name of the Windows server on which the OnTime server runs. This is true for both trial and production environments. You can find the USERDOMAIN by execu...
Symptom Stacktrace in ontigms.0.0.log containing something like “PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to reque...

FAQ MS

Location:
Date:
Time: