Organization search seems not recognizing special characters

[jarias-lfx]

Ticket: SUPPORT-12023
Organization: AT&T Services, Inc.
Project: All

Bug Summary:
When contributor from AT&T Services are trying to sign the CCLA, they are unable to find the Organization using AT&T keyword:

Seems other searches using at least the "&" character is not working like 1&1 Telecommunication:

The Organization appears doing a manual alphabetical search order:

Doing the same search in other tools like Organization Dashboard, works without issues:

Checked Companies table DB and saw nothing out of the ordinary for AT&T.

[mlehotskylf]

@nickmango @jarias-lfx is this still an issue?

[jarias-lfx]

This is still an issue:

[nickmango]

@mlehotskylf Verified and this is a bug on the backend.. The search API is not handling special characters.

[mlehotskylf]

@nickmango is working on the fix.

[nickmango]

@amolsontakke3576 noted the frontend is not encoding the query param for the company name. Can you edit this on your end ?

[amolsontakke3576]

@nickmango I have encoded it. Lets take the example at&t and FE encoded it to at%26t, you need to decode it from the backend.
API :
https://api.easycla.lfx.linuxfoundation.org/v3/organization/search?companyName=at%26t&include-signing-entity-name=false

[nickmango]

Hello @amolsontakke3576 which endpont are you using for the search in this flow ?
On the backend the API is able to decode the encoded value with the v4/company/lookup endpoint
curl --location 'http://localhost:8080/v4/company/lookup/?companyName=AT%26T' returns the expected response { "Employees": "100K+", "ID": "0012M00002hEN7AQAW", "Industry": "Diversified Telecommunication Services", "Link": "att.com", "Name": "AT&T", "Sector": "Telecommunication Services", "Source": "External Data Source", "signingEntityNames": null }

[amolsontakke3576]

@nickmango It is V3 endpoint
v3/organization/search?companyName=at%26t&include-signing-entity-name=false

[nickmango]

Thanks @amolsontakke3576 . I have updated the API for this usecase

[thakurveerendras]

Tested with AT&T org and found that it is working fine.

[thakurveerendras]

Tested with some more organization that contains special character & found that it is working fine, So updating this ticket status

[thakurveerendras]

Verified on prod, it is working fine. So closing this ticket