1 This page lists applications that have been successfully tested with moonshot.
13 * Demonstrates minimal SASL functionality and allows exploration of SASL mechanisms.
25 * Demonstrates GSS-API mechanisms functioning.
26 * Displays all attributes (from SAML, Shibboleth) received
27 * See [[vmdk]] for instructions on how to run
36 * Requires enabling cyrus-sasl support in the build
41 * Jabber server. Provides authentication from moonshot.
46 * Adium (unmodified) - successfully connected to a moonshot jabberd server
54 * Unmodified openLDAP, but has to be compiled with SASL specific build options; most Linux distributions do this by default
58 * * User can authenticate to openLDAP with their federated id, where their DN is mapped from their SASL id (mapping configured in slapd.conf)
62 * ldapwhoami - succesfully bound to openLDAP server with mapped DN returned.
70 * See http://www.project-moonshot.org/gitweb/openssh.git look at the master and debian branches.
71 * No client modifications required.
72 * See the vm-integration or tlv-mic branches for moonshot code that works with this. The requirement is that mutual_authentication needs to be provided in the established context
73 * gss_userok is required from the krb5 library
74 * The [[VM images|vmdk]] have these changes
79 * Provides RFC 4462 authentication and key exchange based on moonshot. In other words you can log in with ssh using Moonshot credentials
80 * If the mechanism returns the local-login-user attribute (typically mapped using Shibboleth from a SAML attribute or RADIUS attribute), then that attribute controls what local accounts are acceptable
81 * In other words federated authentication and authorization