To upload your snap to the Snap Store and access its management web interface, you will need a developer account. If you don’t already have one, creating one is easy.
The account is registered on Ubuntu One, a single sign-on service for Ubuntu and affiliated projects. Head over to https://snapcraft.io/account and select the “I don’t have an Ubuntu One account” option.
Fill out the form that appears. Your “full name” and “username” will be displayed next to your app in the Snap Store, so you should choose appropriate branding. Use your organisation’s name for both if you are publishing on their behalf.
You will then receive an email asking you to verify your account. Click the verification link in the email and complete the reCAPTCHA challenge that follows.
Finally, you will be asked to review the terms of the developer programme. If you wish to revisit these at any time you can find them here:
Once you have accepted the terms, your developer account is immediately ready to start publishing snaps. The details of your account can be reviewed at any time from the menu on the top right.
It can be retrieved with the snapcraft command by first logging in to your Ubuntu One account:
$ snapcraft login Enter your Ubuntu One e-mail address and password. If you do not have an Ubuntu One account, you can create one at https://snapcraft.io/account Email: <your email address> Password: Second-factor auth: 960067 Login successful.
And following a successful login, the
snapcraft whoami command reveals your developer-id:
$ snapcraft whoami email: <your email address> developer-id: xSfWKGdLoQBoQx88vIM1MpbFNMq53t1f
In the example output above, the developer-id is
The contents of one or more SSH public keys can be added to, and associated with, your Ubuntu One account.
This is an essential step if you want to install Ubuntu Core because a registered private/public key pair is used to access the device using SSH after installation.
If you don’t already have an SSH key pair, or would like to use a new one, the following command will generate a new pair:
$ mkdir -p ~/.ssh $ chmod 700 ~/.ssh $ cd ~/.ssh $ ssh-keygen -t rsa
You will be prompted for a filename and then for a passphrase. We recommend using a filename unique for this role, such as
ucid_rsa. Adding a passphrase secures against your private key being compromised, but it will need to be entered whenever the key is used.
Generating public/private rsa key pair. Enter file in which to save the key (/home/ubuntu/.ssh/id_rsa): ucid_rsa Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in ucid_rsa Your public key has been saved in ucid_rsa.pub The key fingerprint is: SHA256:SCFVqXpDet/ZFKUxNYXkrJFpxz4n6QtI4S9KMgVZh14 ubuntu@2004-desktop The key's randomart image is: +---[RSA 3072]----+ | +*AC. o.. | | .+.X=o=..E | | . B.-=. . | | . *o+ o*. | |+ . . +oSo. | |+o.. . o | | o..... . | | .S. | | ..o. | +----[SHA256]-----+
The output is a 2048-bit RSA key pair which is secure enough for most use cases (you may optionally pass in the
-b 4096 flag to the
ssh-keygen command, to create a larger 4096-bit key).
The contents of the
<key name>.pub file (not the private key without an extension) now need to be pasted into the Public SSH Key field on https://login.ubuntu.com/ssh-keys, such as with xclip:
$ cat ~/.ssh/ucid_rsa.pub | xclip sh-rsa AAAAB3N[...]ubuntu@2004-desktop
Press the Import SSH key button to complete the import process.
The key should now be listed beneath SSH Keys at the top of the page which means the key has been recognised and is ready to use. Old and redundant keys should be removed with the ‘Delete selected keys’ button to avoid the potential security risk of someone using an old key.
Last updated 2 days ago. Help improve this document in the forum.