---
title: April 2025
description: Release notes for PingOne DaVinci connectors for April 2025
component: connectors
page_id: connectors::relnotes/archive/2025-04-April
canonical_url: https://docs.pingidentity.com/connectors/relnotes/archive/2025-04-April.html
llms_txt: https://docs.pingidentity.com/connectors/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: July 9, 2026
section_ids:
  april-30: April 30
  the-splunk-connector-now-respects-localized-error-messages: The Splunk Connector now respects localized error messages
  april-25: April 25
  the-lexisnexis-connector-now-respects-localized-error-messages: The LexisNexis Connector now respects localized error messages
  april-4: April 4
  authenticate-user-via-kerberos: Authenticate User via Kerberos
  april-1: April 1
  the-location-policy-connector-now-outputs-country-result: The Location Policy connector now outputs country result
---

# April 2025

## April 30

### The Splunk Connector now respects localized error messages

Fixed Splunk Connector

Error handling for the [Splunk Connector](../../splunk_connector.html) has been corrected and now respects localized error messages. As a result, select error outcomes might produce different message text.

## April 25

### The LexisNexis Connector now respects localized error messages

Fixed LexisNexis Connector

Error handling for the [LexisNexis Connector](../../lexisnexis_connector.html) has been corrected and now respects localized error messages. As a result, select error outcomes might produce different message text.

## April 4

### Authenticate User via Kerberos

Improved PingOne Connector

The [PingOne Connector](../../p1_connector.html) **Authenticate User via Kerberos** capability now supports the selection of a user type, regardless of whether user migration is enabled or not.

The ability to select a user type without user migration allows you to create PingOne DaVinci flows to offer seamless SSO authentication experience to users provisioned from Microsoft Active Directory into PingOne through an [LDAP gateway provisioning connection](https://docs.pingidentity.com/pingone/integrations/p1_create_provisioning_connection_gateway.html) and an [inbound rule](https://docs.pingidentity.com/pingone/integrations/p1_create_inbound_provisioning_rule_gateway.html).

|   |                                                                           |
| - | ------------------------------------------------------------------------- |
|   | The selected LDAP gateway must be configured with at least one user type. |

## April 1

### The Location Policy connector now outputs country result

Updated Location Policy Connector

The [Location Policy Connector](../../location_policy_connector.html) **Allow by Location Name** and **Deny by Location Name** capabilities now provide the location information associated with the user's IP address. This makes it easy to branch the flow more specifically after an allow or deny result by evaluating the user's exact country.