Le 06/01/16 15:00, Jan Sindberg a écrit : > If there is no connection to the LDAP, then it is no longer possible to > create an AccessMgrFactory. > > First we get: > org.apache.directory.fortress.core.CfgRuntimeException: static init: Error > loading from cfg file: [fortress.properties] > SecurityException=org.apache.directory.fortress.core.FinderException: > getConfig dn [cn=DEFAULT,ou=Config,dc=example,dc=com] caught > LdapException=INVALID_CREDENTIALS: Bind failed: ERR_316 Directory service is > not started., errCode=127 > > On subsequent calls we get: > java.lang.NoClassDefFoundError: Could not initialize class > org.apache.directory.fortress.core.AccessMgrFactory > > Is there a way to handle this and make the Fortress core api reconnect later?
Complicated... Fortress is storing all the Authz information in a remote server, and if it's not reachable, then you won't be able to make any decision. AFAIR, we had internal discussion about setting up a local cache within the API to allow Fortress to keep going even if the remote LDAP server is down. I'm not sure it's in Fortress atm, and I'm not sure we decided anything about such an addition... Shawn ?
