---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Authentication errors

# Authentication errors {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

This section describes some common authentication errors and how they can be
resolved.

## Certificate validation issue {#splunkes-auth-errors-security__section_cfj_mxs_ljb}

If an error occurs during authentication, you may see the following screen:

If you have verified that your API account credentials and the Splunk Base URL
information are correct, this error may be due to an issue with the Splunk certificate
for the port 8089 communication. ServiceNow® instance requires a
valid certificate with a common name that matches the server host name to establish
secure connections. For more information, see [Certificates](https://www.servicenow.com/docs/access?context=c_Certificates&version=australia&pubname=australia-platform-security&ft:locale=en-US). If you see this error, you can verify that the issue is due to
a certificate problem by viewing the system logs.

An error condition similar to the following will likely appear:

To proceed with the authentication, you must replace the Splunk default certificate that
is provided for API access on port 8089. For detailed instructions on how to replace the
SSL certificate, see [KB0778285](https://support.servicenow.com/nav_to.do?uri=/u_kb_template_kcs_how_to_for_cs.do?sys_id=1cedb8cadb33374c5ed4a851ca961909&sysparm_domain=null&sysparm_domain_scope=null).