We have developped a keycloak-crowd wrapper. In all applications this works perfectly, but in DMA it gives a lot of problems: especially after sending the message DMSNotifications.NT_REFRESH_LDAP, it very often times out, does not find all users,…
Customers are very annoyed.
So if we know more details of what exactly happen when the message DMSNotifications.NT_REFRESH_LDAP is sent, we hopefully can fix some of these issues.
Hello Cristel,
maybe you could try using SLNetClientTest tool to see what is actually being sent and to further understand what might be an issue. I would suggest starting with this. I would assume the issue is misconfigured call of NT_REFRESH_LDAP and this should help you with that.
Always be extremely careful when using the SLNetClientTest tool, as it can have far-reaching consequences on the functionality of your DataMiner System.
Please let me know if this helps or if you need anything else.
Cheers
Thanks, I have passed this suggestion to the customer.
In the mean time they are looking for a workaround, and they think increasing the timeout(s) DMA 10.1 uses while processing the DMSNotifications.NT_REFRESH_LDAP call.
(I have created a separate dojo question for this : https://community.dataminer.services/question/can-the-timeouts-used-inside-dmsnotifications-nt_refresh_ldap-be-changed-how/)
They are also wondering whether they can increase the timeout. If yes : how ?