# Nightly 8.3 Changelogs - 2026 and beyond

**URL:** <https://forum.inductiveautomation.com/t/nightly-8-3-changelogs-2026-and-beyond/113010>\
**Category:** Ignition Early Access\
**Created:** [December 29, 2025, 3:49pm UTC](https://forum.inductiveautomation.com/t/nightly-8-3-changelogs-2026-and-beyond/113010 "2025-12-29T15:49:04Z")\
**Posts on this page:** 1\
**Showing post:** 85

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/inductiveautomation/original/2X/c/c985ea71ed53a8f212f3920ddf03fe05249170b8.png) [@system](https://forum.inductiveautomation.com/u/system)\
**Post date:** [May 23, 2026, 6:00am UTC](https://forum.inductiveautomation.com/t/nightly-8-3-changelogs-2026-and-beyond/113010/85 "2026-05-23T06:00:55Z")

</div>

Nightly Changelog: 8.3.7\*-b20260522

## Swing

### Designer

**IGN-15126: Null Pointer Exception and IllegalArgumentException when editing scripts in a floating window**  
Fixed a crash that could occur when closing the Designer with floating script or view editors open.

Selecting a floating script or view editor in the Project Browser now correctly focuses the floating window and keeps the selection in sync

## Security

### User Sources

**IGN-16184: AD user sources fail to migrate when Distinguished name has parenthesis**

- Fixed a regression introduced in 8.3.6 which caused pure and hybrid AD user sources to fail migration from 8.1 when user/role search/listing base entry settings include wrapping parentheses
- Fixed a regression introduced in 8.3.6 which caused pure and hybrid AD user sources to fail at runtime due to faulty migration logic which removed wrapping double quotes from user/role search/listing base entry settings.
- The values for User/Role search/listing base entry settings will be left as-is during migration from 8.1 for pure and hybrid AD user sources going forward.
- Pure and hybrid AD user sources will fail to migrate from 8.1 for most user/role search/listing base entry values which cannot be parsed as valid LDAP distinguished names (as per RFC 2253).
- Added a new `legacyNamingEnabled` boolean setting to pure and hybrid AD user sources which is enabled by default for user sources upgraded from 8.1 and disabled by default for user sources upgraded from a prior 8.3 version.
- When the new `legacyNamingEnabled` boolean setting is set to `true`, user/role search/listing base entry values are parsed as they were in 8.1: first as a JNDI CompositeName, and then the first entry in the parsed JNDI CompositeName is parsed as an LdapName.
- When the new `legacyNamingEnabled` boolean setting is set to `false`, user/role search/listing base entry values are parsed as they were in prior 8.3 versions: directly as an LdapName.

---

_[View the full topic](https://forum.inductiveautomation.com/t/nightly-8-3-changelogs-2026-and-beyond/113010)._