1. 22 Oct, 2013 5 commits
  2. 21 Oct, 2013 3 commits
  3. 18 Oct, 2013 3 commits
  4. 17 Oct, 2013 1 commit
  5. 16 Oct, 2013 1 commit
  6. 15 Oct, 2013 3 commits
  7. 12 Oct, 2013 1 commit
    • Christos Stavrakakis's avatar
      cyclades: Fix check for backend disk_templates · 535c9b6b
      Christos Stavrakakis authored
      Fix the way that is checked that the disk template of the flavor is
      included in the available disk templates of the backend. Using
      'contains' is wrong because you may searching for 'file' disk template,
      will there is enabled the 'sharedfile' disk template.
      535c9b6b
  8. 11 Oct, 2013 1 commit
  9. 10 Oct, 2013 1 commit
    • Ilias Tsitsimpis's avatar
      snf-ci: Bulid pithos-web-client package · cc40aa60
      Ilias Tsitsimpis authored
      Synnefo depends on pithos-web-client. Up until now
      we were downloading this package from apt.dev.grnet.gr.
      But when we make a change in Synnefo that also affects
      pithos-web-client, we have to upload a new version of
      pithos-web-client.
      
      This patch instructs snf-ci to clone and build
      the latest pithos-web-client.
      cc40aa60
  10. 09 Oct, 2013 10 commits
  11. 08 Oct, 2013 9 commits
  12. 07 Oct, 2013 2 commits
    • Kostas Papadimitriou's avatar
      astakos: Shibboleth EPPN migration functionality · 3a6c7968
      Kostas Papadimitriou authored
      Prior to this commit astakos used the mod_shib2 EPPN header value as the
      unique identifier for associating shibboleth idp users to astakos user entries.
      
      This commit alters this behaviour and from now on astakos resloves unique
      identifier from the REMOTE_USER header. REMOTE_USER is a header mod_shib2 sets
      containing a value of the available shibboleth IdP metadata. The metadata
      key (persistent-id or eppn in most common scenarios) used can be configured
      from within shibboleth2.xml config file.
      
      <ApplicationDefaults id="default" .... .... REMOTE_USER="persistent-id"...>
      
      An additional setting ``ASTAKOS_SHIBBOLETH_MIGRATE_EPPN`` is added in order
      to facilitate migration of existing EPPN entries to persistent-id/targeted-id
      (or whichever metadata the REMOTE_USER maps to). When set to ``True``, after
      each shibboleth login astakos will try to migrate the existing EPPN entry
      by following the below mentioned steps:
      
      * If no REMOTE_USER header exists or is empty, redirect to an error view.
        Otherwise continue to the next step.
      * Resolve EPPN header and check if an account is currently associated with this
        EPPN.
      * If user exists, retrieve user's shibboleth entry (AstakosUserAuthProvider
        instance) and replace stored identifier (EPPN) with the identifier contained
        in REMOTE_USER header.
      * Continue to login or signup process using REMOTE_USER value as the unique
        user identifier that associates astakos user to the shibboleth account.
      3a6c7968
    • Kostas Papadimitriou's avatar