Project

General

Profile

Bug #41496

Convert WebDAV to use websocket call

Added by Tommie James about 2 years ago. Updated about 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
Erin Clark
Category:
GUI (new)
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

When configuring WebDAV HTTPS the certificate selection isn't retained after saving. The selection HTTPS or HTTP + HTTPS and password however are retained.

Associated revisions

Revision 0bfae164 (diff)
Added by Erin Clark about 2 years ago

Convert webdav to use websocket call to fix issues Ticket: #41496

History

#1 Updated by Dru Lavigne about 2 years ago

  • Private changed from No to Yes
  • Reason for Blocked set to Need additional information from Author

Tommie: please attach a debug (System -> Advanced -> Save debug) to this ticket.

#2 Updated by Tommie James about 2 years ago

  • File debug.tgz added

As requested, debug attached.

#3 Updated by Dru Lavigne about 2 years ago

  • Category changed from Services to Middleware
  • Assignee changed from Release Council to William Grzybowski
  • Reason for Blocked deleted (Need additional information from Author)

#5 Updated by William Grzybowski about 2 years ago

  • Assignee changed from William Grzybowski to Waqar Ahmed
  • Target version changed from Backlog to 11.2-BETA3

Waqar, can you please investigate this and see if its either a middleware or UI issue? Thank you!

#6 Updated by Waqar Ahmed about 2 years ago

  • Status changed from Unscreened to In Progress

#7 Updated by Waqar Ahmed about 2 years ago

  • Status changed from In Progress to Unscreened
  • Assignee changed from Waqar Ahmed to Erin Clark

So from the Middlewared's end, the https certificate is being saved as it should be. After a quick investigation, I found that new UI was not displaying the cert field as set to the value the user previously had selected. This means that if the end user wants to update the configuration for webdav again, he must select the cert value again giving the impression that it the cert wasn't saved in the backend.

I have verified the contents of the calls as well which new ui makes and it is definitely getting the cert value as set.

Erin, could you kindly look into this ? Thank you

#8 Updated by Waqar Ahmed about 2 years ago

  • Category changed from Middleware to GUI (new)

#9 Updated by Erin Clark about 2 years ago

  • Status changed from Unscreened to In Progress

It appears the rest call wasn't returning the certificate, the websocket call does though so I converted the page to use websocket instead.

https://github.com/freenas/webui/pull/1150

#10 Updated by Erin Clark about 2 years ago

  • Status changed from In Progress to Ready for Testing

#11 Updated by Dru Lavigne about 2 years ago

  • File deleted (debug.tgz)

#12 Updated by Dru Lavigne about 2 years ago

  • Subject changed from WebDAV Service Configuration Issue to Convert WebDAV to use websocket call
  • Private changed from Yes to No
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#13 Updated by Timothy Moore II about 2 years ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No

Testing with FreeNAS system updated to FreeNAS-11.2-MASTER-201808290900:

Log in and go to Services > WebDAV > CONFIGURE. Update this page to use HTTP + HTTPS Protocol, and attached test-cert to Webdav SSL Certificate. Click SAVE, then click CONFIGURE to view the options again. The changes appear, including the certificate.

#14 Updated by Dru Lavigne about 2 years ago

  • Status changed from Passed Testing to Done

Also available in: Atom PDF