Trading partner

How it works

The partner profile holds the host, the key, the folder, and the schedule. A transfer job points at a profile. Changing a key is a profile change, not a code change, if you built it that way.

Three suppliers each have an SFTP profile. Supplier two rotates a host key. Only that profile updates. The other jobs keep running. A shared config file would have stopped all three.

How it differs

A trading partner is not a client portal user. One is a system relationship. The other is a person with a password.

A partner profile with a shared password and no owner becomes unrotatable.

Name an owner.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For trading partner, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive trading partner files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.