Unsupported anonymous UserIdentity response discrepancy from UACTT expected result

[Siyuan-Xu-Wapice]

Type of issue

• Bug
• Enhancement
• Compliance
• Question
• Help wanted

Current Behavior

NET Standard Stack server (Both our own server using nuget pacakage and the Ref. Server using lastest Master) responds BadUserAccessDenied (0x801f0000) when Anonymous UserIdentityToken was provided by the client for creating session, but the server doesn't supported it.
Log message from UACTT:

PS. The stack responds all the other unsupported UserIdentityToken correctly, namely: Username(password), X509, kerberos.

Expected Behavior

According to UACTT SessionService -> SessionBase -> TestCases -> Err-009, the server should respond with BadIdentityTokenInvalid for all unsupported UserIdentityToken.

Steps To Reproduce

1. Fetch and Pull the latest Master.
2. Disable Anonymous user support by commenting out the corresponding field in the config.xml file.
3. Build and run the Console Reference Server.
4. Set up a project in UACTT for the Ref. Server.
5. Select SessionService -> SessionBase -> TestCases -> Err-009 and run.

Environment

- OS:Windows 10/11
- Environment: Visual Studio Professional 2022
- Runtime: .NET 4.8, .NET Core 6,8
- Nuget Version: 1.5.375.443
- Component:
- Server: Reference Server (Using latest Master)/ Own server(StandardServer) from Nuget
- Client: UACTT 1.5.4

Anything else?

It seems handling Anonymous UserIdentityToken is bit tricky, when it's used for DiscoveryService. But is it possible to fix it by responding correctly or should the UACTT test case have a different expectation concerning the Anonymous UserIdentityToken?