somiljain2006 opened a new pull request, #8113:
URL: https://github.com/apache/incubator-seata/pull/8113

   - [x] I have read the 
[CONTRIBUTING.md](https://github.com/apache/incubator-seata/blob/2.x/CONTRIBUTING.md)
 guidelines.
   - [x] I have registered the PR 
[changes](https://github.com/apache/incubator-seata/tree/2.x/changes).
   
   ### Ⅰ. Describe what this PR did
   
   - Added allow-downloads to the sandboxed iframe so export/download 
operations are no longer blocked by the browser.
   - Fixed stale edge source/target references during export after renaming 
tasks with Catch transitions.
   - Added defensive handling for missing Catch collections during export.
   - Updated security ignore rules for Saga designer static resources and 
frontend assets to avoid authentication-related loading failures after token 
expiration.
   
   ### Ⅱ. Does this pull request fix one issue?
   
   Fixes #7274
   
   ### Ⅲ. Why don't you add test cases (unit test/integration test)? 
   
   Added integration tests for security/static-resource behavior in 
WebSecurityConfigTest.
   
   ### Ⅳ. Describe how to verify it
   
   1. Start the naming server and open the Saga StateMachine Designer.
   2. Verify the designer loads successfully without static resource 
authentication failures.
   3. Create a simple state machine and export/download JSON or SVG.
   4. Confirm downloads succeed and the browser console no longer shows:
   5. Download is disallowed
   6. Create tasks with a Catch transition, rename the source task, and export 
again.
   7. Verify the exported JSON uses the renamed task consistently without stale 
references.
   8. Reduce JWT expiration time, wait for token expiry, refresh the page, and 
verify static JS/CSS/font resources still load correctly and protected APIs 
still return 401 Unauthorized.
   
   ### Ⅴ. Special notes for reviews
   
   N/A


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to