![]() Make sure your server configuration uses the correct ServerName value. ![]() Svn: OPTIONS of '': SSL negotiation failed: SSL error code -32856 ()įor security reasons, the default configuration does not allow users to commit changes to the repositories over HTTP or HTTPS. Run the following command, assuming your repository is located at the default location of /opt/bitnami/repository: $ sudo chown -R daemon:subversion /opt/bitnami/repository To permit this, change the permissions of your repository directory so that the Apache user is able to write to it. IMPORTANT: Making this change will allow any user to commit changes to your repository. You should now be able to commit changes to the repository using a tool like TortoiseSVN, as shown below.Ĭonfigure basic authentication for a Subversion repository To avoid unauthorized commits and possible data loss, configure basic authentication for your repository as discussed in the next section Update the Apache configuration to enable basic authentication: Once your repository is accessible over HTTP(s), it is recommended that you protect it from unauthorized access by configuring authentication for different users. ĪuthUserFile /opt/bitnami/repository/users Update the Apache configuration file at /opt/bitnami/apache/conf/vhosts/nf and add the highlighted directives below. With this configuration, repository access is only available to those users listed in the /opt/bitnami/repository/users file and they will need to authenticate themselves before gaining access. Note that you should update the path to the file based on the actual location of your repository.Ĭreate the /opt/bitnami/repository/users file and add a user account named myuser to it using the following command. You will be prompted to enter a password for the user account. Note that you should update the path to the file based on the actual location of your repository. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |