External Account creation fails in UI 2026.2.3

Hello Dynamic66,

Thank you for reporting this.

I understand that in PowerShell Universal 2026.2.3, creating an External Account from the Admin Console remains in a loading state after clicking OK, and the account is not created after refreshing the page. You also confirmed that creating the External Account through a script works and that local database identities are not affected.

To help narrow down whether this is specific to the Admin Console workflow, could you please provide the following?

• Hosting method and operating system
• Database type: SQLite, SQL Server, or PostgreSQL
• Whether 2026.2.3 was a clean installation or an upgrade, and the previous PSU version if applicable
• Whether External Account creation from the UI worked in the previous version
• Whether the behavior is the same in another browser or a private/incognito window
• From the browser Developer Tools, the HTTP status and sanitized response for the request generated when clicking OK
• Any Console error generated at the same time
• Relevant sanitized PSU log entries covering only the time of the failed attempt

There is no need to upload a complete HAR file or complete log set.

Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread.

I will review the information and use it to determine the next troubleshooting or reproduction steps.

Best regards,
Ruben Tapia

Hello Dynamic66,

I completed a controlled reproduction test using PowerShell Universal 2026.2.3, build `91f7590a4ff4c3edb7731f93974128cfb4961d98`.

In a clean, isolated Windows deployment using SQLite, I was not able to reproduce the behavior you reported.

The results were:

• External Account creation through the Admin Console succeeded 3/3 times and persisted after reloading the page.
• Script-based External Account creation also succeeded 3/3 times and persisted.
• Local database identity creation through the Admin Console succeeded and persisted.
• No submit-related browser Console error was observed during the successful UI tests.

Because the reported issue did not occur on 2026.2.3 in the clean environment, I did not proceed with a previous-version comparison. At this stage, the available evidence does not establish a general 2026.2.3 regression.

The next useful step is to compare your environment with the lab. Could you please provide:

• Hosting method and operating system
• Database type
• Browser and version
• Whether 2026.2.3 was a clean installation or upgrade, and the previous version
• Whether any custom authentication or identity configuration is involved
• Sanitized browser Console output and the status/timing of the relevant request during one failed attempt
• Sanitized PSU log entries covering the same timestamp

Please send the HAR to ruben.tapia@ironmansoftware.com
With those details, I can determine the highest-value parity test to run next.

Best regards,
Ruben Tapia

Thank for taking the time to test it.

• Hosting Linux - Docker
• Database type: PostgreSQL
• Browser and version: Brave/Chromium
• Whether 2026.2.3 was a clean installation or upgrade, and the previous version: upgraded from 2026.2.3
• Whether any custom authentication or identity configuration is involved: no
• Sanitized browser Console output and the status/timing of the relevant request during one failed attempt: no errors on action
• Sanitized PSU log entries covering the same timestamp: no additional errors on action


I can reproduce the behavior on the other connected PSU server.

Since i can work around it be creating the identity over script the priority is low on this one.

The Dev console output on every admin page outputs this error on load.
i dont think its connected and does not seam to impaired function:

ant-design-charts-blazor.js:1 Uncaught SyntaxError: Identifier 'evalableKeys' has already been declared (at ant-design-charts-blazor.js:1:1)
PendingScript
loadScriptAndStyle
@
AntDesign.Charts.av4…h2.lib.module.js:30
beforeStart
@
AntDesign.Charts.av4…zh2.lib.module.js:6
s
@
blazor.server.js?v=2026.2.3:1
(anonymous)
@
blazor.server.js?v=2026.2.3:1
await in (anonymous)
(anonymous)
@
blazor.server.js?v=2026.2.3:1
importInitializersAsync
@
blazor.server.js?v=2026.2.3:1
(anonymous)
@
blazor.server.js?v=2026.2.3:1
await in (anonymous)
Rr
@
blazor.server.js?v=2026.2.3:1
await in Rr
Tr
@
blazor.server.js?v=2026.2.3:1
Pr
@
blazor.server.js?v=2026.2.3:1
(anonymous)
@
identities:33

Hello Dynamic66,

Thank you for the additional details. The Linux + Docker and PostgreSQL configuration gives us an important difference compared with our previous Windows + SQLite laboratory.

We will adjust the lab to better match your environment and repeat the External Account creation tests under Linux/Docker with PostgreSQL. We will also use appropriate controls to determine whether the behavior is specific to the database provider, hosting environment, or UI workflow.

Once the testing is complete, I will share the relevant findings with you here.

If we are able to reproduce the reported behavior under the closer-matching environment, we will prepare the reproduction evidence and escalate the case directly to our Development team for review.

Thank you again for providing the environmental details and for confirming that the script-based creation remains a usable workaround in the meantime.

Best regards,
Ruben Tapia

Hello Dynamic66,

We completed a second laboratory run with much closer parity to your environment:

* Linux / Docker
* PostgreSQL
* PSU 2026.2.3 build `91f7590a4ff4c3edb7731f93974128cfb4961d98`

The reported behavior was still not reproduced.

External Account creation through the Admin Console succeeded 3/3 times and persisted after reload. Script-based creation also succeeded 3/3 times, and local identity creation through the UI worked as expected.

We also observed the `evalableKeys` JavaScript error you mentioned. However, it was present while all External Account creations succeeded, so we could not establish a correlation with this issue.

At this point, the behavior appears to depend on a condition specific to your environment or topology.

Could you please confirm:

* Whether both PSU servers are part of the same deployment and share the same PostgreSQL database
* Whether a load balancer or reverse proxy is involved
* Whether the issue occurs when accessing each PSU node directly
* The exact Docker image tag/digest
* Your exact Brave/Chromium version
* The actual PSU version you upgraded from

For the next failed attempt, please capture a HAR file covering the External Account submission and send it directly to:

ruben.tapia@ironmansoftware.com

Please do not upload the HAR file to this public forum. HAR files can contain sensitive information such as cookies, tokens, URLs, headers, and account data, so please sanitize the file before sending whenever possible.

Best regards,
Ruben Tapia