Skip to content

First run

A freshly installed instance has no account. Every request is therefore redirected to the setup page (/en/setup, with its own slug per language) as long as no administrator exists.

The only exceptions are the paths without which the wizard could not work: the static assets (/css, /js, /lib, /img, /favicon.ico), /health — so that the installer can wait for the service — and /auth/logout, /auth/confirm and /auth/magic.

An email address and a password, nothing else, with a minimum of 12 characters.

Both the user and their tenant are created — the same route the first redemption of a sign-in link takes in the cloud. An account created here is indistinguishable from a cloud account.

Once setup is complete, every further call redirects to sign-in. Otherwise somebody could walk in and create themselves a second administrator.

If a password was set by somebody else — on the command line or by an administrator — the account is unusable until the holder replaces it: every request from a cookie session lands on the password-change page.

What counts here is the database, not the claim in the cookie — a cookie can be 30 days old.

Then the command line creates the first account:

Terminal-Fenster
cd "C:\Program Files\Invoiceflair\Portal"
Invoiceflair.Api.exe create-owner chef@firma.de --password "a long passphrase" --must-change

--must-change makes sense here, because the password appears on the command line and therefore in the command history. The command also marks setup as complete.

Further commands are set out under Administration on the command line.