|Summary:||[RFE] Support reverse chap in iSCSI login|
|Product:||[oVirt] ovirt-engine||Reporter:||Ayal Baron <abaron>|
|Component:||RFEs||Assignee:||Rob Young <royoung>|
|Status:||CLOSED WONTFIX||QA Contact:||Raz Tamir <ratamir>|
|Version:||---||CC:||bsettle, bugs, dfediuck, lpeer, pmatouse, rbalakri, Rhev-m-bugs, security-response-team, srevivo, ylavi|
|Target Milestone:||---||Keywords:||FutureFeature, Improvement, Reopened, Security, StudentProject|
|Fixed In Version:||Doc Type:||Enhancement|
|Doc Text:||Story Points:||---|
|Last Closed:||2018-05-16 10:28:24 UTC||Type:||---|
|oVirt Team:||Storage||RHEL 7.3 requirements from Atomic Host:|
Description Ayal Baron 2010-06-09 12:41:11 UTC
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Comment 1 Petr Matousek 2010-06-09 12:48:52 UTC
ain't this duplicate of #595608?
Comment 2 Ayal Baron 2010-06-09 13:01:48 UTC
Nope. That one is for GUI to remove the params. This one is for us to actually support it :)
Comment 3 Petr Matousek 2010-06-09 13:10:13 UTC
(In reply to comment #2) > Nope. That one is for GUI to remove the params. > This one is for us to actually support it :) Isn't #595453 for removing it and #595608 for implementing it right? Don't get me wrong, I don't want to play with words, just would like to track one BZ entry -)
Comment 4 Ayal Baron 2010-06-09 14:02:43 UTC
(In reply to comment #3) > (In reply to comment #2) > > Nope. That one is for GUI to remove the params. > > This one is for us to actually support it :) > > Isn't #595453 for removing it and #595608 for implementing it right? Correct, I didn't see the first one, but in any event 595608 is for GUI. Once GUI passes the params to backend (different component), backend would still have to pass them to vdsm (another component) which would have to actually handle the reverse chap. So all in all, there should be 3 BZs for this RFE, this one being the first, the backend one depending on it and the GUI one depending on the backend BZ. For anything we don't mean to implement anytime soon we have a single BZ on the RFEs component. > > Don't get me wrong, I don't want to play with words, just would like to track > one BZ entry -)
Comment 5 Petr Matousek 2010-06-09 15:06:17 UTC
> So all in all, there should be 3 BZs for this RFE, this one being the first, > the backend one depending on it and the GUI one depending on the backend BZ. fair enough
Comment 6 Yaniv Kaul 2012-03-19 12:24:04 UTC
Setting as StudentProject - while not very complex, requires changes in several component (VDSM, core engine, API, UI). I believe just VDSM support is a great student level project.
Comment 7 Itamar Heim 2012-12-10 19:10:48 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
Comment 11 Doron Fediuck 2018-05-16 10:28:24 UTC
Closing old bugs. If needed please reopen and explain why.