1. 09 May, 2023 3 commits
  2. 07 May, 2023 1 commit
  3. 03 May, 2023 1 commit
    • Andrew Walker's avatar
      Fix activedirectory.leave endpoint (#11221) · 5c7a0272
      Andrew Walker authored
      Fixes for SEE-related ticket where support engineer was deliberately
      breaking AD by deleting kerberos settings while we were joined to AD
      caused a regression in activedirectory plugin.
      5c7a0272
  4. 02 May, 2023 2 commits
  5. 28 Apr, 2023 1 commit
  6. 26 Apr, 2023 1 commit
  7. 20 Apr, 2023 1 commit
  8. 19 Apr, 2023 2 commits
  9. 17 Apr, 2023 1 commit
  10. 11 Apr, 2023 2 commits
  11. 08 Apr, 2023 1 commit
  12. 07 Apr, 2023 1 commit
    • Andrew Walker's avatar
      Backport SCALE activedirectory-related fixes to Core (#11012) · 579b4210
      Andrew Walker authored
      This backports a fundamental design change to no longer use python
      bindings into libnet / libads in the activedirectory plugin. This
      is generally more reliable. Information we were gleaning from the
      python bindings can be gotten through subprocessing out to net
      commands. This commit also fixes an edge case where kerberos errors
      would not be properly turned into ValidationError while checking
      user-provided passwords.
      579b4210
  13. 30 Mar, 2023 2 commits
  14. 29 Mar, 2023 1 commit
  15. 23 Mar, 2023 1 commit
  16. 15 Mar, 2023 1 commit
  17. 10 Mar, 2023 1 commit
  18. 09 Mar, 2023 2 commits
  19. 08 Mar, 2023 1 commit
  20. 01 Mar, 2023 1 commit
  21. 28 Feb, 2023 1 commit
  22. 27 Feb, 2023 1 commit
  23. 21 Feb, 2023 1 commit
    • Andrew Walker's avatar
      Ensure that DOSATTRIB xattr is disabled (#10728) · e5af99be
      Andrew Walker authored
      This reverts a change to default parameters that was made
      between 13.0-U3.1 and 13.0-U4. Initial plan was to normalize
      how DOS attributes are stored between SCALE and Core (specifically
      as regards how file ids are generated and used), but upstream
      has since reverted changes to store a synthesized fileid based
      on inode birth time. Our temporary plan for now is to switch
      back to using inode number for this purpose (while evaluating
      other means of handling these).
      e5af99be
  24. 13 Feb, 2023 1 commit
  25. 07 Feb, 2023 1 commit
  26. 31 Jan, 2023 1 commit
  27. 30 Jan, 2023 2 commits
  28. 24 Jan, 2023 1 commit
  29. 19 Jan, 2023 2 commits
  30. 18 Jan, 2023 1 commit
  31. 14 Jan, 2023 1 commit