roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jonathan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ROL-1748) url/role-based blog security in security.xml causes errors when adding blogs to custom planet aggregations
Date Fri, 19 Sep 2008 21:05:19 GMT

    [ https://issues.apache.org/roller/browse/ROL-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14413#action_14413
] 

jonathan commented on ROL-1748:
-------------------------------

This was apparently not an issue using Roller 3.1.  Something is different in the way this
is handled in 4.0 (and 4.0.1)?


> 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/roller/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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message