Scott,

>>Where do you suggest that we store the credential of the principal to be
>>associated with the "run-as" role? In the jboss-web.xml file? I assume
>>it would be necessary for Jetty set up *both* the (new) principal and
>>its credential to enable the normal ejb authentication and authorization
>>mechanisms.
>>
> 
> The principal could be setup in jboss-web.xml, but there is no credential.
> The principal and role are simply assigned.

I can't see how the web container would be able to get away without
assigning a credential along with the principal. If we don't assign
the credential, then anyone could write some code that would set a 
principal and a role (but not the password) and be able to execute ejb
methods protected by a method-permission with that role.

To prevent  this, I can see 2 possibilities:

1. we authenticate the principal by using the principal's credential

2. we authenticate the web-container to the ejb container to enable
    it to use the principal and run-as role

The former means storing the principal's credential in a file
somewhere, probably jboss-web.xml.

The latter has many far-reaching implications and would be a lot of
work to implement, that is if it isn't already - does JBoss support
inter-container security mechanisms?


Jan






_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to