LaaS CLI problems and fixes

Read the full response and verify the intended operation. Administrative HTTP rejection can accompany exit zero. Credential validation can print a positive headline for a negative decision; neither is an acceptance test.

Read a known ID and use the approved complete-inventory interface. Customer page numbers do not advance the service cursor; license list reads one response window. Version 0.5.36 can omit group relationships from its results; the current development version improves lookup but still omits organizational paths. Do not infer missing records or replay grants from partial output.

Preserve active and backup paths without printing secret contents. Activation may consume a code before local persistence fails, and restoration is not guaranteed. login --check attempts renewal; use it only when that attempt is intended. Resolve the failed phase before retrying.

Confirm OpenSSL, the approved certificate/key pair and input format. Export needs an unencrypted PKCS#8 PRIVATE KEY block and complete LF-terminated PEM markers. A counted key or successful inspection does not prove compatibility. Protect passwords in command arguments and do not import partial output.

Check laas version and the installation owner’s replacement process. Staging is not installation and the next launch does not apply it. For an authorized unattended download use laas update --force; force does not skip verification. Confirm an authorized read after replacement.

Run laas doctor and inspect failed, warning and skipped checks. The command is non-strict, cached observations may be old, and a healthy connection is not permission. Keep codes, private keys and full credential contents out of support reports.