Hello! Our LDAP authorization module offers some configuration options, but not enough to do what you want I think. Allura uses "auth.ldap.admin_dn" to bind in some situations, but for validating and setting passwords, it uses the current user. Does that not work for your LDAP setup? How would you want it to work?
The schroot_name option only works if you have use_schroot enabled and requires various other installations requirements documented at https://forge-allura.apache.org/docs/getting_started/scm_host_ssh.html That process hasn't been used by anyone for a while, and I am not familiar with it, so it likely won't work. IIRC its main purpose was to make code repositories share authentication with Allura (and there are other options for that too). I've seen the python version mismatch message too. I think it is just informative, its never caused any problems that I know of. -Dave On 6/5/20 6:31 AM, Tony Hung wrote: > 1. When I use LDAP as my authentication method. The Allura sent user login > credential to LDAP instead of sent the "auth.ldap.schroot_name" I put in the > "development.ini" during Ldap bind request step. I think the user ID should > be send after bind request success. > > 2. When I use command "docker-compose logs http" > It seems apache python module is conflict with python version. > > [:error] [pid 1:tid 139749974105024] python_init: Python version mismatch, > expected '2.7.6', found '2.7.17'. > [:error] [pid 1:tid 139749974105024] python_init: Python executable found > '/usr/bin/python'. > [:error] [pid 1:tid 139749974105024] python_init: Python path being used > '/usr/lib/python2.7:/usr/lib/python2.7/plat-x86_64-linux-gnu:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload'. > -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
