Git svn clear stored credentials

Recently a change was made in my company in the way the SVN repositories were handled; as a result we had to change the accounts we used to access the repos

Whenever I tried pulling or pushing info into those repositories I was getting errors like :

RA layer request failed: PROPFIND request failed on '/svn/2001/ufasoli/myproject/trunk': PROPFIND of '/svn/2001/ufasoli/myproject/trunk'
: 403 Forbidden (https://internal.svn.com) at /lib/Git/SVN.pm line 717

I realized that it was because the credential information was cached locally on the machine, so the system was sending old information , the tricky part was that the old accounts allowed authentication on the repositories, they were just no longer authorized to do anything on them, so I was getting an HTTP 403 error and the system was not prompting me for a new password (since the old accounts could still log in...)

So this is how I fixed it on my windows machine:

Under your user folder you should have a folder where subversion stores cached data C:\Users\ulf\.subversion (in my case)

This folder contains an auth folder were you will normally find another 3 folders :

• svn.simple
• svn.ssl.server
• svn.username

To delete the cached credentials you can delete the content of the following folders :

• svn.simple
• svn.ssl.server

Once this folders deleted git should prompt you again for your username/password

Access jasper reports with URL authentication and remove jasper decoration for better integration

To give you some context recently while working on a new small project I needed to include a few Jasper Reports that where hosted in a Jasper Serverrepository. The main requirement was to include these reports in a lightweight application without the JAVA stack but using only HTML+JavaScript

To my knowledge there are 3 ways to accomplish this :

1. Allow anonymous access to a given URL pattern (I had some troubles working with this approach)
3. Use Jasper's REST APIand authenticate through it (probably the cleaner way)
4. Provide credentials in the URL (quick and dirty) :)

For reasons outside the scope of this article I had to use the 3rd option and provide the credentials in the URL.

Note : This is not a clean way to access the repository (especially as you may see the username and password are clear text) but sometimes there no way around it

Jasper server uses spring under the hood to provide authentication/authorization so you can use the standard Java authentication mechanism, which basically consists in providing the following parameters in the URL :

• j_username
• j_password
• j_acegi_security_check (this one is optional depending on the Jasper Server version)

If your Jasper Server is configured using an organization you will need to provide it as long with your credentials using the special syntax j_username=myUsername|myOrganization

So for example if the base url for your report is the following :

http://my-jasperserver/flow.html?_flowId=viewReportFlow&standAlone=true&_flowId=viewReportFlow&ParentFolderUri=%2Freports%2Fsamples&reportUnit=%2Freports%2Fsamples%2FStandardChartsEyeCandyReport

And your credentials are :

• username : jasperadmin
• organization : myOrg
• password: jasperadmin

Your URL will become :

http://my-jasperserver/flow.html?_flowId=viewReportFlow&standAlone=true&_flowId=viewReportFlow&ParentFolderUri=%2Freports%2Fsamples&reportUnit=%2Freports%2Fsamples%2FStandardChartsEyeCandyReport&j_acegi_security_check&j_username=jasperadmin|myOrg&j_password=jasperadmin

One last thing.By default when showing a report you will get all of Jasper Server decoration around it (menubars, links, etc.) you can get rid of this by appending the one of following parameters to the URL (please note that parameters are not the same depending on which version of Jasper you are using : Community or Corporate)

• Remove jasper decoration in community version : &decorate=no
• Remove jasper decoration in corporate version : &theme=embed&viewAsDashboardFrame=true