{"id":588,"date":"2015-05-26T17:36:29","date_gmt":"2015-05-27T00:36:29","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Polarion-Blog\/Tech-Tips-Restricting-Repository-Access-Via-SVN-WebClient\/ba-p\/380968"},"modified":"2026-03-26T05:28:59","modified_gmt":"2026-03-26T09:28:59","slug":"tech-tips-restricting-repository-access-via-svn-webclient","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/tech-tips-restricting-repository-access-via-svn-webclient\/","title":{"rendered":"Tech Tips: Restricting Repository Access Via SVN WebClient"},"content":{"rendered":"

Welcome to another post from the Polarion Technical Support Team. From time to time we face challenging situations when the solution of the problem is not obvious at first glance and some research around is necessary. Let me share with you one such case that we successfully resolved.
\n

When security isn’t quite secure enough<\/H2>
\nYou probably are aware of Polarion’s multi-tier security architecture and granular permissions scheme that lets you fine tune who can access what. But you might encounter a situation when you require Polarion to be even more strict in its security, and setting permissions is not enough. Suppose, for example, that like one of our customers you want to restrict users’ access to Polarion’s Subversion repository via the SVN WebClient, which appears in the UI as the Repository Browser topic. Our customer said they didn’t want allow their users to upload or download files using that feature.<\/p>\n

When I received the request asking how to restrict users from accessing the repository via SVN WebClient, I was convinced at first that it is absolutely not possible, as this component is tightly bundled within Polarion. Then I realized that it is at least possible to hide the Navigation topic in the UI. So in Polarion’s global administration, I went to the Portal > Topics configuration and removed the XML element that makes the SVN WebClient (i.e. Repository Browser) available in the UI:
\n<topic id=”repository_browser”\/><\/CODE>.<\/p>\n

OK, so this solution prevented new and less experienced users from accessing the SVN WebClient. But what happens if some users have saved its URL, or they have the link in some email or chat history, or they get it from someone on some internet forum? If they have the URL, they can access the client even if it’s access point is hidden in Navigation. It took me quite some time to figure out, but I got an idea for a neat little hack: what if I make a redirect in Apache to some custom page? I thought that should definitely work… and it really does.
\n

The great repo browser hack in Apache<\/H3>
\nBy using Apache mod_rewrite<\/EM> you can redirect any page you want. With simple syntax written to the polarion.conf<\/EM> file and then restarting everything, I convinced Polarion not to display the SVN WebClient even if someone hits its URL. Here’s the end result of this simple but effective hack:
\n

\"Screenshot:<\/A><\/P>
\n

You can get inspired by the code below, where the important parameters of the rewrite rule are location of the SVN WebClient and a custom page that will be displayed in the portal instead of it.<\/P>
\n<IfModule mod_rewrite.c>
\nRewriteEngine on
\nRewriteRule ^\/polarion\/svnwebclient \/var\/www\/norepobrowser.html
\n<\/IfModule><\/CODE>
\n

Still not tough enough?<\/H3>
\nWhat if your goal is to deny access to the whole repository from any<\/EM> SVN client… such as TortoiseSVN? There’s a simple solution: you can deny access from all IP addresses except some specific one (localhost<\/EM> or a server\u2019s fully qualified domain name). The result is that nobody can access the repository from any address, using any client. Only Polarion itself, or an admin logged in to the server are eligible to access repository.<\/p>\n

In the Apache configuration file where the repository location is specified (normally polarionSVN.conf<\/EM>), it will be necessary to add directives that deny access from all IP addresses and just allow it from one specific one. These lines added to the <\/repo> location definition will get the job done:<\/p>\n

Order deny,allow
\nDeny from all
\nAllow from my.polarion.server.mydomain.com<\/CODE><\/p>\n

…where my.polarion.server.mydomain.com<\/EM> is the fully qualified domain name of the Polarion server (same as in the system configuration file polarion.properties<\/EM>).
\n

Happy hacking!<\/H3>
\nSometimes some light hacking of the Apache configuration is just the trick you need. But it’s something you should undertake with caution, and be sure you know what you’re doing. Never experiment with your production system! Remember that you can always download a copy of Polarion with it’s built-in 30-day 3-user evaluation license, and install it on some test machine. Remember too that Polarion’s Gold support plan is available, which provides a free staging server, and help from our experts with any highly individualistic needs you may have.<\/p>\n

In which other areas would you find this trick useful? Is there something you would like to see our support team blog about? Don\u2019t forget to leave us a comment.<\/p>\n

<\/p>\n

 
\n

\"Banner:<\/A><\/P><\/p>\n","protected":false},"excerpt":{"rendered":"

Welcome to another post from the Polarion Technical Support Team. From time to time we face challenging situations when the solution of the problem is not obvious at first glance and some research ar…<\/p>\n","protected":false},"author":48696,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[],"industry":[],"product":[],"coauthors":[],"class_list":["post-588","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/588","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/users\/48696"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/comments?post=588"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/588\/revisions"}],"predecessor-version":[{"id":589,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/588\/revisions\/589"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/media?parent=588"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/categories?post=588"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/tags?post=588"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/industry?post=588"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/product?post=588"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/coauthors?post=588"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}