Upland OL User community

Versioning Preferences

#1

Under Windows | Preferences | Versioning, we enter the credentials for the GIT installation. However, when a different user (we share a dev server and use Remote Desktop Connection and login to the server with our AD/LDAP credentials) runs Connect Design, they see MY credentials. Is that correct? Shouldn’t each user enter their own credentials in Preferences? This seems to be a “system wide” setting when it should be a “user” setting.

The cloned repository still ends up in the [username]/documents/OL Connect folder. But the “Committed By” name in Version History always shows the current users name regardless of which user did the commit.

In short: please explain what credentials are meant to be used in Preferences, and how those credentials relate back to the actual user running the Connect instance.

#2

Bumping this post due to no replies. The “Help” button for the Version credentials screen brings up a generic landing page, no actual information.

In short: please explain what credentials are meant to be used in Preferences, and how those credentials relate back to the actual user running the Connect instance.

#3

The help system has been moved to a different platform so the contextual help may not lead to the expected page, you have to use the Search feature to get there.

As for the versioning credentials, they are saved along with the Designer preferences and are therefore shared across users on the same PC. That is something we aim to change at some point (not just the versioning info, but all preferences) but it is unfortunately not as simple as it would appear to be because it requires the software to be installed differently.

#4

So we need to use a singular account across all users… and that means an account that has rights to all the various GIT repositories we use. I think that’s possible.

#5

Hello,

While reviewing this thread, I noticed that you seem to be using Connect Designer or Server under a user account other than the one that was used to install it. Please note that, even though we know that there are several customers that do this and that it works as expected for most customers most of the time, this is actually not supported and may cause some undefined behavior, such as the one your are describing.

Connect Designer or Server are designed to be installed and used under the same user account. This is an unfortunate known limitation that we plan to address in a future version.