[prev in list] [next in list] [prev in thread] [next in thread] 

List:       geronimo-dev
Subject:    [jira] Updated: (GERONIMO-4155) Can use a run-as role without
From:       "David Jencks (JIRA)" <jira () apache ! org>
Date:       2009-07-30 21:55:15
Message-ID: 247976205.1248990915004.JavaMail.jira () brutus
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/GERONIMO-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

David Jencks updated GERONIMO-4155:
-----------------------------------

    Fix Version/s:     (was: Wish List)
                   2.2

A little more thought shows its easy to implement a runtime exception.  Its not \
really possible to do deploy time checking because the credential store may require \
some kind of remote access not available to the deployment machine.

> Can use a run-as role without defining it
> -----------------------------------------
> 
> Key: GERONIMO-4155
> URL: https://issues.apache.org/jira/browse/GERONIMO-4155
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues) 
> Components: deployment, web
> Affects Versions: 2.1.1, 2.1.4, 2.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.2
> 
> 
> The testsuite/enterprise-testsuite/sec-tests app demonstrates that you can set up a \
> servlet with a run-as role of "baz" that is not mapped to a subject in the geronimo \
> security element and the app will deploy and run fine.  This should result in a \
> deployment error and failing that a runtime error. problem present in trunk rev. \
> 670237

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[prev in list] [next in list] [prev in thread] [next in thread]