Message bus probe is unable to perform the resync when the target system requires a multi-step authentication flow

Currently, the probe is unable to perform native resync when the target system requires a multi-step authentication flow, specifically:
a. Resync request requires a valid token and Token can only be generated using a ticket
b. Ticket itself is generated via a separate authentication API call
Because of this dependency chain, probe resync does not work out-of-the-box.
Current Limitation
-------------------
Probe resync supports only:
Single-step token or basic authentication
In our case:
--------------
Resync requires dynamic ticket generation and Ticket must be exchanged for a token
Token must be attached to the resync API request
Probe doesnt support to create the ticket and using that ticket it doesnt create the token
Current Workaround (Not Ideal)
-----------------------------------
Implemented a separate wrapper script that:
Generates ticket
Exchanges ticket for token
Triggers resync externally

Expected Enhancement (Request to Product Team)
=========================================
We request native support at probe level for multi-step authentication-based resync, without relying on external wrapper scripts.
Requested Capabilities
Pre-Resync Authentication Workflow
Ability to define one or more authentication steps before resync
Example:
Step 1: Get ticket
Step 2: Exchange ticket for token
Step 3: Perform resync using token

Resync Triggered
   ↓
Call Auth API → Generate Ticket
   ↓
Call Token API → Generate Token using Ticket
   ↓
Attach Token to Headers
   ↓
Call Resync API
   ↓
Process and normalize events