Currently OID is the target LDAP provider
Paging access (added 6 months ago) so that over 1000 entries will not get truncated seems to be causing problems on unpatched OID11 - though I tested it against patched OID 11 and OID 12 .
I have been asking people with issues to contact support - if the issue is prioritised I may get a broken setup to test against. If I sense a paging error for example - I could try a non paged version (getting large number of results truncated is better than no results).
Some guy managed to get OUD working by allowing paging (Third party link removed)
Note that
1/ you can supply context in ldap.ora
2/ you can give exact match in the dbservice combo box (and download the single connection details without searching for all services in a context)
I was hoping this might help for LDAPs that do not allow root searching (ODSEE?) (or do not have paged access)
These LDAP considerations apply to the SQLDeveleoper specific LDAP UI for searching for entries - you could always use the advanced URL for LDAP (thick and thin have different syntax).
Also 6 months ago we fixed:
Kerberos Active Directory default login ticket support on windows (give cache as blank i.e. "" (without the quotes)) - was tested with a configuration file with thin jdbc . (You could have, and still can, use thick kerberos and sqlnet.ora configuration)
Paging access (added 6 months ago) so that over 1000 entries will not get truncated seems to be causing problems on unpatched OID11 - though I tested it against patched OID 11 and OID 12 .
I have been asking people with issues to contact support - if the issue is prioritised I may get a broken setup to test against. If I sense a paging error for example - I could try a non paged version (getting large number of results truncated is better than no results).
Some guy managed to get OUD working by allowing paging (Third party link removed)
Note that
1/ you can supply context in ldap.ora
2/ you can give exact match in the dbservice combo box (and download the single connection details without searching for all services in a context)
I was hoping this might help for LDAPs that do not allow root searching (ODSEE?) (or do not have paged access)
These LDAP considerations apply to the SQLDeveleoper specific LDAP UI for searching for entries - you could always use the advanced URL for LDAP (thick and thin have different syntax).
Also 6 months ago we fixed:
Kerberos Active Directory default login ticket support on windows (give cache as blank i.e. "" (without the quotes)) - was tested with a configuration file with thin jdbc . (You could have, and still can, use thick kerberos and sqlnet.ora configuration)
