DS 389 ~/.dsrc file not working after OpenSuSE 15.6 upgrade

[guindos]

Hello.

Yesterday I upgrade my OpenSuSE 15.6 machine where I have a DS389 working. Since then, the system ignores the existence of the ~/.dsrc file. When giving, for example a simple:

dsidm ldapint user list

It will ask me for the basedn, althought I have it well defined inside ~/.dsrc:

[ldapint]
uri = ldapi://%%2fvar%%2frun%%2fslapd-ldapint.socket
basedn = dc=example,dc=com
binddn = cn=Directory Manager

If I debug (-v) the command I see some weird things. In principle, it seems to read correctly the file. But seems to give the command line a higher precedence over the .dsrc file:

DEBUG: dsrc instances: [‘ldapint’]
DEBUG: dsrc completed with {‘args’: {‘server-id’: ‘ldapint’, ‘ldapurl’: ‘ldapi://%2fvar%2frun%2fslapd-ldapint.socket’, ‘root-dn’: ‘cn=Directory Manager’, ‘ldapi_enabled’: ‘on’, ‘ldapi_socket’: ‘2fvar%2frun%2fslapd-ldapint.socket’, ‘ldapi_autobind’: ‘on’}, ‘uri’: ‘ldapi://%2fvar%2frun%2fslapd-ldapint.socket’, ‘basedn’: ‘dc=example,dc=com’, ‘people_rdn’: None, ‘groups_rdn’: None, ‘binddn’: ‘cn=Directory Manager’, …
DEBUG: Called with: Namespace(basedn=None, binddn=None, …

The comnmand with -b “dc=example,dc=com” works as expected.

Previous to the upgrade, the system was reading .dsrc normally and I hadn’t to use -b.

Does anyone know if something has changed on the last SuSE upgrade?

Is there a simple way of having the previous behaviour?

Thanks

[guindos]

Hello.
This is an update. I have tested the system with and without security patches.
With patches, the response to the command dsidm ldapint -v user list is exactly the same as without patches except the last part:

-------------- WITH PATCHES:

vendorVersion: 389-Directory/2.2.10 B2024.225.1200

]
Enter basedn :

As you can see, after showing the version it asks for the basedn.

----------------- WITHOUT PATCHES:

vendorVersion: 389-Directory/2.2.9 B2024.044.1200

]
DEBUG: dsrc path: /root/.dsrc
DEBUG: dsrc container path: /data/config/container.inf
DEBUG: dsrc instances: [‘ldapint’]
DEBUG: dsrc completed with {‘args’: {‘server-id’: ‘ldapint’, ‘ldapurl’: ‘ldapi://%2fvar%2frun%2fslapd-ldapint.socket’, ‘root-dn’: ‘cn=Directory Manager’, ‘ldapi_enabled’: ‘on’, ‘ldapi_socket’: ‘2fvar%2frun%2fslapd-ldapint.socket’, ‘ldapi_autobind’: ‘on’}, ‘uri’: ‘ldapi://%2fvar%2frun%2fslapd-ldapint.socket’, ‘basedn’: ‘dc=example,dc=com’, ‘people_rdn’: None, ‘groups_rdn’: None, ‘binddn’: ‘cn=Directory Manager’, ‘saslmech’: None, ‘tls_cacertdir’: None, ‘tls_cert’: None, ‘tls_key’: None, ‘tls_reqcert’: None, ‘starttls’: False, ‘pwdfile’: None, ‘prompt’: False}
DEBUG: list filter = (&(objectclass=nsPerson)(objectclass=nsAccount)(objectclass=nsOrgPerson)(objectclass=posixAccount))
DEBUG: Retrieving entry with [(‘’,)]
DEBUG: Retrieved entry [dn:
vendorVersion: 389-Directory/2.2.9 B2024.044.1200

]

and the command shows all the list of users.

Without the security patches, the -v shows that the system re-reads the .dsrc file

Without the patches, the version shown is: 389-Directory/2.2.9 B2024.044.1200, while with the patches applied it is: 389-Directory/2.2.10 B2024.225.1200

So, what happened after installing this ds-389 upgrade that now it is not re-reading the .dsrc file?

Is there a way for convincing the system to take into account that file?

Thanks a lot