History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: SES-695
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Arjohn Kampman
Reporter: Daniel Hahn
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Sesame

HTTP Authentication for console

Created: 05/Jan/10 12:44 PM   Updated: 15/Feb/10 07:33 PM
Component/s: Console
Affects Version/s: 2.3.0
Fix Version/s: 2.3.1

File Attachments: 1. File console.diff (4 kb)
2. File console.diff (3 kb)



 Description   
The Sesame console doesn't permit authentication for password-protected HTTP repositories. (That is "connect <url>." doesn't work with repositories that require authentication).

I've patched Console.java to allow username/password authentication. This is very basic (visible password input etc.), but it'll allow the console to use such repositories. It will also automatically ask for auth info once it detects an authentication failure.

 All   Comments   Change History      Sort Order:
Comment by Daniel Hahn [05/Jan/10 12:45 PM]
Diff for Console.java to permit HTTP authentication. Works w/ 2.3.0.

Comment by Daniel Hahn [05/Jan/10 02:12 PM]
Updated version of patch, now correctly inits the manager if user/pass information.

Comment by Arjohn Kampman [07/Jan/10 03:23 PM]
Patch was applied with some small modifications.

Comment by Golda Velez [15/Feb/10 07:33 PM]
Hi, will this patch apply to WorkBench?

I just installed Sesame this morning, and noticed that the workbench seemed to pretty much make the store world-writable. So I uncommented the <security-constraint> sections in
webapps/openrdf-sesame/WEB-INF/web.xml and added corresponding tomcat user + role, but now my workbench doesn't find the local rdf server.

Sorry if this is a FAQ, I have spent about 2 hrs searching for a solution and trying things..

--Golda