search

Blazam-App / BLAZAM

A modern Active Directory management web application with a focus on delegation
https://blazam.org
Other
22 stars 2 forks source link

BalZam Login error #475

Closed nenee-ai closed 3 days ago

nenee-ai commented 1 month ago

Description: When using BalZam, we encounter an error during the login process. The error message is:

Blazam error is: Unexpected character encountered while parsing value: <. Path '', line 0, position 0".

jacobsen9026 commented 1 month ago

Hi @nenee-ai

Were you trying to log in with the built-in "admin" account?

I was not able to identify the error in our logging server...

Is that the complete error message? If there is any more, please paste the complete error text in a reply.

Thank you

nenee-ai commented 1 month ago

Hello @jacobsen9026,

We can log in with the built-in admin account, but we are unable to log in using the delegated admin accounts. Please find the attached screenshot for reference.

Thank you. image (10)

jacobsen9026 commented 1 month ago

I had a feeling... and that type of error is not reported to our error logging server.

Can you please let me know all non-US alphanumeric characters (A-Z,a-z, 0-9) in the username, (eg: ò,-,{,Ä)?

This is most likely an internationalization bug.

jacobsen9026 commented 1 month ago

I had a feeling... and that type of error is not reported to our error logging server.

Can you please let me know all non-US alphanumeric characters (A-Z,a-z, 0-9) in the username, (eg: ò,-,{,Ä)?

This is most likely an internationalization bug.

If you're uncomfortable posting because most or all characters are non-US, you can email it to support@blazam.org and it will be kept private.

nenee-ai commented 1 month ago

Hello, Thank you. I sent the user name to your support@blazam.org.

jacobsen9026 commented 1 month ago

Thank you, I was still unable to reproduce the error. The username is simple enough that it couldn't cause this, but I've removed some old unused JS code I believe could be a possible cause along with adding logging of the error to our log server so we can see more details.

This change will be included in the v1 release which will require .NET 8, due to drop by Monday.

I apologize for any inconvenience.

nenee-ai commented 1 month ago

Thank you. We will try debugging this, it could be some other problem.

jacobsen9026 commented 1 month ago

Did you mean to close this issue?

The issue I thought I saw is not the likely cause.

And this looks like a legitimate JavaScript error.

jacobsen9026 commented 1 month ago

Version 1.0 has been released with the logging additions I mentioned. Honestly not much else was changed to address this specific issue because I was unable to reproduce, but if the error remains, please let me know.

Thank you, Chris

github-actions[bot] commented 2 weeks ago

This issue is stale because it has been open for 14 days with no activity.

github-actions[bot] commented 3 days ago

This issue was closed because it has been inactive for 14 days since being marked as stale.