Secret Parameter Actions

Content Authoring
21

So you have some 753 instances that look like

<Target>
  <ComputerID>123456</ComputerID>
  <ComputerID>234567</ComputerID>
</Target>

I think I’m seeing the same, even with only one computer. When posting an action with a SecureParameter, any invalid <ComputerID> target gives the HTTP 200 response. An action that does not have a SecureParameter sent to an invalid <ComputerID> does send the action, but it won’t have any targeted computers when viewed in the Console.

This is probably related to how the server must look up the encryption keys to each targeted endpoint, so it can propagate actions that are encrypted specifically to those machines. I think this may be working the way it’s expected to.

Would it help to run a session relevance first to check that all of your targeted computer IDs are valid? a fairly quick check might be

elements of intersection of (
/* set of computer IDs to check */
set of (
 1076999036 ; 
 1078737986 ;
 11111111 ;
 1081508528 
 ) 
; set of ids of bes computers
)
22

To get my target computer list, I’m getting the list of computer IDs of the relevant computers of the target fixlet. So the IDs should valid. It seems like more of a capacity issue,