Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
SubZer0
Collaborator

Threat Extraction API key automatically changed regenerated after upgrade to R82?

Hi everyone,

I have a question regarding the Threat Extraction (TE) API. At a customer site, we have a web application integrated via the TE API where partners can upload documents. These documents are then sent via API to the Security Gateway TE blade to be scanned.

The setup works great, but today we ran into an issue where the API key on the Security Gateway changed automatically. There were no configuration changes made on the firewall this week, but last Monday we upgraded the gateway from R81.20 to R82. Document uploading has been used every single day, so the API key didn't change immediately during the upgrade itself. However, we initially activated this API key about a year ago.

I would like to know: Does the TE API key have some sort of built-in expiration timer causing it to automatically regenerate/change after a certain period, or is there another reason for this automatic change?

Thanks in advance for any insights!

0 Kudos
1 Reply
AI-Bot
AI Assistant:

AI-generated answer by CheckMates AI, approved by a moderator. It can contain mistakes, so check it against the linked guides.

There is no documented one-year expiration or scheduled automatic rotation for the local Threat Extraction Web API key in R81.20 or R82. Both versions document the same key-handling procedure; neither describes an age-based renewal mechanism. (R81.20 guide, R82 guide)

What can generate a new key?

The key is stored in the api_key field of:

/opt/CPUserCheckPortal/phpincs/conf/TPAPI.ini

Importantly, sk113599 states that configure_scrub_web_service.sh enable generates a random API key if no API key is configured. It does not describe periodically replacing an existing key. Changes to TPAPI.ini take effect immediately. (sk113599)

That makes a missing or cleared key during API configuration a possible explanation—but it does not establish that this happened at your site. I did not find a documented R81.20-to-R82 issue matching the delayed regeneration you describe.

What to check next

  1. Compare the current api_key privately with the application's configured key and, if available, a securely retained pre-upgrade copy. This distinguishes an actual key change from an authentication failure.
  2. Correlate the first failed upload with gateway events: policy installations, UserCheck/service restarts, and any changes or replacement of TPAPI.ini. These are investigation points, not confirmed causes.
  3. Open a Check Point Support case if the value genuinely changed without intervention. Include the upgrade method, R82 Jumbo Hotfix take, last successful/first failed request timestamps, and sanitized API errors. I cannot check the gateway directly or determine which process changed the file.

For recovery, you can securely deploy the current key to the application, or explicitly set the intended key in TPAPI.ini; the R82 guide documents that manual key changes are effective immediately. Preserve the current state before changing it, and do not post either key or the full file publicly. (R82 guide)

If this solves your question, please mark it as the solution. Everyone is welcome to add to it.

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events