My testing verifies that all changes to this story have been made as expected and disabled data sources are now being handles as expected. Since this story is resolved it will now be closed.

This issue was reopened because it seems that added data sources are not persisting in the "Data Sources" table within Preferences after closing an IGB session (when closing and reopening IGB).

They added sources are still visible under "Available Data" on the Main Screen, however, they do not show up in the Data Sources table within preferences after closing an IGB session.

Reassigning to Tarun so that necessary changes can be made.

My testing verifies that this story has been resolved. Disabled data sources now populate to the Data Sources list in Preferences and there is no "enabled" check mark for disabled sources. Sources can be edited, deleted, and authenticated.

Since this story is resolved it will now be closed.

It seems that the change that was made to the code was to actually close the authentication window when canceled or clicking on the "X" in the upper-right corner of the widget. I do like this change to the code but the issue explained in this story requires a different fix.

If you enter an incorrect username or password at the authentication window then you will see the pop-up saying that the Quickload server is not responding and it is being disabled for the session. The disabled data source should still populate to the list of data sources but it does not---that is the real issue of this story. The data source gets added in the background but not to the list of data sources, because trying to add the source again causes a pop-up to arise saying that the data source has already been added. You can't remove this data source though or edit it because it is not selectable since it is not on the data sources list.

Therefore, if a user accidentally enters the wrong username or password then they won't be able to go back and correct this unless they clear IGB preferences which causes IGB to close.

But to clarify, the story doesn't actually relate to the authentication window at all; using the authentication window is just an easy way to force a data source to become "disabled". The real problem lies in the fact that an added data source does not get populated to the data sources list if it is disabled, even though it should be (just with no checkmark in the "enabled" checkbox).

Before continuing with any further resolution you should discuss the story with David to see if this story is even worth working on because the whole data sources list may be refactored soon anyways.

To reproduce the "Disabling for the Session" popup, it may be helpful to add a data source that requires authentication and then just "Cancel" the Authentication window. (this usually produces the pop-up).

An example of a data source that requires authentication can be found by asking Mason.