Add support for CANONICALIZE_HOST_NAME checks in mongosh

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 1.3.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Iteration Wolverhampton, Iteration Xochimilco
    • Needed
    • Hide

      This is only adding compatibility with the legacy shell, so would only need documentation if the documentation wasn’t already there.

      The --sspiHostnameCanonicalization option now supports all values of the driver CANONICALIZE_HOST_NAME auth mechanism property, i.e. none, forward, forwardAndReverse as well as the legacy true and false options.

      Show
      This is only adding compatibility with the legacy shell, so would only need documentation if the documentation wasn’t already there. The --sspiHostnameCanonicalization option now supports all values of the driver CANONICALIZE_HOST_NAME auth mechanism property, i.e. none , forward , forwardAndReverse as well as the legacy true and false options.

      Once support for the CANONICALIZE_HOST_NAME authentication mechanism property is implemented in the driver (NODE-3351), we have to update the implementation in mongosh on how to handle --sspiHostnameCanonicalization.

            Assignee:
            Anna Henningsen
            Reporter:
            Michael Rose (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: