Moonshot

Last updated:

4 months 2 weeks ago

Group Manager

Project Moonshot is a Janet-led initiative, in partnership with the GÉANT project and others, to develop a single unifying technology for extending the benefits of federated identity to a broad range of non-Web services, including Cloud infrastructures, High Performance Computing & Grid infrastructures and other commonly deployed services including mail, file store, remote access and instant messaging. The goal of the technology is to enable the management of access to a broad range of services and applications, using a single technology and infrastructure. This is expected to significantly improve the delivery of these services by providing users with a common single sign-on, for both internal and external services. Service providers will be able to more easily offer their services to users from other organisations using a single common authentication mechanism. This will enhance the user’s experience, and reduce costs for those organisations supporting users, and delivering services to them. This group is for community of Moonshot users, whether you're new to the technology, you're currently evaluating and getting to grips with it, or you've deployed it. For the list of guidance available about Moonshot within this group, see the Start Here wiki page. Jisc Assent, the production service underpinned by the Moonshot technology, went live on 25th March 2015. For information on, or to join the Jisc Assent service, please visit http://www.jisc.ac.uk/assent

Group administrators:

Recent members:

Source Access

Rhys Smith

9 October 2013 at 1:33pm

Table of contents

Introduction
Source Access
Obtaining Commit Access

Introduction

Most parts of Moonshot are open source, released under the BSD license. This page gives details on how to get source access.

Source Access

Moonshot uses launchpad to manage the software project at https://code.launchpad.net/moonshot, and its master git repository is available at git://git.project-moonshot.org/mech_eap.git.

Obtaining Commit Access

In general, commit access is available to anyone making significant contributions to the project.

To obtain commit access, please send an ssh public key to hartmans@painless-security.com. Preferably do this securely. Ways of doing this include:

Sending an https pointer to the public key for a URI that you obviously control and that lives on a server with a validatable certification path.
Sending the key in a GPG-signed message with a key in the strong set.
Sending the key in a S/MIME signed message with a S/MIME certificate that can be validated to a public root

If you don't have a mechanism for sending such a secure key, send one anyway; we will work something out.