Registry#

Behavior#

Generate user request#

' Copyright 2026 the contributors of APPXC (github.com/alexander-nbg/appxc) ' SPDX-License-Identifier: 0BSD @startuml |User Application| start ->UI opens; if (admin keys) then (available) :UI opens (no load admin keys button); else (missing) :UI opens (with load admin keys button); endif; stop @enduml

Update User Database#

? this diagram sounds technical (calling registry)

' Copyright 2026 the contributors of APPXC (github.com/alexander-nbg/appxc) ' SPDX-License-Identifier: 0BSD @startuml |User Interface| start ->registry shall add user with role from request data; |Registry| switch (check public keys) case (all new) :use new user ID upate registry; case (consistent set) :use existing user ID update registry; case (inconsistent set) :to indicate error: use negative user ID no registry update; endswitch |User Interface| ->return with user ID; stop @enduml

Checking Public Keys#

The registry stores the public signing key and the public encryption key which also serve as an identification. They must be unique. Hence, if any of the signing or encryption keys already exists, a new user must not be added. There are two cases:

  • the keys are consistent:

    • eventually new user data will be updated

  • one key already exists but the other key(s) for the user entry is inconsistent to the keys from the request

    • a negative user ID is returned to indicate an error (fail operational)

Alternative: Inconsistent Keys#

An alternative to returning a negative user ID would be to raise an error. Consequences:

  • try/catch in calling user interface

    • fair enough to demand a safe integration

  • which error class to use? Error class options:

  • a custom error class to allow precise filtering within try/catch?

    • (-) added complexity even if APPXC custom error classes are commonly used

  • an existing error class

    • (-) not possible to filter for this situation in UI The negative user ID is preferred since it makes this particular error transparent without adding a specific error code.

v0.0.4.dev4
Page Status
Draft collecting drafts and still containing alternative analysis (2026/03)
On this page
Show Source