I have tried the latest code v1.2 with openLDAP configurations. I'm not able to login to the UI. Here's my ldap settings.
#LDAP
ldap.server=ldap://ldapserver:389/
#For openLDAP anonymous user ldap.user and ldap.password set to empty.
#For LDAP set values - ldap.user and ldap.password
ldap.user=
ldap.password=
ldap.searchbase=dc=maxcrc,dc=com
ldap.distributionlist=
#For ldap isLDAP set to true
ldap.isLDAP=true
#For openldap isopenLDAP set to true
ldap.isopenLDAP=true
This is the error in tomcat logs.
24-Nov-2017 09:57:47.950 SEVERE [http-nio-8443-exec-1] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [com.cognizant.buildon.controller.AuthenticationWebController] in context with path [/buildon] threw exception
java.lang.NullPointerException
at com.cognizant.buildon.domain.LDAPAuthentication.getEmpId(LDAPAuthentication.java:294)
at com.cognizant.buildon.controller.AuthenticationWebController.doPost(AuthenticationWebController.java:289)
Hi,
I have tried to setup the openldap with latest code base.
But login not succeeded.
2017-12-04 12:40:15 [http-nio-8443-exec-6] DEBUG c.m.v.resourcepool.BasicResourcePool - awaitAvailable(): [unknown]
2017-12-04 12:40:16 [http-nio-8443-exec-6] DEBUG c.c.b.domain.LDAPAuthentication - javax.naming.NotContextException: Not an instance of DirContext
2017-12-04 12:40:27 [DefaultQuartzScheduler_QuartzSchedulerThread] DEBUG o.quartz.core.QuartzSchedulerThread - batch acquisition of 0 triggers
Here's is my LDAP setttings
#LDAP
ldap.server=ldap://ldapserver:389
#For openLDAP anonymous user ldap.user and ldap.password set to empty.
#For LDAP set values - ldap.user and ldap.password
ldap.user=Manager
ldap.password=password
ldap.searchbase=dc=maxcrc,dc=com
ldap.distributionlist=
#For ldap isLDAP set to true
ldap.isLDAP=true
#For openldap isopenLDAP set to true
ldap.isopenLDAP=true
I tried to turn OFF the web-hook and I can modify the Jenkins file through Jenkinsfile editor and check-in.
When web-hook is turned ON I can commit the Jenkins file through editor. What is the significance of this ON option?Will it trigger build on automatically?
I have enabled LDAP for authentication. But when I try to login to the buildon ui the authentication is failing with "invalid credentials" and shows below error on buildonui.log
07:26:25.663 [http-nio-8443-exec-9] DEBUG c.c.b.domain.LDAPAuthentication - javax.naming.InvalidNameException: [LDAP: error code 34 - invalid DN]
07:26:25.663 [http-nio-8443-exec-9] DEBUG c.c.b.domain.LDAPAuthentication - javax.naming.NotContextException: Not an instance of DirContext
The pipeline view is not working in historical reports for buildon triggered via github webhook framework.
I have found an exception on tomcat localhost log
11-Dec-2017 12:48:08.420 SEVERE [http-nio-8443-exec-9] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [com.cognizant.buildon.controller.HistoricCIWebController] in context with path [/buildon] threw exception
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:657)
at java.util.ArrayList.get(ArrayList.java:433)
at com.cognizant.buildon.domain.GitOperations.gethistoricalBranch(GitOperations.java:1229)
at com.cognizant.buildon.controller.HistoricCIWebController.doPost(HistoricCIWebController.java:277)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
Team,
I have installed buildon UI v1.2 with local DB authentication.
I'm using the latest image "devopsbasservice/buildonframework:buildonJenkinsfile2.0" in Jenkinsfile.
I'm able to configure SCM and buildon is failing with few errors. Attaching the buildonui & framework log for your reference buildon_rollingfile.2017-11-28.0.log