ACE AESDirect WebLink Recent Change

This message is intended for ACE AESDirect WebLink developers ONLY.

 

Due to mandatory U.S. Customs and Border Protection (CBP) security restrictions that were recently implemented, it will no longer be possible to display AESDirect content in iFrames.  Any ACE AESDirect WebLink software developers currently using iFrames will need to develop an alternate implementation that does not include iFrames. 

 

It is imperative that ACE AESDirect WebLink developers follow the process as outlined in the WebLink Process Overview documentation.  Step #5 is a crucial step (i.e., Clicking the Submit AESDirect Filing) that triggers some events in the background that are critical to current and future functionality.  The ACE AESDirect WebLink outage experienced by some users after the August 2nd AESDirect deployment was caused by missing step #5.   Future deployments of AESDirect will expose this implementation omission again. 

 

Similarly with the ACE AESDirect WebLink Test Environment, it is imperative that ACE AESDirect WebLink developers follow the process as outlined in the WebLink Test Process Overview documentation.  Step #5 (i.e., Clicking the Submit AESDirect Filing) and Step #6 (i.e., navigating to the SessionBroker URL) are critical steps that the AESDirect Support Team has observed were missed.  Again, the omission of these steps will be exposed upon a future deployment of AESDirect with outages for the users of ACE AESDirect WebLink software.

 

For more information regarding these changes please contact the U.S. Customs and Border Protection at ASKACE@CBP.DHS.GOV.