Yes, the instructions are still the same (if a little scant of details :-).
It's basically:
1) A configuration option in BaseWrapperManagedConnectionFactory
to define the reauthentication mechanism class
2) Define an interface in org.jboss.resource.adapter.jdbc.vendor for the
reauthentication
mechanism, e.g. something like:
| public interface ReauthenticationMechansim
| {
| void reauthenticate(Connection c, String user, String password) throws
SQLException;
| }
|
3) Invocation of the reauthentication during matchManagedConnections()
and suppression of any failure to match of the CRI/Subject.
4) An option on the JBossManagedConnectionPool to tell it to reduce the pooling
to one-pool since multiple pools (for different users/passwords - subjects) are
no longer required.
5) Change the xslt to have a <reauthentication-mechanism>some.class.name</>
for data-sources that does the configuration for both (1) and (4)
Actually (4) is probably a bit more complicated for generic pooling where
the CRI (connection request info) can have other parameters besides
user/password. e.g. the JMS rar has queue/topic connection,
but making it work for the JDBC adapter will be a good start.
And (3) needs some care to make sure errors thrown by the reauthenication
mechanism are handled properly, i.e. don't match the conneciton so it is then
destroyed as broken.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052600#4052600
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052600
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
