Thanks for helping me during this aventure,
So, I did some tests :
On ubuntu (@Home || @Work on a VM) :
OpenAM (default configuration) + GateIn Tomcat : OK
OpenAM (default configuration) + GateIn JBoss : OK
OpenAM (default configuration) + ExoPlatform : OK
OpenAM (manual configuration) + GateIn Tomcat : OK
OpenAM (manual configuration) + GateIn JBoss : OK
OpenAM (manual configuration) + ExoPlatform : OK
On Windows :
OpenAM (default configuration) : Impossible to install it, there is an existing GIRA for this point.
OpenAM (manual configuration) + GateIn Tomcat : KO, cf. point 4.
OpenAM (manual configuration) + GateIn JBoss : KO, cf. point 4.
OpenAM (manual configuration) + ExoPlatform : KO, cf. point 4.
Note : 1) The difference between the manual and the default configuration is the domain name. All my tests are on a local machine. In the default configuration, OpenAM use the domain name "localhost" contrary to the manual configuration where you can't choose the domain name. In this case, I've chosen a domain name that points on the localhost (in Windows, I modified the hosts file for example and added a domain name for 127.0.0.1)
2) I tested ExoPlatform because GateIn have some similar codes since GateIn comes from ExoPlatform and JBoss Portal.
3) In the documentation, the syntax of the jaas.conf file is false, the right way to write it is :
// org.exoplatform.web.security.PortalLoginModule required;
// org.exoplatform.services.security.jaas.SharedStateLoginModule required;
// org.exoplatform.services.security.j2ee.TomcatLoginModule required;
// Uncomment the following part (and comment the other part for CAS integration
4) When the result is KO, it's appears the bug is the blank plage or the loop on the blank page that I described earlier. OpenAM, after a successful authentification, redirects you to the portal and in the portal something fails... May be the validation of the cookie or something like that, if you have any idea, please share it.
5) For the manual configuration, the chosen domain is : .vauban.com but in the cookies the domain writen in the cookie is localhost... Not strange because in the /etc/hosts or /Windows/system32/drivers/etcs/hosts/ 127.0.0.1 refers to localhost and/or openam.vauban.com.But when it's KO, the cookie has the domain .vauban.com in the cookie.
Conclusion ???? : I need some helps to "understand" why in Windows, it's so impossible....