incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henry Story (JIRA)" <>
Subject [jira] [Commented] (CLEREZZA-506) profile access denied
Date Thu, 05 May 2011 15:33:03 GMT


Henry Story commented on CLEREZZA-506:

This can be fixed by the following semi-diff to rdf.web.proxy/rdf.web.proxy.core/src/main/scala/org/apache/clerezza/rdf/web/proxy/WebProxy.scala

		lazy val theGraph: MGraph = try {
			val g = tcManager.getMGraph(graphUriRef)
		} catch {
			case e: NoSuchEntityException => {
+				import scala.collection.JavaConversions._
+				tcManager.getTcAccessController.
+					setRequiredReadPermissionStrings(graphUriRef,
+					List(new TcPermission(Constants.CONTENT_GRAPH_URI_STRING, TcPermission.READ).toString))

The question is that the right longer term solution? If I add this then extra information
placed in the graph becomes visible in rdf/xml - but the html is closed. Ok so perhaps a problem
in the jsr311 code.

I am still not quite sure exactly what these permissions do. They give everyone read permission
to the graph? If so then perhaps we should make it possible to set how visible a proxy graph
should be. Perhaps the name of remote proxy graphs will the depend on this visibility. If
it is visible by all, it just has the remote name. If it is to be visible by a local user
it would have a name, relative to that user or group...

> profile access denied
> ---------------------
>                 Key: CLEREZZA-506
>                 URL:
>             Project: Clerezza
>          Issue Type: Bug
>            Reporter: Henry Story
>            Assignee: Henry Story
>   Original Estimate: 3h
>  Remaining Estimate: 3h
> All profile access is denied currently to anonymous, which means that it is not even
possible to see the public key.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message