That fixed it for me! Thanks!
I am running into exactly the same problem. I had a jive account already. I can access the Jive Support Community, Jive Developers Community and Jive Sandbox just fine via the browser. But when I run jiveapps create, it can't authenticate (same error as above).
I used the #enrollment link as Arnold specified. When I filled out the form, it says my username had already been taken. When I changed the username to a unique one, it says the email address had already been taken. Clearly, the username and email address are taken because I already registered. So if I am registered, why can't jiveapps create authenticate my developers community credentials?
Ran into the same situation when they switched over auth a while back. Basically I have two separate accounts with distinct usernames and email addresses now
Sent from my Windows Phone
I just went into develops.jivesoftware.com to change my password and log in using the new password via the browser. Everything works fine. Yet, when I run jiveapps create in Git Bash, it failed to authenticate. (Authentication failure) I am at a lost.
I took Nil's suggestion and created an account with unique username AND email address. That got me further. "jiveapps create" at least authenticates correctly now but it now complains about Git Push failed. Once it fails, you can't create the app with the same name anymore. Not even after you run "jiveapps delete <name>". "jiveapps delete" simply return "Error: " with no further information. This process is starting to feel like it's held together with duct tapes.
Errors for "jiveapps create" ...
$ jiveapps create xchange2
iconv will be deprecated in the future, use String#encode instead.
c:/Ruby193/lib/ruby/gems/1.9.1/gems/systemu-2.2.0/lib/systemu.rb:29: Use RbConfi
g instead of obsolete and deprecated Config.
=== Creating new Jive App "xchange2"...
Step 1 of 4. Checking availability and creating remote repository... SUCCESS
Step 2 of 4. Generating app scaffolding...
NOTE: Gem.cache is deprecated, use Gem::source_index. It will be removed on or a
Gem.cache called from c:/Ruby193/lib/ruby/gems/1.9.1/gems/rubigen-1.5.5/lib/rubi
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on o
r after 2011-11-01.
Gem.source_index called from c:/Ruby193/lib/ruby/site_ruby/1.9.1/rubygems.rb:117
NOTE: Gem::SourceIndex#each is deprecated with no replacement. It will be remove
d on or after 2011-11-01.
Gem::SourceIndex#each called from c:/Ruby193/lib/ruby/gems/1.9.1/gems/rubigen-1.
Enter App Title or hit enter for default [xchange2]:
Enter App Description or hit enter for default [Description of xchange2]:
Step 3 of 4. Creating local Git repository and pushing to remote... FAILURE
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Git Push failed. Deleting app and cleaning up. Check SSH key and try again:
$ jiveapps keys:list
$ jiveapps keys:remove <user@machine>
$ jiveapps keys:add
$ jiveapps create xchange2
Someone else experienced the same "Git Push failed" problem (https://community.jivesoftware.com/message/1425336#1425336). The suggested solution didn't work for me but it may for those of you who are stuck at the same point I am.
I had a similar problem initially. It seemed that the going through the registration link given in the email didn't actually register me. I can't remember exactly what I did, but I think I went to the Developers page and registered from there. After that, I was able to go in with my usual username and password.
Try registering at https://developers.jivesoftware.com/register.jsp. Hopefully that will do the trick.