incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CLEREZZA-506) profile access denied
Date Thu, 05 May 2011 18:55:03 GMT

    [ https://issues.apache.org/jira/browse/CLEREZZA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029500#comment-13029500
] 

Reto Bachmann-Gmür commented on CLEREZZA-506:
---------------------------------------------

- The question is that the right longer term solution? 

I think that reading a cached garph from the web shoul be allowed to everyone, or as you implement
it, everyone who's allowed to read from the content graph

- If I add this then extra information placed in the graph becomes visible in rdf/xml - but
the html is closed.
The permissions are on the graph so serialization format really makes no difference, with
the permission requirement as set above everyone allowed to accedd the conrtent graph can
access the graph named by graphUriRef. Either directly or by some jax-rs root resources.

> profile access denied
> ---------------------
>
>                 Key: CLEREZZA-506
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-506
>             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: http://www.atlassian.com/software/jira

Mime
View raw message