Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

fisheye managed git repositories

In the world of gitorious/github, when a new repository is created, I'd like to upload my public key so from my desktop, I can work with ssh keypair authentication - how can I do this?

It seems like behind the scenes, fisheye will generate a keypair - but it's not clear what that's for - communication between fisheye and the new repository?

3 answers

I guess another way to think about this is with a fisheye managed git repository, fisheye is playing middle man.

So after fisheye creates a repository and has ssh auth set up, how would a developer connect to that repository - where does _that_ public key go?

0 votes
seb Atlassian Team Oct 07, 2011

Hi Edward,

When connecting to an external Git repository, FishEye can be configured to use a key pair for ssh authentication. In this way, FishEye becomes a consumer of the origin repository, much like your desktop would when cloning from gitorious or github.

However, when you configure FishEye to host and manage a Git repository, there is currently no support for using ssh keys for authentication when cloning from FishEye; user/pass is currently the only option. The authentication section is actually not used and will be removed when creating managed repositories.

We hope to provide key based authentication for managed repositories soon.

Regards,

Seb

Hi Edward,

As Seb said, we don't support key based authentication for managed repositories just yet. However there is an issue open at https://jira.atlassian.com/browse/FE-3771 - if you'd like to see this feature implemented, please add your comments or vote there!

If entering your password each time you perform a push or pull is getting old, you can set up permanent credentials for using basic authentication to connect to your FishEye server via a .netrc file, as described in this knowledge base article.

cheers,

Tim

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

78 views 2 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you