Fix x509 username being required in connection string building and parsing

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 0.3.0
    • Affects Version/s: None
    • Component/s: Connectivity
    • None
    • 1
    • Iteration Papaya
    • Not Needed

      Currently when a user hasn't passed an x509 username, our connection model builds a connection string which still has a username field included in it. Similarly, when parsing a connection string, we require this x509 username to be there.

      This task involves updating our connection string building and parsing to allow for x509 username to be optional.

            Assignee:
            Rhys Howell
            Reporter:
            Rhys Howell
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: