Do these users and roles exist on the public instance too? Otherwise you won't be able to activate.

-will

On 01.04.2009, at 23:33, Sebastian Frick wrote:


Hello,

we have a several templates for non-cms-editors, which maintain their content by logging in at the author instance, being redirected directly on their templates where they are able to activate their content by using a button on page. Due to security reasons I'd like to define a certain role with maximum restrictions. Beside paths like resources, their own templates (including some dialogs) and the activation uri /.magnolia/activation/* (I also tried /.magnolia/ activation) they shouldn't have any acess to other URIs (neither content nor internal admin pages). The activation process seems to work fine as you cannot see any 401-errors on the client side via firebug but it's throwing an exception though:

"info.magnolia.cms.exchange.ExchangeException: Not able to send the activation request [http://localhost:8081/.magnolia/activation]: Server returned HTTP response code: 401 for URL: http://localhost:8081/.magnolia/activation : Not able to send the activation request [http://localhost:8081/.magnolia/activation ]: Server returned HTTP response code: 401 for URL: http://localhost:8081/.magnolia/activation at info .magnolia .module .exchangesimple.BaseSyndicatorImpl.activate(BaseSyndicatorImpl.java: 288)"

Activation process works fine as long I allow all URIs, the roles on publish and author are equal. Am I using a wrong pattern or is there a missing URI?

Regards Sebastian


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to