|
| 1.406.2.47 | modified | starksm | testsuite/build.xml | Include all deploy/jms content recursively in the jacc test configuration |
| 1.1.4.3 | modified | starksm | tomcat/src/main/org/jboss/web/tomcat/security/JaccAuthorizationRealm.java | - If there is no JACC Subject context handler data when the resource permission check is made, check to see if the request principal is a JBossGenericPrincipal that encapsulates the authenticated user. This is needed for FORM-AUTH which caches the authenticated user as part of the session context and does not reauthenticate to the Realm. Resolves (JBAS-1592) JaccAuthorizationRealm always returns false on subsequent requests.- Fix a problem with the migration to tomcat 5.5.x that broke the isUserInRole call for the JACC Realm. |
| 1.10.2.8 | modified | starksm | tomcat/src/main/org/jboss/web/tomcat/security/JBossSecurityMgrRealm.java | Change the roleMap to a mapping from the caller principal to the GenericPrincipal rather than just the caller's roles. |
| 1.3.4.3 | modified | starksm | tomcat/src/main/org/jboss/web/tomcat/security/JBossGenericPrincipal.java | Keep the original Set<Princpal> of the user roles in addition to the role names. |
| 1.1.2.1 | modified | starksm | testsuite/src/resources/test-configs/jacc/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml | Add the SecurityManagerService attribute for testing the auth cache flushing. |
| 1.9.2.61 | modified | starksm | testsuite/imports/test-jars.xml | Add the cross-server.jar target |
| 1.9.2.60 | modified | loubyansky | testsuite/imports/test-jars.xml | ported ha local connection factory from HEAD |
| 1.2.2.1 | modified | loubyansky | testsuite/src/resources/jca/ha/test-ha-ds.xml | ported ha local connection factory from HEAD |
| 1.2.2.1 | modified | loubyansky | testsuite/src/main/org/jboss/test/jca/test/HAConnectionFactoryUnitTestCase.java | ported ha local connection factory from HEAD |
| 1.1.2.1 | modified | loubyansky | testsuite/src/main/org/jboss/test/jca/ejb/HAConnectionSessionBean.java | ported ha local connection factory from HEAD |
| 1.4.2.3 | modified | loubyansky | tools/etc/buildmagic/modules.xml | ported ha local connection factory from HEAD |
| 1.67.2.6 | modified | loubyansky | connector/build.xml | ported ha local connection factory from HEAD |
| 1.22.2.5 | modified | loubyansky | connector/src/resources/stylesheets/ConnectionFactoryTemplate.xsl | ported ha local connection factory from HEAD |
| 1.1.2.1 | modified | loubyansky | connector/src/resources/ha-local-rar/META-INF/ra.xml | ported ha local connection factory from HEAD |
| 1.1.2.4 | modified | loubyansky | connector/src/resources/dtd/jboss-ds_1_5.dtd | ported ha local connection factory from HEAD |
| 1.6.2.1 | modified | loubyansky | connector/src/main/org/jboss/resource/adapter/jdbc/local/HALocalManagedConnectionFactory.java | ported ha local connection factory from HEAD |
| 1.13.4.2 | modified | andd | system/src/main/org/jboss/system/server/ServerConfig.java | JBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console |
| 1.9.6.1 | modified | andd | system/src/main/org/jboss/system/server/ServerConfigImpl.java | JBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console |
| 1.47.2.4 | modified | andd | system/src/main/org/jboss/system/server/ServerImpl.java | JBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console |
| 1.4.6.1 | modified | andd | jmx/src/main/org/jboss/mx/util/MBeanServerLocator.java | JBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console |
| 1.75.2.3 | modified | andd | jmx/src/main/org/jboss/mx/server/MBeanServerImpl.java | JBAS-1610Implemented the ability to run jboss using the 'platform MBeanServer' on jdk1.5+ runtimes. Attribute ServerConfig.getPlatformMBeanServer() has been added to indicate if we are using the platform MBeanServer as the main jboss server. Both the 'jboss.platform.mbeanserver' property must be set, and the jvm must be jdk1.5+. to enable this feature. MBeanServerLocator will instead return the platform MBeanServer, in this case. To enable this feature use: './run -Djboss.platform.mbeanserver' and see the 'java.lang' and 'java.util.logging' domains appearing in the jmx-console |
