[JBoss JIRA] (JBJCA-1004) Subject / security domain overrides null values from CRI for a datasource with allow-multiple-users
by Ivo Studensky (JIRA)
Ivo Studensky created JBJCA-1004:
------------------------------------
Summary: Subject / security domain overrides null values from CRI for a datasource with allow-multiple-users
Key: JBJCA-1004
URL: https://issues.jboss.org/browse/JBJCA-1004
Project: IronJacamar
Issue Type: Bug
Components: JDBC
Affects Versions: 1.0.15.Final
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Fix For: 1.0.16.Final
An issue cloned from JBPAPP6-1323 for the upstream.
DataSource configured with security-domain using org.picketbox.datasource.security.CallerIdentityLoginModule is able to create correct connection
when one of ds.getConection(username, password) is set to null.
Null parameter is substituted using value of corresponding field from the security-domain.
The datasource is defined using <allow-multiple-users/>.
See test org.jboss.as.test.integration.jca.security.DsWithCallerIdentityLoginModuleTestCase at https://github.com/pskopek/jboss-as/tree/JBPAPP-9583.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6724) method-params containing an array not correctly processed for EJB2.1 with CMT
by Robert Panzer (JIRA)
[ https://issues.jboss.org/browse/AS7-6724?page=com.atlassian.jira.plugin.s... ]
Robert Panzer commented on AS7-6724:
------------------------------------
I think I found the problem.
Seems to be related to mismatches between Class.getName() and Class.getCanonicalName().
I am preparing a fix and will send a pull request.
> method-params containing an array not correctly processed for EJB2.1 with CMT
> -----------------------------------------------------------------------------
>
> Key: AS7-6724
> URL: https://issues.jboss.org/browse/AS7-6724
> Project: Application Server 7
> Issue Type: Feature Request
> Components: EJB
> Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final)
> Environment: JBoss 7.2.0-Final Prerelease (Commit 4ed76c) and JBoss 7.1.3.Final on Win7/64 JDK 1.7.0_09
> Reporter: Robert Panzer
> Assignee: jaikiran pai
> Attachments: cmt-never-array-params.zip
>
>
> It seems that the method-params for container transactions are not matched correctly if the contain arrays.
> I've got an EJB "First" that calls another EJB "Second". Both have the same interface containing a method void test(String[]);
> If I define the transaction attribute NEVER including method-params for "First" and without params for "Second" the test fails with
> JBAS014163: Transaction present on server in Never call (EJB3 13.6.2.6)
> I define the container transaction like this:
> <container-transaction>
> <method>
> <ejb-name>FirstWithParams</ejb-name>
> <method-intf>Local</method-intf>
> <method-name>test</method-name>
> <method-params>
> <method-param>java.lang.String[]</method-param>
> </method-params>
> </method>
> <method>
> <ejb-name>FirstWithParams</ejb-name>
> <method-intf>Local</method-intf>
> <method-name>test</method-name>
> <method-params>
> <method-param>java.lang.String</method-param>
> </method-params>
> </method>
> <method>
> <ejb-name>FirstWithParams</ejb-name>
> <method-intf>Local</method-intf>
> <method-name>test</method-name>
> <method-params>
> <method-param>int</method-param>
> </method-params>
> </method>
> <method>
> <ejb-name>Second</ejb-name>
> <method-intf>Local</method-intf>
> <method-name>test</method-name>
> </method>
> <trans-attribute>Never</trans-attribute>
> </container-transaction>
> I will attach a test case that fails at the call to test(String[]) but successfully call test(String) and test(int).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-6316) Review of AccessController and PrivilegedAction use across AS7
by Dimitris Andreadis (JIRA)
[ https://issues.jboss.org/browse/AS7-6316?page=com.atlassian.jira.plugin.s... ]
Dimitris Andreadis commented on AS7-6316:
-----------------------------------------
No, everything in old jboss-* was bad, we need to reinvent the wheel. :-)
> Review of AccessController and PrivilegedAction use across AS7
> --------------------------------------------------------------
>
> Key: AS7-6316
> URL: https://issues.jboss.org/browse/AS7-6316
> Project: Application Server 7
> Issue Type: Task
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 8.0.0.Alpha1
>
>
> The following needs reviewing across AS7: -
> - On demand instantiation of PrivilegedActions where singletons would suffice (Consider frequency of calls, gc may be preferable).
> - Use of AccessController even though there is no SecurityManager set.
> - Code duplication, in every case I have seen so far the code is the same regardless of if PRIVILEGED or NON_PRIVILEGED
> - Utility methods with visibility too high.
> - In depth review of the other methods, i.e. if the first thing a public method does is set the class loader based on a parameter passed in it could be used badly - it may even be a justification for that method to NOT use a PrivilegedAction.
> - Code that requires to be executed using a PrivilegedAction should also be double checked that it is not doing too much as the identity of the caller.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (AS7-5663) CLONE - System properties are currently unusable for setting a connector's proxy-name
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-5663?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-5663:
----------------------------------------------
Radim Hatlapatka <rhatlapa(a)redhat.com> changed the Status of [bug 900961|https://bugzilla.redhat.com/show_bug.cgi?id=900961] from ON_QA to VERIFIED
> CLONE - System properties are currently unusable for setting a connector's proxy-name
> -------------------------------------------------------------------------------------
>
> Key: AS7-5663
> URL: https://issues.jboss.org/browse/AS7-5663
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Domain Management, Web
> Affects Versions: 7.1.1.Final
> Environment: -JBoss Enterprise Application Platform (EAP) 6.0.0
> Reporter: Aaron Ogburn
> Assignee: Tomaz Cerar
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
>
> A connector's proxy-name cannot be set through system properties currently in the web subsystem:
> ==domain.xml==
> <subsystem xmlns="urn:jbossomain:web:1.1" default-virtual-server="default-host" instance-id="${jboss.node.name}"
> native="false">
> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" proxy-name="${jboss.proxy.name}"/>
> The property is never parsed though and
> request.getServerName() just returns ${jboss.node.name}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month