XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    invalid credentials in new installation from source

    Scheduled Pinned Locked Moved Xen Orchestra
    9 Posts 4 Posters 898 Views 5 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • GriAleG Offline
      GriAle
      last edited by

      Try install 5.72.0 in

      Operating System: Debian GNU/Linux 11 (bullseye)
                  Kernel: Linux 5.10.0-15-amd64
            Architecture: x86-64
      

      and when try first connect in web invalid credentials in console

      2022-07-05T15:29:22.545Z xo:authentification ERROR no available algorithm with id argon2id {
        error: Error: no available algorithm with id argon2id
            at getAlgorithmFromId (/root/xen-orchestra/node_modules/hashy/index.js:189:11)
            at getAlgorithmFromHash (/root/xen-orchestra/node_modules/hashy/index.js:196:10)
            at verify (/root/xen-orchestra/node_modules/hashy/index.js:293:10)
            at /root/xen-orchestra/node_modules/hashy/index.js:33:22
            at Promise._execute (/root/xen-orchestra/node_modules/bluebird/js/release/debuggability.js:384:9)
            at Promise._resolveFromExecutor (/root/xen-orchestra/node_modules/bluebird/js/release/promise.js:518:18)
            at new Promise (/root/xen-orchestra/node_modules/bluebird/js/release/promise.js:103:10)
            at verify (/root/xen-orchestra/node_modules/hashy/index.js:32:9)
            at default.checkUserPassword (file:///root/xen-orchestra/packages/xo-server/src/xo-mixins/subjects.mjs:311:26)
            at file:///root/xen-orchestra/packages/xo-server/src/xo-mixins/authentication.mjs:53:20
            at default._authenticateUser (file:///root/xen-orchestra/packages/xo-server/src/xo-mixins/authentication.mjs:117:24)
            at default.authenticateUser (file:///root/xen-orchestra/packages/xo-server/src/xo-mixins/authentication.mjs:162:20)
            at Strategy._verify (file:///root/xen-orchestra/packages/xo-server/src/index.mjs:289:26)
      
      
      GriAleG julien-fJ 2 Replies Last reply Reply Quote 0
      • GriAleG Offline
        GriAle @GriAle
        last edited by

        @GriAle
        admin@admin.net / admin

        1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          Hi,

          Have you followed https://xen-orchestra.com/docs/installation.html#from-the-sources ?

          GriAleG 1 Reply Last reply Reply Quote 1
          • ronivayR Offline
            ronivay Top contributor
            last edited by ronivay

            I can reproduce this (ref: https://github.com/ronivay/XenOrchestraInstallerUpdater/issues/133) and it seems to be caused by commit: https://github.com/vatesfr/xen-orchestra/commit/49890a09b7a3c4bcbe7f462577c6d0a7da8b7006

            If you start from fresh (no redis database specifically) and install from that commit, or latest master, the default user creation doesn't work properly and above mentioned error is present in xo-server logs. It's actually all user creations (their passwords to be exact), not just default user. Doesn't affect existing users so if updating from previous version, everything seemingly works fine until new user is created and login with it fails.

            If installing from commit: https://github.com/vatesfr/xen-orchestra/commit/dfce56cee8023ce0dc9292e0c1dda5e6937910e5 with fresh redis database, all works as it should. Also if broken admin@admin.net user was already created with installation from newer commit and redis database wasn't cleared, resetting user password with recover-account-cli.mjs in installation from this commit brings it back to life again.

            rjlan created this issue in ronivay/XenOrchestraInstallerUpdater

            closed invalid credentials on login to fresh install #133

            0 julien-f committed to vatesfr/xen-orchestra
            chore: update dev deps
            0 julien-f committed to vatesfr/xen-orchestra
            feat(async-each): add basic JsDoc typing
            GriAleG 1 Reply Last reply Reply Quote 1
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              @julien-f can you take a look?

              1 Reply Last reply Reply Quote 0
              • julien-fJ Offline
                julien-f Vates 🪐 Co-Founder XO Team @GriAle
                last edited by

                @GriAle Investigating.

                1 Reply Last reply Reply Quote 0
                • GriAleG Offline
                  GriAle @ronivay
                  last edited by

                  @ronivay
                  thx its fix
                  https://github.com/ronivay/XenOrchestraInstallerUpdater/issues/133#issuecomment-1175317853

                  rjlan created this issue in ronivay/XenOrchestraInstallerUpdater

                  closed invalid credentials on login to fresh install #133

                  1 Reply Last reply Reply Quote 0
                  • GriAleG Offline
                    GriAle @olivierlambert
                    last edited by

                    @olivierlambert
                    yes i try on clear install Debian 11 and after update and always get this error

                    julien-fJ 1 Reply Last reply Reply Quote 0
                    • julien-fJ Offline
                      julien-f Vates 🪐 Co-Founder XO Team @GriAle
                      last edited by

                      @GriAle Should be fixed: https://github.com/vatesfr/xen-orchestra/commit/ba03a4849831deecda7b8139374b5c43bf90d2b3

                      0 julien-f committed to vatesfr/xen-orchestra
                      chore(xo-server): update to hashy@0.11.1
                      
                      Fixes https://xcp-ng.org/forum/post/50866
                      
                      Introduced by 49890a09b7a3c4bcbe7f462577c6d0a7da8b7006
                      
                      Fixes argon2id support which is the new default algorithm since argon2@0.28.7
                      1 Reply Last reply Reply Quote 2
                      • First post
                        Last post