continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brent N Atkinson (JIRA)" <>
Subject [jira] [Commented] (CONTINUUM-2701) Legacy projects with ampersand lack permission after upgrade
Date Thu, 07 May 2015 16:39:01 GMT


Brent N Atkinson commented on CONTINUUM-2701:

The error message was a little confusing in the project description. It is more obvious what
is going wrong when you attempt to edit the description in JIRA since the formatting goes
away. I'm going to update the description to prevent formatting of the message. I was able
to get a similar message locally.

> Legacy projects with ampersand lack permission after upgrade
> ------------------------------------------------------------
>                 Key: CONTINUUM-2701
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>            Reporter: Philippe Busque
>              Labels: maybe-1.5
>             Fix For: 1.5.0
>         Attachments: CONTINUUM-2701-screenshot.png
> I upgraded Continuum from 1.3.6 to 1.4.1
> Some of my projets had ampersand in their name. In 1.3.X, this was allowed.
> Now in 1.4.1, the interface block you from creating project with ampersand in their name.
However, for every project with ampersand already in their name, those project are locked
> When opening the project, the following message is displayed :
> Authorization Error
> You are not authorized to access this page. Please contact your administrator to be granted
the appropriate permissions.
> In the logs, the following trace is displayed:
>  INFO  org.codehaus.plexus.redback.authorization.rbac.RbacAuthorizer  - no permission
found for operation continuum-view-group resource Questions &amp; Answers

This message was sent by Atlassian JIRA

View raw message