| Summary: | Cannot re-login once logged in with wrong user ID in remote login dialog. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] Target Management | Reporter: | Loganathan <loganathan001> | ||||
| Component: | RSE | Assignee: | dsdp.tm.rse-inbox <tm.rse-inbox> | ||||
| Status: | NEW --- | QA Contact: | Martin Oberhuber <mober.at+eclipse> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | dmcknigh | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Loganathan
Created attachment 173165 [details]
This image shows the user id field disable, without giving chance to change the wrong user ID.
This image shows the user id field disable, without giving chance to change the wrong user ID.
What kind of connection is being used in this case? That dialog looks like an SSH connection prompt. If you reconnect via right-mouse-click on the Files subsystem ->"Connect..." do you get the RSE prompt? (In reply to comment #2) > What kind of connection is being used in this case? That dialog looks like an > SSH connection prompt. If you reconnect via right-mouse-click on the Files > subsystem ->"Connect..." do you get the RSE prompt? Yes, it is a SSH connection prompt. And as u mentioned if I reconnect via right-mouse-click on the Files subsystem ->"Connect...", fine, the prompt is not appearing with disabled user id field. But it appears while I reconnect via right-mouse-click on the Connection -> "Connect...". This also appears while opening a Remote Project in the Navigator view, and while initially expanding the filter in RemoteSystemsView. I believe that this needs to be corrected. And you know, during the automatic connection, while using the a remote API say, initial FileServiceSubSystem.getRemoteFileObject(), the prompt appearing is the one which I have mentioned (with disable User ID field during reconnect). This also needs to be addressed along with the fix. Thanks, Loganathans. S. (In reply to comment #3) > > But it appears while I reconnect via right-mouse-click on the Connection -> > "Connect...". This also appears while opening a Remote Project in the Navigator > view, and while initially expanding the filter in RemoteSystemsView. I believe > that this needs to be corrected. I believe the connection context menu action is "Connect" (without the "...") so it's not a prompting action when there is a saved password. I can't remember what the history was for not having that action automatically promptable. As you mentioned in the defect description, to get that prompt back, you can select the connection and right-mouse-click->"Clear Passwords". (In reply to comment #4) > (In reply to comment #3) > > > > But it appears while I reconnect via right-mouse-click on the Connection -> > > "Connect...". This also appears while opening a Remote Project in the Navigator > > view, and while initially expanding the filter in RemoteSystemsView. I believe > > that this needs to be corrected. > > I believe the connection context menu action is "Connect" (without the "...") > so it's not a prompting action when there is a saved password. I can't > remember what the history was for not having that action automatically > promptable. As you mentioned in the defect descriptiondescription, to get that prompt > back, you can select the connection and right-mouse-click->"Clear Passwords". Hi, as you mentioned, its true that I can use 'Clear Passwords' option, but my question is, why are you disabling the user ID field without knowing it is valid at least once. You know, in my application, I show only Navigator, which is involving remote project creation. If I'm in the middle of a remote project creation and if I have given the user ID wrongly once, I have to cancel/close the whole project creation action, and go to the 'RemoteSystemsView' and do the 'Clear Passwords' action, and then do the project creation again. My point is we can do the same disabling action only after a successful login in that user ID and passowrd. Till that, we can leave it editable. Thanks, Loganathan. S. I'm not seeing this with dstore connections so I suspect this is SSH-specific. Martin, could you take a look at this? |