[
https://issues.apache.org/jira/browse/JUDDI-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268620#comment-14268620
]
ASF subversion and git services commented on JUDDI-908:
-------------------------------------------------------
Commit d7195270482912abf42a29e2ed7b647dd5cb910a in juddi's branch
refs/heads/master from [~spyhunter99]
[ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=d719527 ]
JUDDI-241 fixing several issues with publisher assertions
JUDDI-256 updating the tck to fire up two nodes, setup synchronization, then
perform a custody transfer
JUDDI-905 done for now, reports transactions/second for a number of basic
save/delete operations
JUDDI-906 tck now fires up two nodes, replication is working yet, but needs
some additional test cases
JUDDI-907 service code is in place, still need a ui component and test cases
JUDDI-908 functionality fixed, test case still needed
> Enforce access control rules on deleting publisher assertions
> -------------------------------------------------------------
>
> Key: JUDDI-908
> URL: https://issues.apache.org/jira/browse/JUDDI-908
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Reporter: Alex O'Ree
> Assignee: Alex O'Ree
> Fix For: 3.3
>
>
> previous versions pretty much let any authenticated user delete a publisher
> assertion. Assuming they had the information
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
