You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2013/04/10 21:05:16 UTC

[jira] [Closed] (ROL-1748) url/role-based blog security in security.xml causes errors when adding blogs to custom planet aggregations

     [ https://issues.apache.org/jira/browse/ROL-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Glen Mazza closed ROL-1748.
---------------------------

    Resolution: Not A Problem

Matter apparently resolved per reporter's last comment.
                
> url/role-based blog security in security.xml causes errors when adding blogs to custom planet aggregations
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ROL-1748
>                 URL: https://issues.apache.org/jira/browse/ROL-1748
>             Project: Roller
>          Issue Type: Bug
>          Components: Authentication, Roles and Access Controls
>    Affects Versions: 4.0
>            Reporter: jonathan
>            Assignee: Roller Unassigned
>
> I've been using security.xml to secure various blogs only allowing certain user types access:
> <property name="objectDefinitionSource">
>             <value>
>                 PATTERN_TYPE_APACHE_ANT
>         ...
>                  /<blogname>/**=register
>                 ...
>             </value>
> etc...
> However... This is causing big troubles when I attempt to create planet groups.  I get the following error when trying to add a feed (http://blogs.domain.com/roller/<blogname>/feed/entries/atom) to a custom aggregation group:
> ERROR 2008-09-17 10:34:52,954 PlanetSubscriptions:save - Unexpected error saving subscription
> Error fetching subscription - http://blogs.domain.com/roller/<blogname>/feed/entries/atom
> --- ROOT CAUSE ---
> com.sun.syndication.io.ParsingFeedException: Invalid XML: Error on line 1: Content is not allowed in prolog.
> If I remove the security configuration, the problem goes away.  Is there a way to do this and keep the security.xml paths secured?  I assume the application is getting denied access to the feed due to lack of credentials?
> Any help greatly appreciated, as always.
> jonathan.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira