davidcoutadeur

I have fixed last small issues, and tested an installation + an upgrade scenario. Everything seems fine. I am merging this

Hello @opoplawski, As explained in release notes, we have proceeded to some cleaning in the configuration files. As you may have noticed, the configuration have been moved to /etc/self-service-password. We...

See also https://github.com/lsc-project/lsc/issues/216

Seems all fine for me, but I could run the test because of https://github.com/lsc-project/lsc/pull/238#issuecomment-1770175306 We need to run the test when fixed.

Tests are successful. Everything seems fine to me!

Ok, if it is not mandatory for DB -> LDAP or LDAP -> LDAP. By the way, it can be interesting to give a look to the code to understand...

I don't reproduce with a hsqldb -> ldap connector. Maybe this is specific to a special database. The bug was found on a DB2 -> LDAP connector

> Thanks for the quick reply, I've pushed the changes for the optimized FORCE policy at https://github.com/INTM-Group/lsc/tree/opti-force-policy, you can review them and make a PR directly from our branch, afaik....

> Hello, > > We tried to package the application and tested it on our test platform. Unfortunately this doesn't seem to work. The contents of the member "attribute" is...

This PR is replaced by #285