Subclipse / Team and single sign on

[dbarrieu]

Hi,

I try to find a way to optimize the authentification to multiple SVN repositories.
For the usage of my Eclipse RCP product, users are synchronize with more than 10 différents SVN repositories. Each of then display a specific authentification so for the first connection, or for a password update, users must put his authentification as many times as there are SVN repository.
Do you know if there actualy a way, in subclipse or Team, to optimise this ?
Maybe with the usage of the security storage configuration of Eclipse...

Regards.

[nikopp]

Hi, if you use svnserve, you can use the same authentication realm for all repositories in svnserve.conf: ### This option specifies the authentication realm of the repository. ### If two repositories have the same authentication realm, they should ### have the same password database, and vice versa. The default realm ### is repository's uuid. realm = oneForAll Because the password is locally stored per realm instead of per repo. Niko

…

On Thu, Jan 21, 2021 at 5:31 PM dbarrieu ***@***.***> wrote: Hi, I try to find a way to optimize the authentification to multiple SVN repositories. For the usage of my Eclipse RCP product, users are synchronize with more than 10 différents SVN repositories. Each of then display a specific authentification so for the first connection, or for a password update, users must put his authentification as many times as there are SVN repository. Do you know if there actualy a way, in subclipse or Mylyn, to optimise this ? Maybe with the usage of the security storage configuration of Eclipse... Regards. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#155>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABNTLTNEFTSFZTQEXKYNR3S3BJGLANCNFSM4WNE7OSA> .

[dbarrieu]

Thanks for your quick reply.

Regards.

[markphip]

Subclipse itself does not collect or cache any credentials. Instead it is all done by the SVN API implementation. Using JavaHL, as example, it caches passwords the same as the SVN command line client does and is controlled by the same settings etc. Even the dialog to provide username and password is triggered by the API. Subclipse provides the API with a callback method to collect credentials and the API decides when and if to call this method when it decides it needs to ask the user for credentials.

SVN's cache is based on the "realm". So if all of your repositories are on the same server and the authentication is all part of the same realm, the user should only be challenged for credentials one time .. provided that the user is allowed to cache their credentials. This is determined by the SVN client configuration.