Integrating with Axosoft OnTime using Windows authentication

[lbauer]

Have you tried user just "user" instead of "user@mydomain.com?"

[hutch619]

Yes, I've tried it as "user@mydomain.com", "user" and even "mydomain/user" but none of them worked.

As a sanity check, I decided to test out Axosoft's sdk example project to rule out the possibility of me setting up something wrong on OnTime's end. The example worked just fine so it's got to be something on Vault's side that isn't set up right.

For anyone else having problem that wants to verify Ontime's SDK service is set up correctly:

• OnTime's 2011 SDK Samples
• Walkthrough video

In OnTime's sample project, all that's required are the urls for the service handlers and the Security Token. You don't have to provide a windows account or password which I assume is because the id of the ontime user the web service will run as has already been specified in the Web.Config for the OnTimeSDK service. If this is the case then why does Vault need this? Is Vault trying to override what this specified user is for auditing purposes?

[lbauer]

Could you send me a screenshot of your OnTime Manage Users page, showing your Name/Windows ID/LoginID/Windows Auth, etc. values?

Email support at sourcegear.com, Attn: Linda. Please include a link to this forum post.