{"id":13118,"date":"2019-12-08T08:00:28","date_gmt":"2019-12-08T07:00:28","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/"},"modified":"2019-12-08T08:00:28","modified_gmt":"2019-12-08T07:00:28","slug":"documentum-ldap-config-object-certdb_location-has-invalid-value","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/","title":{"rendered":"Documentum &#8211; LDAP Config Object &#8220;certdb_location&#8221; has invalid value"},"content":{"rendered":"<p>In a <a href=\"https:\/\/www.dbi-services.com\/blog\/documentum-automatic-silent-creation-of-ldap-ldaps-server-config-objects\/\" target=\"_blank\" rel=\"noopener noreferrer\">previous blog<\/a>, I talked about the automation of the LDAP\/LDAPs creation. However, the first time that I applied these steps, I actually faced an issue and I couldn&#8217;t really get my head around it, at first. This will be a rather short post but I still wanted to share my thoughts because it might avoid you some headache. The issue is only linked to the SSL part of the setup so there is no problem with the basis non-secure LDAP communications.<\/p>\n<p>So, after applying all the steps, everything went fine and I therefore tried to run the <em>dm_LDAPSynchronization<\/em> job to validate the setup. Doing so, the generated log file wasn&#8217;t so great:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [17,21,22,23,64]\">[dmadmin@content-server-0 ~]$ cat $DOCUMENTUM\/dba\/log\/repo01\/sysadmin\/LDAPSynchronizationDoc.txt\nLDAPSynchronization Report For DocBase repo01 As Of 2019\/09\/22 12:45:57\n\n2019-09-22 12:45:56:124 UTC [default task-79]: LDAP Synchronization Started @ Sun Sep 22 12:45:56 UTC 2019\n2019-09-22 12:45:56:124 UTC [default task-79]:\n2019-09-22 12:45:56:124 UTC [default task-79]: $JMS_HOME\/server\/DctmServer_MethodServer\/deployments\/ServerApps.ear\/lib\/dmldap.jar\n2019-09-22 12:45:56:125 UTC [default task-79]: ---------------------------------------------------------------------------------\n2019-09-22 12:45:56:125 UTC [default task-79]: Product-Name : Content Server-LDAPSync\n2019-09-22 12:45:56:125 UTC [default task-79]: Product-Version : 16.4.0110.0167\n2019-09-22 12:45:56:125 UTC [default task-79]: Implementation-Version : 16.4.0110.0167\n2019-09-22 12:45:56:125 UTC [default task-79]: ---------------------------------------------------------------------------------\n2019-09-22 12:45:56:125 UTC [default task-79]:\n2019-09-22 12:45:56:126 UTC [default task-79]: Preparing LDAP Synchronization...\n2019-09-22 12:45:57:101 UTC [default task-79]: INFO: Job Status: [LDAP Synchronization Started @ Sun Sep 22 12:45:56 UTC 2019]\n2019-09-22 12:45:57:120 UTC [default task-79]: INFO: Job Status updated\n2019-09-22 12:45:58:415 UTC [default task-79]: INFO: List of Ldap Configs chosen for Synchronization\n2019-09-22 12:45:58:415 UTC [default task-79]: INFO:    &gt;&gt;&gt;0812d6878000252c - Internal_LDAP&lt;&lt;&lt;\n2019-09-22 12:45:58:415 UTC [default task-79]: INFO:\n2019-09-22 12:45:58:418 UTC [default task-79]:\n2019-09-22 12:45:58:418 UTC [default task-79]: ==================================================================================\n2019-09-22 12:45:58:420 UTC [default task-79]: Starting Sychronization for ldap config object &gt;&gt;&gt;Internal_LDAP&lt;&lt;&lt; ...\n2019-09-22 12:45:58:425 UTC [default task-79]: Unexpected Error. Caused by: [DM_LDAP_SYNC_E_EXCEPTION_ERROR]error:  \"Ldap Config Property \"certdb_location\" has invalid value \"ldap_chain\".\"\n2019-09-22 12:45:58:426 UTC [default task-79]: ERROR: DmLdapException:: THREAD: default task-79; MSG: [DM_LDAP_SYNC_E_EXCEPTION_ERROR]error:  \"Ldap Config Property \"certdb_location\" has invalid value \"ldap_chain\".\"; ERRORCODE: 100; NEXT: null\n        at com.documentum.ldap.internal.sync.SynchronizationContextBuilder.getCertDbLocation(SynchronizationContextBuilder.java:859)\n        at com.documentum.ldap.internal.sync.SynchronizationContextBuilder.setCertDbLocation(SynchronizationContextBuilder.java:225)\n        at com.documentum.ldap.internal.sync.SynchronizationContextBuilder.buildSynchronizationContext(SynchronizationContextBuilder.java:49)\n        at com.documentum.ldap.LDAPSync.prepareSync(LDAPSync.java:438)\n        at com.documentum.ldap.LDAPSync.processJob(LDAPSync.java:238)\n        at com.documentum.ldap.LDAPSync.execute(LDAPSync.java:80)\n        at com.documentum.mthdservlet.DfMethodRunner.runIt(Unknown Source)\n        at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)\n        at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)\n        at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)\n        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)\n        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n        at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86)\n        at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)\n        at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)\n        at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)\n        at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)\n        at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)\n        at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)\n        at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)\n        at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)\n        at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)\n        at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58)\n        at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:72)\n        at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)\n        at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76)\n        at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)\n        at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)\n        at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)\n        at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)\n        at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:282)\n        at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:261)\n        at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80)\n        at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:172)\n        at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)\n        at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774)\n        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)\n        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)\n        at java.lang.Thread.run(Thread.java:745)\n\n2019-09-22 12:45:58:426 UTC [default task-79]: WARNING:   **** Skipping Ldap Config Object - Internal_LDAP ****\n2019-09-22 12:45:58:775 UTC [default task-79]: Synchronization of ldap config object &gt;&gt;&gt;Internal_LDAP&lt;&lt;&lt; is finished\n2019-09-22 12:45:58:775 UTC [default task-79]: ==================================================================================\n2019-09-22 12:45:58:775 UTC [default task-79]:\n2019-09-22 12:45:58:786 UTC [default task-79]: INFO: Job Status: [dm_LDAPSynchronization Tool had ERRORS at 2019\/09\/22 12:45:58. Total duration was 2 seconds.View the job's report for details.]\n2019-09-22 12:45:58:800 UTC [default task-79]: INFO: Job Status updated\n2019-09-22 12:45:58:800 UTC [default task-79]: LDAP Synchronization Ended @ Sun Sep 22 12:45:58 UTC 2019\n2019-09-22 12:45:58:800 UTC [default task-79]: Session s2 released successfully\nReport End  2019\/09\/22 12:45:58\n[dmadmin@content-server-0 ~]$<\/pre>\n<p>&nbsp;<\/p>\n<p>After a bunch of checks inside the repository, everything seemed fine. All the objects had the correct content, the correct references, aso&#8230; However there was one thing that wasn&#8217;t exactly as per the <a href=\"https:\/\/knowledge.opentext.com\/knowledge\/cs.dll\/kcs\/kbarticle\/view\/KB6321243\" target=\"_blank\" rel=\"noopener noreferrer\">KB6321243<\/a> and that was the extension of the Trust Chain file. If you look at the basis of SSL Certificate encodings, then there are two main possibilities: <em>DER<\/em> (binary = not readable) or <em>PEM<\/em> (ASCII = readable). In addition to that, you can also have files with <em>CRT<\/em> or <em>CER<\/em> extensions but they are always either <em>DER<\/em> or <em>PEM<\/em> encoded. The KB asks you to have a <em>PEM<\/em> encoded SSL Certificate so this file can technically have either a &#8220;<em>.pem<\/em>&#8221; or &#8220;<em>.cer<\/em>&#8221; or &#8220;<em>.crt<\/em>&#8221; extension, that&#8217;s almost synonymous. Therefore, here I was, thinking that I could keep my &#8220;<em>.crt<\/em>&#8221; extension for the PEM encoded SSL Trust Chain.<\/p>\n<p>To validate that this was the issue, I switched my file to the &#8220;<em>.pem<\/em>&#8221; extension and updated the &#8220;<em>dm_location<\/em>&#8221; Object:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [2,22,23,24,29,33]\">[dmadmin@content-server-0 ~]$ cd $DOCUMENTUM\/dba\/secure\/ldapdb\n[dmadmin@content-server-0 ldapdb]$ mv ldap_chain.crt ldap_chain.pem\n[dmadmin@content-server-0 ldapdb]$ \n[dmadmin@content-server-0 ldapdb]$ iapi repo01 -U${USER} -Pxxx\n\n\n        OpenText Documentum iapi - Interactive API interface\n        Copyright (c) 2018. OpenText Corporation\n        All rights reserved.\n        Client Library Release 16.4.0110.0058\n\nConnecting to Server using docbase repo01\n[DM_SESSION_I_SESSION_START]info:  \"Session 0112d68780001402 started for user dmadmin.\"\n\nConnected to OpenText Documentum Server running Release 16.4.0110.0167  Linux64.Oracle\nSession id is s0\nAPI&gt; retrieve,c,dm_location where object_name='ldap_chain'\n...\n3a12d68780002522\nAPI&gt; get,c,l,file_system_path\n...\n$DOCUMENTUM\/dba\/secure\/ldapdb\/ldap_chain.cer\nAPI&gt; set,c,l,file_system_path\nSET&gt; $DOCUMENTUM\/dba\/secure\/ldapdb\/ldap_chain.pem\n...\nOK\nAPI&gt; get,c,l,file_system_path\n...\n$DOCUMENTUM\/dba\/secure\/ldapdb\/ldap_chain.pem\nAPI&gt; save,c,l\n...\nOK\nAPI&gt; ?,c,UPDATE dm_job OBJECTS set run_now=true, set a_next_invocation=DATE(NOW) WHERE object_name='dm_LDAPSynchronization'\nobjects_updated\n---------------\n              1\n(1 row affected)\n[DM_QUERY_I_NUM_UPDATE]info:  \"1 objects were affected by your UPDATE statement.\"\n\nAPI&gt; exit\nBye\n[dmadmin@content-server-0 ldapdb]$<\/pre>\n<p>&nbsp;<\/p>\n<p>With the above, I just changed the extension of the file on the file system and its reference in the &#8220;<em>dm_location<\/em>&#8221; Object. The last iAPI command triggered the <em>dm_LDAPSynchronization<\/em> job to run. Checking the new log file, the issue was indeed solved which confirmed that despite the fact that the Trust Chain was a <em>PEM<\/em> encoded certificate, it wasn&#8217;t enough. There is actually a hardcoded value\/check inside Documentum, which forces you to use the &#8220;<em>.pem<\/em>&#8221; extension and nothing else:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [17,21,22,23,31]\">[dmadmin@content-server-0 ldapdb]$ cat $DOCUMENTUM\/dba\/log\/repo01\/sysadmin\/LDAPSynchronizationDoc.txt\nLDAPSynchronization Report For DocBase repo01 As Of 2019\/09\/22 13:19:33\n\n2019-09-22 13:19:30:360 UTC [default task-87]: LDAP Synchronization Started @ Sun Sep 22 13:19:30 UTC 2019\n2019-09-22 13:19:30:360 UTC [default task-87]:\n2019-09-22 13:19:30:361 UTC [default task-87]: $JMS_HOME\/server\/DctmServer_MethodServer\/deployments\/ServerApps.ear\/lib\/dmldap.jar\n2019-09-22 13:19:30:367 UTC [default task-87]: ---------------------------------------------------------------------------------\n2019-09-22 13:19:30:367 UTC [default task-87]: Product-Name : Content Server-LDAPSync\n2019-09-22 13:19:30:367 UTC [default task-87]: Product-Version : 16.4.0110.0167\n2019-09-22 13:19:30:367 UTC [default task-87]: Implementation-Version : 16.4.0110.0167\n2019-09-22 13:19:30:367 UTC [default task-87]: ---------------------------------------------------------------------------------\n2019-09-22 13:19:30:367 UTC [default task-87]:\n2019-09-22 13:19:30:370 UTC [default task-87]: Preparing LDAP Synchronization...\n2019-09-22 13:19:32:425 UTC [default task-87]: INFO: Job Status: [LDAP Synchronization Started @ Sun Sep 22 13:19:30 UTC 2019]\n2019-09-22 13:19:32:453 UTC [default task-87]: INFO: Job Status updated\n2019-09-22 13:19:34:292 UTC [default task-87]: INFO: List of Ldap Configs chosen for Synchronization\n2019-09-22 13:19:34:292 UTC [default task-87]: INFO:    &gt;&gt;&gt;0812d6878000252c - Internal_LDAP&lt;&lt;&lt;\n2019-09-22 13:19:34:292 UTC [default task-87]: INFO:\n2019-09-22 13:19:34:294 UTC [default task-87]:\n2019-09-22 13:19:34:294 UTC [default task-87]: ==================================================================================\n2019-09-22 13:19:34:297 UTC [default task-87]: Starting Sychronization for ldap config object &gt;&gt;&gt;Internal_LDAP&lt;&lt;&lt; ...\n2019-09-22 13:19:35:512 UTC [default task-87]: INFO: Directory Type: Sun ONE Directory Server ...\n2019-09-22 13:19:35:517 UTC [default task-87]: INFO: Ldap Connection: SSL connection\n2019-09-22 13:19:35:517 UTC [default task-87]: INFO: ldap:\/\/ldap.domain.com:636\n2019-09-22 13:19:35:517 UTC [default task-87]: INFO: {java.naming.provider.url=ldap:\/\/ldap.domain.com:636, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory}\n2019-09-22 13:19:35:597 UTC [Thread-91752]: INFO: DM_LDAP_IGNORE_HOSTNAME_CHECK environment variable is enabled.\n2019-09-22 13:19:35:598 UTC [Thread-91752]: INFO: Skipping hostname check\n2019-09-22 13:19:35:598 UTC [Thread-91752]: INFO: DctmTrustMangaer.checkServerTrusted(): Successfully validated the certificate chain sent from server.\n2019-09-22 13:19:35:635 UTC [default task-87]: INFO: DM_LDAP_IGNORE_HOSTNAME_CHECK environment variable is enabled.\n2019-09-22 13:19:35:635 UTC [default task-87]: INFO: Skipping hostname check\n2019-09-22 13:19:35:635 UTC [default task-87]: INFO: DctmTrustMangaer.checkServerTrusted(): Successfully validated the certificate chain sent from server.\n2019-09-22 13:19:35:663 UTC [default task-87]: INFO: LDAP Search Retry: is_child_context = true\n2019-09-22 13:19:35:663 UTC [default task-87]: INFO: LDAP Search Retry: Retry count = 1\n2019-09-22 13:19:35:665 UTC [default task-87]: Starting the group synchronization...\n...\n2019-09-22 13:19:35:683 UTC [default task-87]: Group synchronization finished.\n2019-09-22 13:19:35:683 UTC [default task-87]:\n2019-09-22 13:19:35:683 UTC [default task-87]: INFO: Updating Last Run Time: [20190922131935Z]\n2019-09-22 13:19:35:683 UTC [default task-87]: INFO: Updating Last Change No: [null]\n2019-09-22 13:19:35:749 UTC [default task-87]: INFO: Ldap Config Object &gt;&gt;&gt;&gt;Internal_LDAP&lt;&lt;&lt;&lt; updated\n2019-09-22 13:19:35:751 UTC [default task-87]: Disconnected from LDAP Server successfully.\n2019-09-22 13:19:36:250 UTC [default task-87]: Synchronization of ldap config object &gt;&gt;&gt;Internal_LDAP&lt;&lt;&lt; is finished\n2019-09-22 13:19:36:250 UTC [default task-87]: ==================================================================================\n2019-09-22 13:19:36:250 UTC [default task-87]:\n2019-09-22 13:19:36:265 UTC [default task-87]: INFO: Job Status: [dm_LDAPSynchronization Tool Completed with WARNINGS at 2019\/09\/22 13:19:36. Total duration was 6 seconds.]\n2019-09-22 13:19:36:278 UTC [default task-87]: INFO: Job Status updated\n2019-09-22 13:19:36:278 UTC [default task-87]: LDAP Synchronization Ended @ Sun Sep 22 13:19:36 UTC 2019\n2019-09-22 13:19:36:278 UTC [default task-87]: Session s2 released successfully\nReport End  2019\/09\/22 13:19:36\n[dmadmin@content-server-0 ldapdb]$<\/pre>\n<p>&nbsp;<\/p>\n<p>A pretty annoying design but there is nothing you can do about it. Fortunately, it&#8217;s not hard to fix the issue once you know what&#8217;s the problem!<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In a previous blog, I talked about the automation of the LDAP\/LDAPs creation. However, the first time that I applied these steps, I actually faced an issue and I couldn&#8217;t really get my head around it, at first. This will be a rather short post but I still wanted to share my thoughts because it [&hellip;]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197,525],"tags":[129,1547,1761,1417,382],"type_dbi":[],"class_list":["post-13118","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-documentum","tag-ldap","tag-ldaps","tag-silent","tag-ssl"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Documentum - LDAP Config Object &quot;certdb_location&quot; has invalid value - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - LDAP Config Object &quot;certdb_location&quot; has invalid value\" \/>\n<meta property=\"og:description\" content=\"In a previous blog, I talked about the automation of the LDAP\/LDAPs creation. However, the first time that I applied these steps, I actually faced an issue and I couldn&#8217;t really get my head around it, at first. This will be a rather short post but I still wanted to share my thoughts because it [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-12-08T07:00:28+00:00\" \/>\n<meta name=\"author\" content=\"Morgan Patou\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@MorganPatou\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Morgan Patou\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum &#8211; LDAP Config Object &#8220;certdb_location&#8221; has invalid value\",\"datePublished\":\"2019-12-08T07:00:28+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/\"},\"wordCount\":405,\"commentCount\":0,\"keywords\":[\"Documentum\",\"ldap\",\"LDAPs\",\"Silent\",\"SSL\"],\"articleSection\":[\"Application integration &amp; Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/\",\"name\":\"Documentum - LDAP Config Object \\\"certdb_location\\\" has invalid value - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2019-12-08T07:00:28+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum &#8211; LDAP Config Object &#8220;certdb_location&#8221; has invalid value\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\",\"name\":\"Morgan Patou\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"caption\":\"Morgan Patou\"},\"description\":\"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex &amp; critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.\",\"sameAs\":[\"https:\/\/blog.dbi-services.com\/author\/morgan-patou\/\",\"https:\/\/x.com\/MorganPatou\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Documentum - LDAP Config Object \"certdb_location\" has invalid value - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - LDAP Config Object \"certdb_location\" has invalid value","og_description":"In a previous blog, I talked about the automation of the LDAP\/LDAPs creation. However, the first time that I applied these steps, I actually faced an issue and I couldn&#8217;t really get my head around it, at first. This will be a rather short post but I still wanted to share my thoughts because it [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/","og_site_name":"dbi Blog","article_published_time":"2019-12-08T07:00:28+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum &#8211; LDAP Config Object &#8220;certdb_location&#8221; has invalid value","datePublished":"2019-12-08T07:00:28+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/"},"wordCount":405,"commentCount":0,"keywords":["Documentum","ldap","LDAPs","Silent","SSL"],"articleSection":["Application integration &amp; Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/","name":"Documentum - LDAP Config Object \"certdb_location\" has invalid value - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-12-08T07:00:28+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-ldap-config-object-certdb_location-has-invalid-value\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum &#8211; LDAP Config Object &#8220;certdb_location&#8221; has invalid value"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8","name":"Morgan Patou","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","caption":"Morgan Patou"},"description":"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex &amp; critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.","sameAs":["https:\/\/blog.dbi-services.com\/author\/morgan-patou\/","https:\/\/x.com\/MorganPatou"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13118","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=13118"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13118\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=13118"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=13118"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=13118"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=13118"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}