Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uploadig LDAP user avatar errors by <Invalid JSON Custom Fields> #32189

Open
momentics opened this issue Apr 11, 2024 · 7 comments
Open

Uploadig LDAP user avatar errors by <Invalid JSON Custom Fields> #32189

momentics opened this issue Apr 11, 2024 · 7 comments

Comments

@momentics
Copy link

It used to be work till 6.7.0. Latest checked version is 6.6.0 and seems 6.6.3 too.
However, updating server up to 6.7.0 breaks this functionality.

Steps to reproduce:

  1. Sync on ldap users (this configuration used to be work since 4.x succesifully)
  2. Open Users list on Admin Panel
  3. Try to set up user's avatar image by *.jpg file
  4. Invalid JSON Custom Fiels error occurs

Expected:

  • Avatar to be updated without errors

Configuation:

  • Server: Latest, 6.7.0 docker image (all in one).
  • Client: 3.9.14, windows 10 x64
  • Starter license, 10/25 used

image

@momentics
Copy link
Author

Update:
Avatars are displayed if the user is logged into RC. Most likely they are downloaded from AD Imge but not from uploaded pics.

@reetp
Copy link

reetp commented May 15, 2024

Hi,

can you check on the latest 6.7.x or 6.8.x please.

@momentics
Copy link
Author

momentics commented May 15, 2024

Hi,
can you check on the latest 6.7.x or 6.8.x please.

Hello @reetp
I just tried 6.8.0 to repeat the issue.

That what had been done:

  • Latest 6.8.0 had been installed via docker image
  • New Windows AD user had been created
  • RC->Working space->Settings->LDAP had been synchronized, to refresh users list. New created user is visible in RC-> Working space->Users.
  • User's parameters had been edited (particularly avatar image). Used JPG file 512x512px, and 65 kb in size
  • Original error repeated

However, if the same JPG file is configured in Windows AD->UserImage, same error occurs. But avatar will be shown right after first time mentioned user is logged into RC.

Therefore, same issue exists in latest 6.8.0 version. Sorry John...

update:
All RC docker image installations were done on top of an existing installation of the previous version... that is, always an upgrade.

@reetp
Copy link

reetp commented May 16, 2024

Therefore, same issue exists in latest 6.8.0 version. Sorry John...

You don't have to apologise to me, or anyone ;-)

Thanks for testing it!

I have pinged the dev who tends to handle LDAP/AD stuff. See if he has any ideas.

@reetp
Copy link

reetp commented May 20, 2024

The dev who does most of the LDAP stuff doesn't believe it is a LDAP error per se.

I presume you have some code in LDAP->Premium-> Sync Custom Fields or similar?

What is the custom code that is triggering this?

@momentics
Copy link
Author

momentics commented May 20, 2024

Hello @reetp !

Nope. It is not premium and no custom code. It is Starter licence.

Trivial conf:

  • Server type - Active Directory

  • Host - host ip

  • Port - 389 (this is private network)

  • Reconnect - Yes

  • Reserve auth - Yes

  • User DN - correct user DN

  • Password - correct user DN password

  • Encryption - none

  • Cert - None (this is private network)

this configuration used to be since 4.x and triggered manually.

update1:

and used to be work 6.6.0 - absolutely sure. And probably 6.6.3.

update2
before 6.6.0 when licensing was different, configuration contained autosync options also. Since licensing abilities was changed and there is no options to see\or clear right now (and i'm n otsure if it was cleared in configuration database due upgrade). So it's most likely there

@reetp
Copy link

reetp commented May 21, 2024

Should all work for our number of users.

Hmmm.

Any errors in the browser console?

Note if we search the code for this error we can see this:

https://github.com/search?q=repo%3ARocketChat%2FRocket.Chat+error-invalid-customfield&type=code

JSON.parse(settings.get('Accounts_CustomFields'));

Check Accounts, Registration, Custom Fields

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants