geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-660) Referential integrity checking on role names
Date Sat, 27 Aug 2005 23:22:06 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-660?page=all ]

Aaron Mulder updated GERONIMO-660:
----------------------------------

    Fix Version: 1.0-M5
    Environment: 

> 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-M5

>
> 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


Mime
View raw message