I want to send a note out about this issue that I briefly discussed with Alec yesterday. This is a problem I am seeing over and over from customers with no current technical solution. I will describe how I am currently handling it.

1. On developers portal, I create an account. I specify a company value during registration. The screening query performed by Download Manager includes the company name in the name field. This is good.
2. For the linked account on redhat.com, this is usually a person account but I guess could be an org account. Either way, the screening query done via SSO or eval app either sends a person name or a separate company name in the name field. This is not good.

Problem: These company name values are coming from two distinct fields (or mismatched to where we screen a person name on redhat.com and a company name on developers). If the name values do not match 100%, then the customer goes into a HOLD-CLEAR loop. This occurs if they download something from Download Manager and then for example download from the eval app or container registry. This happens because the company name keeps changing and triggers a re-screen, even though the compliance team overrode the hold on the account.

If we have a company value, we must screen that value. But we need to overcome this issue of two distinct company name fields that could contain unique values. The company name values must match across systems, or if we somehow know the name then we need to screen that in all cases.

My solution currently is to have the customers update their account and match up the company values between systems whether that is a true company name, or asking them to put their personal name into the company field on Developers Portal account page.