Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-26339

Account specifics to be handled before proxying

Details

    Description

      • account locking should apply to the account before proxying
      • ssl checks should be done before proxying
      • password expiration should be checked before proxying

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          wlad Vladislav Vaintroub added a comment - - edited

          maybe account locking should apply both before and after proxying, for both accounts, anyway this is a little ambiguous.

          wlad Vladislav Vaintroub added a comment - - edited maybe account locking should apply both before and after proxying, for both accounts, anyway this is a little ambiguous.
          ralf.gebhardt Ralf Gebhardt added a comment -

          True, none of the accounts should be used if locked.

          ralf.gebhardt Ralf Gebhardt added a comment - True, none of the accounts should be used if locked.
          ralf.gebhardt Ralf Gebhardt added a comment -

          This has been discussed again. Only for the connecting user it should be checked if the account is locked. After proxying is an internal usage, like done with other locked system accounts

          ralf.gebhardt Ralf Gebhardt added a comment - This has been discussed again. Only for the connecting user it should be checked if the account is locked. After proxying is an internal usage, like done with other locked system accounts

          People

            serg Sergei Golubchik
            ralf.gebhardt Ralf Gebhardt
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.