Supply attributes through a pipeline session
Step 4 of 4 in Issue credentials.
Provide attributes as late as possible: seed short connector fields at session start and let connector invocations fetch authoritative values when the wallet calls the credential endpoint. Manual contribution is for backend and admin cases.
contributorId in contribution bodies is provenance, not the runtime connector binding. Completeness
reports, per claims binding, the missingRequiredPaths. With missingRequiredClaims: defer on the issuer
and no explicit deferral policy on the binding, the credential endpoint returns a deferred response
(transaction_id) instead of an error. Attributes are encrypted in the session and deleted by
the retention policy.
Next
This completes the journey. Continue with Prove the credential status profiles.