![]() If you specify No authentication but enter a repository URL which includes a username and password, Fisheye will remove the password from the URL and set the authentication method to Password, storing the password specified in the password field.Screenshot: 'No authentication' selected for a local repositoryįisheye's access to repositories is always read-only, so it can easily be used with repositories which only require authentication and authorization for write operations. repositories which are accessible to the Fisheye server on the local filesystem. ![]() internal repositories on a secure network which allow anonymous reads to network users, or.public repositories which grant read-only access to anonymous users, or.If you have supplied credentials via another mechanism (such as ssh-agent or a default passphrase-less private key for a ssh connection) Git or Mercurial will use this automatically. It means that Fisheye can connect to the repository using Git or Mercurial without any credentials or authentication. This is the simplest authentication method. Screenshot: Selecting an authentication method This section will be available when initially defining a repository configuration and also in the "SCM Details" section when maintaining a repository. the "Mercurial Authentication" section in the screenshot below). When a Fisheye repository type supports these authentication methods, you will see an Authentication section during repository configuration (e.g. Password for http(s) - This is for the username / password method of authentication with http and https URLs (also known as basic-auth).Upload private key for SSH - A SSH key is created and managed externally to Fisheye.Generate key pair for SSH - A SSH key is generated and managed by Fisheye to access the repository. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |