Can anyone suggest me with any findings on this issue .
The page is not loading and all the users are complaining on this issue .
Cybersecurity
DevOps Cloud
IT Operations Cloud
Can anyone suggest me with any findings on this issue .
The page is not loading and all the users are complaining on this issue .
Do you have a compound index in this order, CDSID,GIvenName, surname, email,Full Name which by the way is a TERRIBLE idea to index. All the attributes in that field need to have a matching compound index for the pattern shown in the text entry box. I recommend trimming down the search criteria seriously and making a much simpler compound index.
We have all the attributes indexed for all the servers .Can you please guide me the proper way to index as while connecting to Apache Directory also we get issue and we need to try 5 to 6 times to connect to eDirectory.
Can you show me the indexDefinition from the NCP Server object, via Apache DS for the index I asked about?
Do you know the difference between a compound and regular index? User App wants to use server side sort and virtural list views to 'cheat' on how it displays and allows sorting of columns, by using eDir compound indexes, which is kind of clever, but requires some fairly 'expensive' indexes.
Now Apache DS having trouble connecting is a much more fundamental problem. That is not a good thing. What errors do you get? Is this a routing issue or a cert issue do you think?
I get this error when trying open an LDAP connection and after 6 to 7 attempts I am login in .
Looks like the LDAP issue is known with the Apache directory tool, Related to TLS 1.3. Check out this article on Server Fault https://stackoverflow.com/questions/73689042/why-authentication-fails-with-starttls-connection-in-apache-directory-studio#73693495
The specific item I wanted to see was the indexDefinition for the specific index.
Here is one of mine for a compound index:
0$AncidGnSnCn$0$0$0$1$ancestorID$given name$surname$cn
That is Given Name, Surname and CN (AncestorID is a long story).
I just want to confirm you have one.
What you can do is in ndstrace on the server, enable LDAP trace. Trace it to a file, since it is going to zoom by with all the LDAP traffic (On the LDAP server/Group object, enable all the tracing options, even hexdump, their meanings have changed so don't worry about it) and if you do not have the index, it will complain on each search that there is a missing index.