You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "David Blevins (JIRA)" <de...@geronimo.apache.org> on 2005/09/27 00:11:41 UTC

[jira] Updated: (GERONIMO-660) Referential integrity checking on role names

     [ http://issues.apache.org/jira/browse/GERONIMO-660?page=all ]

David Blevins updated GERONIMO-660:
-----------------------------------

    Fix Version: 1.0
                     (was: 1.0-M5)

> Referential integrity checking on role names
> --------------------------------------------
>
>          Key: GERONIMO-660
>          URL: http://issues.apache.org/jira/browse/GERONIMO-660
>      Project: Geronimo
>         Type: Improvement
>   Components: security
>     Versions: 1.0-M3
>     Reporter: David Jencks
>      Fix For: 1.0

>
> Currently there is nothing stopping you from having a default-role or a principal mapped role in the geronimo security descriptor that is not present in the roles listed in the j2ee deployment descriptors. I think it would be useful to check on this and at least print a loud warning, or throw a deployment exception.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira