My favorites | Sign in
Project Home Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 414: Google Code SVN should use OAuth for authentication
122 people starred this issue and may be notified of changes. Back to list
Status:  Reviewed
Owner:  dbentley@google.com


Sign in to add a comment
 
Reported by chris.messina, Sep 7, 2007
When I attempted to check in changes to Google Code SVN, I assumed that I should use my Gmail 
account password, not realizing that a separate password is generated for this kind of activity. 
While I can appreciate the security reason for this, it wasn't expected or uniform.

A better solution might be to implement the Out Of Band OAuth protocol (once the spec is final) in 
order to make this experience more uniform and to avoid the confusion over first having to obtain a 
password and THEN go back to your flow.
May 21, 2008
#1 azmatali...@gmail.com
(No comment was entered for this change.)
Owner: dclinton
Labels: -Type-Defect Type-Enhancement
Jun 4, 2008
#2 azmatali...@gmail.com
(No comment was entered for this change.)
Labels: Milestone-2008-Q4
Jul 15, 2008
#3 kur...@gmail.com
Hello! When trying to commit changes, my TortoiseSVN fails.

MKACTIVITY of '/svn/!svn/act/12c1754c-a3b6-974b-9ce2-54e6a9e46b00':
authorization failed (http://aegonbowlinggame.googlecode.com)

I am using my username and the generated password. I also tried a regenerated one but
it keeps failing. Are users/administrators bound to IP-adresses?

Thanks for your help!
Jul 15, 2008
#4 suss...@gmail.com
kurtze, if you need help, it's probably best to mail the googlegroup or open a new
issue... not append your problem to an issue about implementing a new OAuth feature.  :-)

Try using https:// to commit, not http:// as the 'source' tab explains.  Writes can
only happen over https://

Aug 4, 2008
#5 azmatali...@gmail.com
(No comment was entered for this change.)
Owner: azmatalipasha
Oct 5, 2008
#6 provoost...@gmail.com
I would also *love* to see Oauth support for issue manipulation. I'm building a web
application on top of Google Code that needs to manipulate issues (the elegant way). 
Nov 26, 2008
#7 azmatali...@gmail.com
(No comment was entered for this change.)
Status: Reviewed
Dec 17, 2008
#8 azmatali...@gmail.com
(No comment was entered for this change.)
Labels: -Milestone-2008-Q4 Milestone-2009
Oct 28, 2009
#9 bmos...@gmail.com
You can use the following svn command to accomplish the change:

svn switch --relocate \
 http://myproject.googlecode.com/svn \
 https://myproject.googlecode.com/svn

Nov 12, 2009
#10 apa...@google.com
(No comment was entered for this change.)
Owner: apa...@google.com
Apr 4, 2010
#11 apa...@google.com
(No comment was entered for this change.)
Labels: Milestone-None
Apr 5, 2010
#12 ninge...@google.com
(No comment was entered for this change.)
Labels: -Milestone-None
Nov 17, 2010
#13 michael.c.soh
I'm not sure if an OAuth solution would be good.  I prefer the current method (e.g. randomized password string) since it's simple and doesn't require any sort of token manipulation.  Perhaps I have a bad taste in my mouth from implementing OAuth to my twitter apps but I like simplicity of having a second password.

If you impliment OAuth, provide a choice.
May 6, 2011
#14 nathaniel@google.com
 Issue 813  has been merged into this issue.
Jun 9, 2011
#15 ninge...@google.com
(No comment was entered for this change.)
Owner: dbentley@google.com
May 15, 2012
#16 techtonik@gmail.com
OAuth support would be awesome for Mercurial too https://developers.google.com/appengine/docs/python/tools/uploadinganapp#oauth

It will probably require a little cooperation with upstream.
Sign in to add a comment

Powered by Google Project Hosting