# Error with Active Directory Connector using SASL Authentication

**URL:** <https://developer.sailpoint.com/discuss/t/error-with-active-directory-connector-using-sasl-authentication/69541>\
**Category:** IIQ Discussion and Questions\
**Tags:** identityiq\
**Created:** [June 27, 2024, 4:39pm UTC](https://developer.sailpoint.com/discuss/t/error-with-active-directory-connector-using-sasl-authentication/69541 "2024-06-27T16:39:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevinwoodbury](https://avatars.discourse-cdn.com/v4/letter/k/f07891/32.png) [@kevinwoodbury](https://developer.sailpoint.com/discuss/u/kevinwoodbury)\
**Post date:** [June 27, 2024, 4:39pm UTC](https://developer.sailpoint.com/discuss/t/error-with-active-directory-connector-using-sasl-authentication/69541/1 "2024-06-27T16:39:58Z")

</div>

### Which IIQ version are you inquiring about?

Version 8.3

### Please share any images or screenshots, if relevant.

 ![SASL Error.png](https://global.discourse-cdn.com/sailpoint/original/2X/3/37f36fd60da9c5b460a355cd6786c58f2d66f054.png)

### Share all details related to your problem, including any error messages you may have received.

In our Non-Production environment (but soon to be in production in Mid-July) the use of NTLM has been disabled. This started to cause issues with the Active Directory Connector and using Simple Authentication (where the username must be provided as DOMAIN/UserName. We found that is we switch to SASL that under the covers Kerberos Authentication can be leveraged. However, when we try to use SASL we are getting a different authentication error (see attached Screenshot). Basically the error reads "FATAL: Runtime exception occurred while updating he KDC cache and the KRB configuration file - dc=,dc=; java.lang.Exception [ERROR 1] ERROR occurrend while instantiating SPSSASLConextManager, cannot proceed with context creation.

---

<div class="post-metadata">

**Author:** ![enistriminsait](https://avatars.discourse-cdn.com/v4/letter/e/58f4c7/32.png) [@enistriminsait](https://developer.sailpoint.com/discuss/u/enistriminsait)\
**Post date:** [June 27, 2024, 5:23pm UTC](https://developer.sailpoint.com/discuss/t/error-with-active-directory-connector-using-sasl-authentication/69541/2 "2024-06-27T17:23:51Z")

</div>

Hi @kevinwoodbury,

I see this error for the first time, but reading the message I have some questions.

Ensure that AD service si up and running:  
Are you sure the configuration on AD side is correct?  
ports are opened?  
have the all the permission for this operation?  
can you to connect from another side to ad in slas?

I found those link about the SASL configuration, maybe they will help you:

> **[Forest Settings](https://documentation.sailpoint.com/connectors/active_directory/help/integrating_active_directory/forest_settings.html?Highlight=SASL)**
>
> SailPoint Connectors Documentation

> **[Prerequisites](https://documentation.sailpoint.com/connectors/active_directory/help/integrating_active_directory/prerequisites.html?Highlight=SASL)**
>
> SailPoint Connectors Documentation

> **[Domain Settings](https://documentation.sailpoint.com/connectors/active_directory/help/integrating_active_directory/domain_settings.html?Highlight=SASL)**
>
> SailPoint Connectors Documentation

> **[Required Permissions](https://documentation.sailpoint.com/connectors/iqservice/help/integrating_iqservice_admin/min_permission_config.html)**
>
> SailPoint Connectors Documentation

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [August 26, 2024, 5:24pm UTC](https://developer.sailpoint.com/discuss/t/error-with-active-directory-connector-using-sasl-authentication/69541/3 "2024-08-26T17:24:47Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.