The Samsung author and distributor certificates come from Certificate Manager in Tizen Studio, which offers them only once the Samsung Certificate Extension is installed from Package Manager. The panel signs the .wgt with that pair; you register the app in Seller Office, upload the package and the store assets, and request certification. Plan around two constraints: a new seller launches in the US only, and certification runs for weeks.
Distribution scope: Seller Office admits new members as public sellers, and a public seller's apps can launch in the United States only. Any other country requires partner status, which Samsung grants through its regional content teams.
No Samsung Certificate Extension in the list? Its repository is switched off. Open the gear icon at the top right of Package Manager, find the Extension SDK repositories, set the Samsung entry to on and reload the tab. Take the update it offers while you are there: Samsung withdrew certificate creation from releases before 2.0.74 in September 2025, so an older extension fails at the author step.
The author certificate is permanent. Samsung verifies every update against the author certificate of the first release, and a package signed by any other author is refused. Keep an offline backup of the .p12 and its password for the life of the app.
Signing locally instead? With no certificates on file, the Samsung build returns the Tizen source (.zip) for you to package and sign in Tizen Studio.
Frequent rejection causes: Back-key handling and incomplete test details. The template implements Samsung's Back rules (up one level, exit dialog on Home, long presses ignored), which leaves the test details as the part to get right.
Rebuild Samsung in the panel with the original author certificate still on file, upload the new .wgt as a new version, and request certification again. Videos, logo and links come from the feed and need no new version.
Where the Samsung Certificate Extension comes from, what each certificate does, what Samsung's certification tests, and whose account publishes the app.