[ http://issues.apache.org/jira/browse/JS2-211?page=history ]
     
Ate Douma closed JS2-211:
-------------------------

     Resolution: Fixed
    Fix Version: 2.0-M2

Implemented, but not using jetspeed-portlet.xml meta data definition.
After some thought this didn't seem right because it really wouldn't be meta 
data in the sense you would
want to store it in the database. Its only a deployment instruction.

I implemented it quite simple now by allowing optional configuration of the 
PortletApplicationManager.
Just set appropriate values for the roleManager property and autoCreateRoles 
property.

> Autocreate RolePrincipals for PA role definitions on deployment
> ---------------------------------------------------------------
>
>          Key: JS2-211
>          URL: http://issues.apache.org/jira/browse/JS2-211
>      Project: Jetspeed 2
>         Type: New Feature
>   Components: Deployment, Security
>     Versions: 2.0-dev/cvs
>     Reporter: Ate Douma
>     Assignee: Ate Douma
>     Priority: Minor
>      Fix For: 2.0-dev/cvs, 2.0-M2

>
> When a new PA is deployed with several role definitions, these roles still 
> needs to be created by hand
> before they can be assigned to a user.
> As the required name of these roles (as derived from the web.xml) is 
> predefined, I want to add the feature
> to automatically create new RolePrincipals on deployment.
> As initial implementation I'm going to use a new jetspeed-portlet.xml 
> meta-data definition: <roles create="true"/>
> to enable this feature.
> Also, if nobody objects, I'd like to make this the default behavior once this 
> works and then 
> <roles create="false"/> can be used to prevent it.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to