D4Science Infrastructure

according to @g.panichi@isti.cnr.it the issue isn't solved, either the password is not the previous one (unlikely) or the solution adopted is not the correct one. I think we should either contact ENG or find who followed this work CNR side.

@paolo.fabriani@eng.it @ciro.formisano@eng.it could you help us here? Which is the SVN user (and how it is retrieved in the code) involved in the DataMiner algorithms auto deployment on production?

There is an authentication problem for the svn.d4science user, on dm-pool-manager-* service:

gcube@dm-pool-manager-proto:~$ svn list https://svn.d4science.research-infrastructures.eu/gcube/trunk/data-analysis/DataMinerConfiguration/algorithms
Authentication realm: <https://svn.d4science.research-infrastructures.eu:443> D4Science SVN
Password for 'svn.d4science': **********

Authentication realm: <https://svn.d4science.research-infrastructures.eu:443> D4Science SVN
Username:

I've found the problem. The ldap users were filtered using the posixAccount objectclass. I did not add that object class to the svn.d4science user, as it's not a real user.
Now subversion authenticates against inetorgPerson.
I just tried on the proto dm pool manager and it works.

Folks, I have modified the version of DM pool manager in dev environment to get SVN credentials from the IS. In particular, on the Generic Resource DMPMConfigurator of NextNext I have included the elements:

<svn.repository.username>svn.d4science</svn.repository.username>

<svn.repository.password>D4U534_5vN</svn.repository.password>

And it seems to work.
Please, make more tests if you can: if everything will be OK I will prepare the new version for the next release.

PS: it is backward compliant with the previous version, so if you remove the elements from the IS it will get the credentials from local svn config files.