[JBoss JIRA] Updated: (JBAS-2624) Generic AuthorizationManager service
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2624?page=all ]
Dimitris Andreadis updated JBAS-2624:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
(was: JBossAS-5.0.0.Beta1)
Affects Version/s: (was: JBossAS-5.0.0.GA)
Move to Beta2.
> Generic AuthorizationManager service
> ------------------------------------
>
> Key: JBAS-2624
> URL: http://jira.jboss.com/jira/browse/JBAS-2624
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Anil Saldhana
> Assigned To: Anil Saldhana
> Fix For: JBossAS-5.0.0.Beta2
>
>
> For the first pass, the AuthorizationManager interface is defined as follows:
> public interface AuthorizationManager
> {
> //Permission can be of type WebUserDataPermission,
> //WebResourcePermission and WebRoleRefPermission
> public boolean hasPermission(Permission perm, Principal principal);
> public boolean doesUserHaveRole(String roleName);
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Closed: (JBMICROCONT-10) Simple Profiles for testing purposes
by Scott M Stark (JIRA)
[ http://jira.jboss.com/jira/browse/JBMICROCONT-10?page=all ]
Scott M Stark closed JBMICROCONT-10.
------------------------------------
Resolution: Done
This is part of the jboss5 beta.
> Simple Profiles for testing purposes
> ------------------------------------
>
> Key: JBMICROCONT-10
> URL: http://jira.jboss.com/jira/browse/JBMICROCONT-10
> Project: JBoss MicroContainer
> Issue Type: Task
> Components: Deployment
> Reporter: Adrian Brock
> Fix For: JBossMC_2_0_0 Beta
>
>
> Simple Profile
> --------------
> For initial testing we need a simple profile
> that takes identifies a list of deployments and
> passes them to the MainDeployer
> Backwards Compatibility Profile
> -------------------------------
> This will work like old jboss
> i.e. processing similar to statically
> deploying the conf folder, conf/jboss-service.xml
> and the deployment scanner
> farm and deploy-singleton are irrelvent since
> these will be handled by tags inside the
> microcontainer metadata
> IDE Profile
> -----------
> TODO - Need to synch with JBoss IDE
> Versioned/Persistent Profile
> ----------------------------
> TODO
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months