Home » Eclipse Projects » Subversive » Feature Request: Password saving for a session or timeout
|
| Re: Feature Request: Password saving for a session or timeout [message #41453 is a reply to message #41423] |
Tue, 10 February 2009 10:36   |
 Jörg Thönnes
Messages: 229
Registered: July 2009 |
Senior Member |
|
|
Hello Dills,
do you know that you can store your credentials separately using a keystore?
We use this to keep our passwords during upgrades of our shared installation which always creates a
new directory $HOME/.eclipse in the users home directory.
Starting eclipse as:
eclipse -keyring $HOME/.eclipse-keyring/.keyring
would use .keyring as the keystore for that instance.
In your case, you could switch between different users by switching the keystore between eclipse
restarts. If you delete the key-store, _all_ credentials are deleted, ie any passwords you had to enter.
HTH, Jörg
On 02/10/09 02:54, Dills wrote:
> I am not sure if this is the right place to make this request. I am
> guessing at least it will get some feedback and I will find out pretty
> fast if such functionality already exists.
>
> I am working in a team environment where multiple people may use the
> same laptop without changing linux username and all sharing the same
> workspace and eclipse install. When using subversive it is obviously
> preferred to save your password credentials so that you don't need to
> continuously click okay on the password box when performing a commit,
> update or even just browsing the repository (this is perhaps the worst
> because very folder you open requires another password okay). However,
> currently when you save your password you are then never asked for a
> password again. Hence, if a different user comes along and uses eclipse
> they are likely to perform all actions under your user name and
> password. The only way around this is to remove the saved password when
> you stop working or to tell them to manually change the password
> information before doing anything with svn.
>
> I think that it would be ideal if there was an option to temporarily
> save the password - say for some defined period of time (maybe 30 min, 1
> hr, 2 hr even). Then when you are using subversive you will have
> minimal times that you need to re-enter your credentials, but when
> someone else uses the same eclipse it is likely that they will be
> automatically asked to enter their credentials because your password has
> lapsed.
>
> I also think that this should be a reasonably simple change to make to
> the plugin. Obviously you would still have the option to leave no
> password at all times, or save the password forever, maintaining current
> functionality.
>
|
|
|
| Re: Feature Request: Password saving for a session or timeout [message #41519 is a reply to message #41423] |
Tue, 10 February 2009 20:25 |
Eclipse User |
|
|
|
Originally posted by: mliebelt.web.de
Nice idea, I like that. We have similar problems, but not the same
situation. I would more like to destroy the cached user ID and password
information.
So the best solution (in my opinion) could be:
1. Allow to clear the cache totally.
2. Allow to clear the cache for
- a special user
- a special server
That would allow to clean up at the end, and you may start a new when you
open the workspace. There were times when opening an old workspace after a
long period (with the change of password in between) led to the situation
that by starting the workspace, a lot of requests with wrong password were
send, so out LDAP shut the door, and I had to reset the password again.
Just my 2€cent
By
Markus
On Tue, 10 Feb 2009 02:54:52 +0100, Dills <dylan.reynolds@entecho.com.au>
wrote:
> I am not sure if this is the right place to make this request. I am
> guessing at least it will get some feedback and I will find out pretty
> fast if such functionality already exists.
>
> I am working in a team environment where multiple people may use the
> same laptop without changing linux username and all sharing the same
> workspace and eclipse install. When using subversive it is obviously
> preferred to save your password credentials so that you don't need to
> continuously click okay on the password box when performing a commit,
> update or even just browsing the repository (this is perhaps the worst
> because very folder you open requires another password okay). However,
> currently when you save your password you are then never asked for a
> password again. Hence, if a different user comes along and uses eclipse
> they are likely to perform all actions under your user name and
> password. The only way around this is to remove the saved password when
> you stop working or to tell them to manually change the password
> information before doing anything with svn.
>
> I think that it would be ideal if there was an option to temporarily
> save the password - say for some defined period of time (maybe 30 min, 1
> hr, 2 hr even). Then when you are using subversive you will have
> minimal times that you need to re-enter your credentials, but when
> someone else uses the same eclipse it is likely that they will be
> automatically asked to enter their credentials because your password has
> lapsed.
>
> I also think that this should be a reasonably simple change to make to
> the plugin. Obviously you would still have the option to leave no
> password at all times, or save the password forever, maintaining current
> functionality.
>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
|
|
|
| Re: Feature Request: Password saving for a session or timeout [message #42588 is a reply to message #41453] |
Fri, 27 February 2009 10:33 |
| Eclipse User |
|
|
|
Originally posted by: mliebelt.web.de
Hi Jörg,
I have some questions to the solution you provide:
1. Does that work independent of the SVN Connector you use? I have tested
that in the following context: Eclipse 3.3, Subversive, Connector Native
JavaHL and got as a result a file .keyring. But when I deleted that file
and restarted eclipse, updated my checkout directories and browsed the
repositories, I was never asked for my password again. So I got the
impression that the password is stored somewhere else, and the created
..keyring file is (semantically) empty.
2. When I read the eclipse help to that technique, I find the following:
-keyring keyringFilePath The location of the authorization database (or
"key ring" file) on disk.
This argument must be used in conjunction with the -password option.
Relative paths are interpreted relative to the directory that Eclipse
was started from.
-password password The password for the authorization database.
Used in conjunction with the -keyring option.
I don't understand the second phrase "the password for the authorization
database". Is that optional or do I have to set one for it? And how is
that done?
I have the impression that I don't understand yet how Subversion with the
integration in eclipse by Subversive works. And there are a lot of
possibilites and for each one, I would like to know where the password is
stored and how it could be reset then.
The following options exist:
- Install a subversion client or go without it (SVN Connector Native
JavaHL or SVNKit)
-* In case of subversion client: Is the password information stored in the
SVN client configuration (only), or is it stored in eclipse (additionally
or only)?
- Say in eclipse that the password should be stored (Repository Location,
Authorization, "Save password")
- Using the same eclipse installation with different workspaces and the
role of the configuration directory in the eclipse installation
If you have a clear understanding how all these go together, or you could
tell me a resource where to find the necessary information, I would be
really glad :-)
Thank's a lot
Markus
On Tue, 10 Feb 2009 11:36:01 +0100, Jörg Thönnes <Joerg.Thoennes@macd.com>
wrote:
> Hello Dills,
>
> do you know that you can store your credentials separately using a
> keystore?
>
> We use this to keep our passwords during upgrades of our shared
> installation which always creates a
> new directory $HOME/.eclipse in the users home directory.
>
> Starting eclipse as:
>
> eclipse -keyring $HOME/.eclipse-keyring/.keyring
>
> would use .keyring as the keystore for that instance.
>
> In your case, you could switch between different users by switching the
> keystore between eclipse
> restarts. If you delete the key-store, _all_ credentials are deleted, ie
> any passwords you had to enter.
>
> HTH, Jörg
>
> On 02/10/09 02:54, Dills wrote:
>> I am not sure if this is the right place to make this request. I am
>> guessing at least it will get some feedback and I will find out pretty
>> fast if such functionality already exists.
>>
>> I am working in a team environment where multiple people may use the
>> same laptop without changing linux username and all sharing the same
>> workspace and eclipse install. When using subversive it is obviously
>> preferred to save your password credentials so that you don't need to
>> continuously click okay on the password box when performing a commit,
>> update or even just browsing the repository (this is perhaps the worst
>> because very folder you open requires another password okay). However,
>> currently when you save your password you are then never asked for a
>> password again. Hence, if a different user comes along and uses eclipse
>> they are likely to perform all actions under your user name and
>> password. The only way around this is to remove the saved password when
>> you stop working or to tell them to manually change the password
>> information before doing anything with svn.
>>
>> I think that it would be ideal if there was an option to temporarily
>> save the password - say for some defined period of time (maybe 30 min, 1
>> hr, 2 hr even). Then when you are using subversive you will have
>> minimal times that you need to re-enter your credentials, but when
>> someone else uses the same eclipse it is likely that they will be
>> automatically asked to enter their credentials because your password has
>> lapsed.
>>
>> I also think that this should be a reasonably simple change to make to
>> the plugin. Obviously you would still have the option to leave no
>> password at all times, or save the password forever, maintaining current
>> functionality.
>>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
|
|
|
| Re: Feature Request: Password saving for a session or timeout [message #42624 is a reply to message #42588] |
Fri, 27 February 2009 11:23 |
Jörg Thönnes
Messages: 229
Registered: July 2009 |
Senior Member |
|
|
Hi Markus,
sorry for giving you only short answer, but I do not have the time to test all your scenarios below:
On 02/27/09 11:33, Markus Liebelt wrote:
> I have some questions to the solution you provide:
>
> 1. Does that work independent of the SVN Connector you use?
Yes, after changing that, Eclipse never asked for a password, neither for CVS nor for SVN or the
Myln Task Connectors I use to access Trac, JIRA, Bugzilla and Web-based repositories.
> I have
> tested that in the following context: Eclipse 3.3, Subversive, Connector
> Native JavaHL and got as a result a file .keyring. But when I deleted
> that file and restarted eclipse, updated my checkout directories and
> browsed the repositories, I was never asked for my password again. So I
> got the impression that the password is stored somewhere else, and the
> created .keyring file is (semantically) empty.
I call Eclipse e.g. using "... -keyring /export/home/joerg/.eclipse-keyring/.keyring ..."
and get a non-empty file:
-rw-rw-r-- 1 joerg joerg 8732 Feb 20 18:31 /export/home/joerg/.eclipse-keyring/.keyring
This file contains binary data. We use Linux as you see.
> 2. When I read the eclipse help to that technique, I find the following:
> -keyring keyringFilePath The location of the authorization database (or
> "key ring" file) on disk.
> This argument must be used in conjunction with the
> -password option.
> Relative paths are interpreted relative to the directory
> that Eclipse was started from.
>
> -password password The password for the authorization database.
> Used in conjunction with the -keyring option.
>
> I don't understand the second phrase "the password for the authorization
> database". Is that optional or do I have to set one for it? And how is
> that done?
No idea. I never used "-password" nor was prompted to do so.
> I have the impression that I don't understand yet how Subversion with
> the integration in eclipse by Subversive works. And there are a lot of
> possibilites and for each one, I would like to know where the password
> is stored and how it could be reset then.
Just as a test I moved my .keyring to another place and restarted Eclipse. If I now synchronize my
subversion repository (Subversive based), the dialog "Provide Authentication Information" appears.
Now I enter my user and password and it works again.
After stopping Eclipse, I have two new files:
-rw-rw-r-- 1 joerg joerg 1294 Feb 27 12:17 .keyring
-rw-rw-r-- 1 joerg joerg 8732 Feb 20 18:31 .keyring-ORIG
Now I delete the new one (less data, since just one password stored). Start Eclipse and again the
authentication dialog pops up on synchronize.
Copied back my ORIG file and after Eclipse start all is working as before without any password queries.
Please note that
1. We use Linux.
2. We use Eclipse 3.3.2 (things may have changed with 3.4)
3. We use a shared installation (the central eclipse dir is write-protected)
If Eclipse detects a write protected copy, it thinks it is a shared installation and creates a local
.eclipse directory in the users home directory.
Hope that helps!
Jörg
> The following options exist:
> - Install a subversion client or go without it (SVN Connector Native
> JavaHL or SVNKit)
> -* In case of subversion client: Is the password information stored in
> the SVN client configuration (only), or is it stored in eclipse
> (additionally or only)?
> - Say in eclipse that the password should be stored (Repository
> Location, Authorization, "Save password")
> - Using the same eclipse installation with different workspaces and the
> role of the configuration directory in the eclipse installation
>
> If you have a clear understanding how all these go together, or you
> could tell me a resource where to find the necessary information, I
> would be really glad :-)
>
> Thank's a lot
>
> Markus
>
> On Tue, 10 Feb 2009 11:36:01 +0100, Jörg Thönnes
> <Joerg.Thoennes@macd.com> wrote:
>
>> Hello Dills,
>>
>> do you know that you can store your credentials separately using a
>> keystore?
>>
>> We use this to keep our passwords during upgrades of our shared
>> installation which always creates a
>> new directory $HOME/.eclipse in the users home directory.
>>
>> Starting eclipse as:
>>
>> eclipse -keyring $HOME/.eclipse-keyring/.keyring
>>
>> would use .keyring as the keystore for that instance.
>>
>> In your case, you could switch between different users by switching
>> the keystore between eclipse
>> restarts. If you delete the key-store, _all_ credentials are deleted,
>> ie any passwords you had to enter.
>>
>> HTH, Jörg
>>
>> On 02/10/09 02:54, Dills wrote:
>>> I am not sure if this is the right place to make this request. I am
>>> guessing at least it will get some feedback and I will find out pretty
>>> fast if such functionality already exists.
>>>
>>> I am working in a team environment where multiple people may use the
>>> same laptop without changing linux username and all sharing the same
>>> workspace and eclipse install. When using subversive it is obviously
>>> preferred to save your password credentials so that you don't need to
>>> continuously click okay on the password box when performing a commit,
>>> update or even just browsing the repository (this is perhaps the worst
>>> because very folder you open requires another password okay). However,
>>> currently when you save your password you are then never asked for a
>>> password again. Hence, if a different user comes along and uses eclipse
>>> they are likely to perform all actions under your user name and
>>> password. The only way around this is to remove the saved password when
>>> you stop working or to tell them to manually change the password
>>> information before doing anything with svn.
>>>
>>> I think that it would be ideal if there was an option to temporarily
>>> save the password - say for some defined period of time (maybe 30 min, 1
>>> hr, 2 hr even). Then when you are using subversive you will have
>>> minimal times that you need to re-enter your credentials, but when
>>> someone else uses the same eclipse it is likely that they will be
>>> automatically asked to enter their credentials because your password has
>>> lapsed.
>>>
>>> I also think that this should be a reasonably simple change to make to
>>> the plugin. Obviously you would still have the option to leave no
>>> password at all times, or save the password forever, maintaining current
>>> functionality.
>>>
>
>
>
|
|
|
| Re: Feature Request: Password saving for a session or timeout [message #42749 is a reply to message #41453] |
Sat, 28 February 2009 08:24 |
| Eclipse User |
|
|
|
Originally posted by: mliebelt.web.de
Hi Jörg,
I have some questions to the solution you provide:
1. Does that work independent of the SVN Connector you use? I have tested
that in the following context: Eclipse 3.3, Subversive, Connector Native
JavaHL and got as a result a file .keyring. But when I deleted that file
and restarted eclipse, updated my checkout directories and browsed the
repositories, I was never asked for my password again. So I got the
impression that the password is stored somewhere else, and the created
..keyring file is (semantically) empty.
2. When I read the eclipse help to that technique, I find the following:
-keyring keyringFilePath The location of the authorization database (or
"key ring" file) on disk.
This argument must be used in conjunction with the -password option.
Relative paths are interpreted relative to the directory that Eclipse
was started from.
-password password The password for the authorization database.
Used in conjunction with the -keyring option.
I don't understand the second phrase "the password for the authorization
database". Is that optional or do I have to set one for it? And how is
that done?
I have the impression that I don't understand yet how Subversion with the
integration in eclipse by Subversive works. And there are a lot of
possibilites and for each one, I would like to know where the password is
stored and how it could be reset then.
The following options exist:
- Install a subversion client or go without it (SVN Connector Native
JavaHL or SVNKit)
-* In case of subversion client: Is the password information stored in the
SVN client configuration (only), or is it stored in eclipse (additionally
or only)?
- Say in eclipse that the password should be stored (Repository Location,
Authorization, "Save password")
- Using the same eclipse installation with different workspaces and the
role of the configuration directory in the eclipse installation
If you have a clear understanding how all these go together, or you could
tell me a resource where to find the necessary information, I would be
really glad
Thank's a lot
Markus
On Tue, 10 Feb 2009 11:36:01 +0100, Jörg Thönnes <Joerg.Thoennes@macd.com>
wrote:
> Hello Dills,
>
> do you know that you can store your credentials separately using a
> keystore?
>
> We use this to keep our passwords during upgrades of our shared
> installation which always creates a
> new directory $HOME/.eclipse in the users home directory.
>
> Starting eclipse as:
>
> eclipse -keyring $HOME/.eclipse-keyring/.keyring
>
> would use .keyring as the keystore for that instance.
>
> In your case, you could switch between different users by switching the
> keystore between eclipse
> restarts. If you delete the key-store, _all_ credentials are deleted, ie
> any passwords you had to enter.
>
> HTH, Jörg
>
> On 02/10/09 02:54, Dills wrote:
>> I am not sure if this is the right place to make this request. I am
>> guessing at least it will get some feedback and I will find out pretty
>> fast if such functionality already exists.
>>
>> I am working in a team environment where multiple people may use the
>> same laptop without changing linux username and all sharing the same
>> workspace and eclipse install. When using subversive it is obviously
>> preferred to save your password credentials so that you don't need to
>> continuously click okay on the password box when performing a commit,
>> update or even just browsing the repository (this is perhaps the worst
>> because very folder you open requires another password okay). However,
>> currently when you save your password you are then never asked for a
>> password again. Hence, if a different user comes along and uses eclipse
>> they are likely to perform all actions under your user name and
>> password. The only way around this is to remove the saved password when
>> you stop working or to tell them to manually change the password
>> information before doing anything with svn.
>>
>> I think that it would be ideal if there was an option to temporarily
>> save the password - say for some defined period of time (maybe 30 min, 1
>> hr, 2 hr even). Then when you are using subversive you will have
>> minimal times that you need to re-enter your credentials, but when
>> someone else uses the same eclipse it is likely that they will be
>> automatically asked to enter their credentials because your password has
>> lapsed.
>>
>> I also think that this should be a reasonably simple change to make to
>> the plugin. Obviously you would still have the option to leave no
>> password at all times, or save the password forever, maintaining current
>> functionality.
>>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
|
|
|
Goto Forum:
Current Time: Fri Apr 19 23:02:53 GMT 2024
Powered by FUDForum. Page generated in 0.02584 seconds |
] 
Search
Help
Register
Login
Home
