Once more regarding your quote "vickyk" wrote : ...the reauthentication would be decided at the RA level If an RA states that it support re-authentication, this does not mean per se that for a specific deployment re-authentication should be used --> this should be a deployment option, defined in -ds.xml. In a use case where the RA is called with few technical users, re-authentication might be too expensive, and a PoolBySubjectAndCri (or PoolBySubject) should be used. In another case with 1000 of end users, the same RA might be used with re-authentication. Since one does not know the internals of an RA, one also does not know how efficient re-authentication is implemented.
"vickyk" wrote : What I understand is that you wanted to keep the SubPoolCreation even when the re-authentication. | Yes, but only if the deployment (--> ds.xml) requires it (see above). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244954#4244954 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244954 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
