SUSECONNECT(8)

πŸ“¦ version 1.23.0, in opensuse-leap 16.0

πŸ’… SUSECONNECT β€” like, the SUSEConnect manual page, bestie (section 8, SUSECONNECT(8) energy) πŸŽ€

okay so listen. this is the whole vibe of SUSEConnect, the SUSE Customer Center registration tool. everything's here, nothing's missing, pinky promise 🫢


✨ NAME ✨

SUSEConnect β€” the SUSE Customer Center registration tool, aka the little guy that gets your machine officially on the internet with SUSE πŸ’–


🌸 SYNOPSIS 🌸

SUSEConnect [<optional>...]  -p PRODUCT

that's it. that's the shape of it. iconic.


πŸ¦‹ DESCRIPTION πŸ¦‹

So basically: SUSEConnect registers your SUSE Linux Enterprise installations with the SUSE Customer Center. Why do we care? Because registering is literally what unlocks access to software repositories (updates included, bestie, updates included) and it lets you manage your subscriptions and organizations online. main character access only πŸ”₯

By default, SUSEConnect registers the base SUSE Linux Enterprise product installed on your system. But it can also register extensions and modules β€” yes, more ✨

Wanna register an extension or a module? Use the --product <PRODUCT-IDENTIFIER> option together with the product identifier of that extension or module. And if you wanna peek at everything available? Hit --list-extensions and see the full menu of extensions and modules for your system. iykyk πŸ’…

Manage your subscriptions at the SUSE Customer Center: https://scc.suse.com β€” go, be responsible, slay πŸ‘‘


🌈 OPTIONS 🌈

okay this is the big one. every single flag, no skips, no cap:

  • -p, --product <PRODUCT> β€” picks which product to activate/deactivate. Only one product at a time, so don't get greedy πŸ™ˆ. Defaults to the base SUSE Linux Enterprise product on this system. You get product identifiers from --list-extensions. Format: <name>/<version>/<architecture>
  • -r, --regcode <REGCODE> β€” the subscription registration code for the product you're registering. It ties that product to the specified subscription and turns on software repositories for it. Cute bonus: -r - passes the registration code via stdin, and -r @/file/path points at a file containing the code. versatile icon πŸ’…
  • -d, --de-register β€” de-registers the system and base product, or (with --product) just a single extension, and removes all its services installed by SUSEConnect. after this the system no longer consumes a subscription slot in SCC. bye bestie 🫢
  • -l, --list-extensions β€” lists all extensions and modules available for installation on this system. window shopping ✨
  • --instance-data <path to file> β€” path to the XML file holding the public key and instance data for cloud registration with SMT
  • -e, --email <email> β€” email address for product registration
  • --url <URL> β€” URL of the registration server (e.g. https://scc.suse.com)
  • --namespace <NAMESPACE> β€” namespace option for use with SMT staging environments
  • -s, --status β€” gets current system registration status in json format
  • --status-text β€” gets current system registration status in text format
  • --keepalive β€” sends a keepalive call to the registration server so it can detect which systems are still running. "i'm alive" but make it protocol πŸ’€
  • --write-config β€” writes options to the config file at /etc/SUSEConnect
  • --cleanup β€” removes old system credentials and all zypper services installed by SUSEConnect. spring cleaning 🌸
  • --rollback β€” reverts the registration state in case of a failed migration
  • --root <PATH> β€” path to the root folder, uses the same parameter for zypper
  • --gpg-auto-import-keys β€” automatically trust and import new repository signing keys
  • --version β€” prints program version
  • --debug β€” provides debug output
  • --json β€” prints output in JSON format. ⚠️ this flag is only supported for registering, de-registering and list-extensions β€” so don't try it on everything, it will not serve πŸ’€
  • -h, --help β€” shows help message

πŸŽ€ EXIT CODES πŸŽ€

SUSEConnect sets these exit codes, and yes we're listing all of them:

  • 0: Registration successful πŸŽ‰
  • 64: Connection refused
  • 65: Access error, e.g. files not readable
  • 66: Parser error: Server JSON response was not parseable
  • 67: Server responded with error: see log output

πŸ’œ COMPARED TO SUSE_REGISTER πŸ’œ

⭐ BEFORE

suse_register -a email=<email> -a regcode-sles=<regcode> -L <logfile>

⭐ AFTER

SUSEConnect --url <registration-server-url> -r <regcode> >> <logfile>

glow-up complete, honestly ✨


🧚 USE WITH REGISTRATION PROXY 🧚

SUSEConnect can also be used to register systems with a local SUSE registration proxy (RMT/SMT) instead of the SUSE Customer Center. Just use SUSEConnect --url <registration-proxy-server-url> to register systems with RMT/SMT. local legend behaviour πŸ’…


πŸ‘‘ IMPLEMENTATION πŸ‘‘

SUSEConnect is implemented in Golang. It talks to the registration server using a RESTful JSON API over HTTP, wrapped in TLS encryption. secure, modern, doing the most (affectionate) πŸ”₯


🌟 ENVIRONMENT 🌟

SUSEConnect respects the HTTP_PROXY environment variable. See https://www.suse.com/support/kb/doc/?id=000017441 for more details on how to manually configure proxy usage. proxy bestie, we got you 🫢


πŸ“ FILES πŸ“

  • /etc/SUSEConnect β€” configuration file containing server URL, regcode and language for registration

πŸ’– AUTHOR πŸ’–

SUSE LLC (<scc-feedback@suse.de>)


SUSE Customer Center: https://scc.suse.com

SUSEConnect on GitHub: https://github.com/SUSE/connect-ng


πŸ’€ SEE ALSO πŸ’€

SUSEConnect(5)


this page was cooked up in January 2022, and it's page SUSECONNECT(8) of the manual, in case you were wondering. now go register something, you gorgeous nerd 🧚✨πŸ’