English | 日本語
Home > Merge > Merge for Windows > Documentation Contents > Credentials

Credentials

InformationTo reach this options page, select Options > Options... > Application > Credentials

Use the table on this page to provide user name and password information for accessing Perforce, Subversion and Visual SourceSafe repositories. All passwords are stored securely in encrypted form in the Windows Registry.

For more information about accessing Perforce, Subversion and Visual SourceSafe repositories, see the Perforce File System Plugin, Subversion File System Plugin and Visual SourceSafe File System Plugin topics.

To provide anonymous access to a Subversion or Visual SourceSafe server, add an entry to the table for the server with a blank User name and Password.

Column Description
Server The name of a Perforce (together with the Perforce port), Subversion or Visual SourceSafe server to which you might want to connect. For example: 10.0.1.1:1666, server.example.com, or p4.example.com:1667.
User name The user name to use when connecting to the server. Leave blank for anonymous access to a Subversion or Visual SourceSafe server.
Password The password to use when connecting to the server. Leave blank for anonymous access to a Subversion or Visual SourceSafe server.
Default For If a Perforce URI is specified that does not specify a server, username or password (e.g. p4://depot/folder/file.txt), Merge will use the first credential entry marked as the default for Perforce to provide the required information.

Credentials and the Versions button

Merge uses the entries in the credentials table when endeavouring to populate the file and folder comparison Versions button button versions menu in the following situations:

For more information about the Versions button button, see Comparing Text Files (or Typed/Pasted Text).

Using credentials to supply a placeholder password

It is possible to use * as a password placeholder with Perforce, Subversion and Visual SourceSafe URIs. This prevents passwords appearing visibly on the screen in the URI.

For example, if the URI p4://jrs:*@p4.example.com/depot/folder/file.txt were used in a file comparison, the credentials list would be checked for an entry containing a server p4.example.com and a user name jrs. The password from that entry would then be used to make the connection.