Submitted by ahcene.chh on Thu, 08/10/2023 - 17:39
I'm working with bonita community edition 7.x trying to implement an LDAP authentication with bonita engine and no matter the configuration and jars i add, the bonita engine just doesn't respond, i couln't change the default authentication on bonita and i was wondering if there's anyone with a similar problem and if they did change the bonita's default Authentication method to teach me how to do it.
Submitted by fatoumatacissoko22 on Fri, 04/15/2016 - 16:37
j'installe bonita sur un server et j'utlise la version 7 et tomcat 7 aussi j'ai reussi a avoir le portail mais j'arrive pas à m'authentifier. pouvez vous me dire svp s'il ya d'autre configuration a faire.le LoginModule ou se trouve t-il? ci dessous vous avez mon fichier log de bonita.
merci d'avance !
Submitted by ruben_zornoza on Thu, 04/03/2014 - 12:28
Hello everyone,
I'm trying to configure a JAAS authentication in a Bonita 6.2.5 Community Tomcat bundle but it seems that i can not change the login module.
I have changed the LoginManager at "BonitaBPMCommunity-6.2.5-Tomcat-6.0.37\bonita\client\platform\conf\loginManager-config.properties" to org.bonitasoft.console.common.server.login.impl.jaas.JAASLoginManagerImpl
I enabled the SECURITY_OPTS at setenv.bat and I added it to the CATALINA_OPTS:
In previous versions of Bonita (5.*) there wasn't any need for user accounts to actualy exist in Bonita Portal. What if I don't want to use LDAP/AD authentication but some custom third party authentication mechanism which doesn't expose users through LDAP protocol? How can I overcome the need for user existence within portal?
In 5.* releases Bonita supported authentication mechanisms like Jasig CAS for example. This isn't available in 6.* community editions anymore?