Loading...
Loading...
The incorrect mid server is selected while requesting a new certificate using automated certificate management Current flow and expected flow : The current code snippet (function: getRandomMid ) selects a mid-server that is active and validated. By doing this we may select a mid-server that does not have connectivity to the target certificate authority. And the selected mid-server is used for a different purpose in the instance such as discovery or service mapping or some integration. The expected flow is to, either it shouldn't send the query if there is no mid on the routing policy or define a mid-server application or capability (or capabilities) that users will be able to use and assign to their MID servers. Code Snippet: ++++++++++++++++++++++++++++++++++ getRandomMid: function() { //Fetching a random mid server and storing it, so we can use this in case routing policy does not have a mid server var midGr = new GlideRecord("ecc_agent"); midGr.addQuery("status", "Up"); midGr.addQuery("validated", "true"); midGr.query(); if(midGr.hasNext()) { var totalMids = midGr.getRowCount(); var randomNumber = Math.floor(Math.random()*totalMids); var randomMidGr = new GlideRecord("ecc_agent"); randomMidGr.addQuery("status", "Up"); randomMidGr.addQuery("validated", "true"); randomMidGr.chooseWindow(randomNumber, randomNumber+1); randomMidGr.query(); randomMidGr.next(); return randomMidGr.getUniqueValue(); } }, ++++++++++++++++++++++++++++++++++
Navigate to All > Service Catalog > Certificate Management. Click Request New Certificate - Automated flow. The current code snippet (function: getRandomMid ) selects a mid-server that is active and validated. By doing this we may select an incorrect mid-server that does not have connectivity to the target certificate authority. Please review the function getRandomMid and its usage in Script Include-CertificateRequestAutomatedFlow
This problem has no workaround, after carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to address this issue as a future product enhancement. Subscribe to this Known Error article to receive notifications when more information will be available.
PRB1642641
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.