Kepler

This has now been fixed.

this is not fixed for me. After merging the changes from the trunk to the branch, I have to click the "login anonymously" button three times, at which point the "datos" search works, but I'm not sure that it is actually logging in. Debi, can you confirm that this works on the 2.0 branch?

The error message has gone. However,the GUI showed three times when I kept clicking the "Login Anonymously" button.

This is on kepler 2.0 branch.

I figured it out!

when you try to use the "Login Anonymously" button, the authentication service will try to look of the kepler user from the current "save repository":
RepositoryManager.getInstance().getSaveRepository();
but if you haven't checked any repository as the saveRepository, then it will be null and we can't look up the username to use.
If you do have a repository selected, you can login anonymously.

Now for the fix...

Ugh. We still have two different systems for managing our various "remote services":
-Repositories (components)
-EcogridServices (data)

We are searching for data in this case, but we reuse the same login gui when authenticating for a save to a remote repository.

Instead of associating the anonymous use with the Repository, we should associate it with the Authentication Domain (KNB, SEEK, DEV, etc....)

Refactored the anonymous login configuration to be at the Domain class rather than the Repository class.
-adds configuration to Domain objects (username/password) and removes it from Repository objects
-ecogrid services that are not already configured statically with an authDomain (i.e. KNB) will use the default anonymous user (also configured in the ecogrid configuration.xml)

Now you do not need to have a save repository configured and checked in order to do the anonymous search.

Also, when you authenticate to save a component to a repository, you can use the anonymous user as configured for that auth domain (which is in turn mapped to the save repository).

Original Bugzilla ID was 4799