iiamhuman Developer Docsv1

PERSONHOOD CREDENTIAL INTEGRATION · STEP 11

Publish Your App

Complete Developer Gate publishing, activate your app, and apply the updated config.

Publish Your App

After you have completed testing and confirmed that the integration works as expected, you can publish your app.

Complete the Developer Gate Requirement

Before publishing, open Developer Gate and complete the Publishing registration. Scan the displayed request with your Personhood Credential app and submit a valid Uniqueness credential. This proves that the developer publishing the app meets the platform's uniqueness requirement.

Wait for the Publishing registration to be verified before continuing.

Publish and Update Your App Config

Return to the app configuration page and select Publish app. When publishing succeeds, the app status changes to Active.

Publishing changes the app configuration. Download the app config again, replace the version used by your backend, and redeploy or restart it so it uses the new configuration. Keep request signing material on the backend.

Keep the request-issuer DID you downloaded during registration in the same secure backend secret store. You do not need to download a new request-issuer DID when publishing.

Journal’s environment example

Journal’s checked-in production config for iamhuman-journal has status: "active"; its separate iamhuman-journal-stage config has status: "testing". These are repository configuration values, not a live deployment check. Publish your own production registration and download its current config.

Journal selects the config with DEPLOY_ENV and bundles it into the server build. Rebuild and redeploy after replacing that file. Keep the stage registration, domains, and signing secret separate from production.

Before You Go Live

  • Confirm your production allowed origin, PD fetch domain, and VC submission domain are configured correctly.
  • Verify that your production deployment uses the newly downloaded app config.
  • Run one final end-to-end request on the registered HTTPS host: scan, approve, complete the browser session, choose a name if needed, and publish a comment.
  • Check that anonymous or expired sessions cannot comment, revoked credentials require verification again, and temporary status failures block posting without claiming rejection.

Your app is now active and can accept presentation requests from users.