Model download link returns "Application Not Authorized to Use UTS Login Service

[sunnysunnyp143]

Describe the bug

The model download link in the medcat-v2 README fails after UMLS/NIH login.
After authenticating with a valid NIH/UMLS account, NLM returns an error page
instead of redirecting to the MedCAT model download form.

Link used

From medcat-v2/README.md:

https://uts.nlm.nih.gov/uts/login?service=https://medcat.sites.er.kcl.ac.uk/auth-callback

The API-key-based link (/auth-callback-api) fails the same way.

Error message

The login now routes through login-prod.nlm.nih.gov and returns:

Application Not Authorized to Use UTS Login Service
The application you attempted to authenticate to is not authorized to use
UTS Login Service. This usually indicates that the application is not
registered with UTS Login Service, or its authorization policy defined in
its registration record prevents it from leveraging UTS Login functionality,
or it's malformed and unrecognized by UTS Login Service.

Likely cause

The medcat.sites.er.kcl.ac.uk callback does not appear to be registered with
NLM's updated UTS login endpoint (login-prod.nlm.nih.gov). This looks like an
NLM-side service-registration issue rather than a user account problem.

To reproduce

1. Open the README download link
2. Sign in with a valid NIH/UMLS account
3. Observe the "Application Not Authorized" error page

Expected behavior

Redirect to the MedCAT model download form after successful UMLS login.

What I've verified

• UMLS license is active; direct login at https://uts.nlm.nih.gov/uts/ works fine
• Both /auth-callback and /auth-callback-api links produce the same error
• Tried in a fresh browser session

Environment

• MedCAT v2 (latest)
• Attempting to download: v2 SNOMED model pack

Request

Could the callback registration be updated with NLM, or a direct download link
provided in the meantime? Thanks!

[mart-r]

We are aware that the regular auth callback link isn't working. It's because we had to change the domain of the model distributor, and as such the new domain is no longer registered with NIH. We have reached out to change the registration or re-register the new domain, but have unfortunately not received any feedback on that.

With that said, I have just tried the /auth-callback-api endpoint and it works just fine with my API key. In fact, since this works by querying the API key validity in the back end (rather than going to the NIH website) the error message you've described cannot be produced with this method.