Skip to content
Josh Gough edited this page Sep 23, 2013 · 3 revisions

Common misconception:

  • Some users believed that an administrator can approve an integration one time against a target VersionOne instance, and that all their internal company users could then use the integration without additional configuration steps on an individual basis.
    • Reality: each developer (currently) has to grant an integration authority to act on his or her behalf by going to through the steps documented at The VersionOne Community Site, specifically with either the Web or Installed application directions.

Goal for Visual Studio Client OAuth2 Enabling:

  • There will be "a user interface component" that allows a developer to grant the Visual Studio Client the authority to act on his or her behalf against a specified VersionOne instance.
    • It's curently an open question as to whether he "user interface component" may be from within Visual Studio or outside?

Clone this wiki locally