1. 15 May, 2016 1 commit
  2. 28 Apr, 2016 1 commit
    • Stanislav Tsymbalov's avatar
      auth/imap: Autocreating users; email domain filter · 2f9b6ca5
      Stanislav Tsymbalov authored and Aaron Wells's avatar Aaron Wells committed
      Bug 1523644. This change adds an "autocreate users"
      option to auth/imap, and it allows you to add a domain
      name filter to check that the user's email address is
      @ a particular domain.
      
      Taken together, these changes make it possible to use
      auth/imap with Google Apps for Business, and other
      similar services.
      
      behatnotneeded: Requires an IMAP server to test
      
      Change-Id: Ic1892e4df652e3997d21897cc03bfb9cf1e075cf
      2f9b6ca5
  3. 23 Jun, 2015 1 commit
  4. 03 Dec, 2014 1 commit
  5. 04 Jun, 2014 1 commit
  6. 14 Oct, 2013 1 commit
  7. 17 Feb, 2012 1 commit
    • Richard Mansfield's avatar
      Fix method names in auth plugin and instance configuration (bug #933937) · 11bcc0d0
      Richard Mansfield authored
      
      
      The validation/submission methods called during auth *plugin*
      configuration and auth *instance* configuration have the same names,
      but in each of these cases, the methods deal with completely different
      data, and are passed arguments in a different order.
      
      This is a problem for the saml plugin, which needs to detect where
      it's being called from, and reverse the order of the arguments if
      necessary.
      
      To fix this, the new methods validate_instance_config_options and
      save_instance_config_options are called during instance configuration,
      and the names 'validate_config_options' and 'save_config_options' are
      left for global plugin configuration, as these are the names used for
      all other plugin types.
      
      The old names are still usable in case any third party auth plugins
      are relying on them, but they'll produce a warning when called during
      instance configuration.
      
      Change-Id: I996ed7a2cdbe0e50dcb0c88560d10a2044b4e21c
      Signed-off-by: default avatarRichard Mansfield <richard.mansfield@catalyst.net.nz>
      11bcc0d0
  8. 13 May, 2011 1 commit
  9. 20 Jul, 2010 1 commit
  10. 15 Sep, 2009 1 commit
  11. 16 Feb, 2008 2 commits
  12. 15 Feb, 2008 1 commit
    • Nigel McNie's avatar
      Improvements to authentication plugins: · c78bac3b
      Nigel McNie authored
       * Give authentication plugins titles and descriptions, which are used by the authlist pieform element so people see an easier name
       * Add a new API method to the PluginAuth class, is_usable(). This can be used by auth plugins to check that required extensions are available. The authlist element will tell the user what they need to do to enable a plugin.
      c78bac3b
  13. 25 Jan, 2008 1 commit
    • Nigel McNie's avatar
      Lets authentication plugins trigger the creation of users if the plugin can authenticate them. · f782dbf9
      Nigel McNie authored
      If an authentication plugin thinks that a user should be able to log in, and furthermore thinks that it is able/allowed to automatically create user accounts, then it is now able to do just that. The authentication API now has a new method - can_auto_create_users() - to define whether each authentication instance feels it can/should be able to do this.
      
      If the instance thinks it can, it needs to export some information through the get_user_info method in order to populate the user account. Although this may change shortly to be optional, with the users instead being forced to enter any information that is required that they haven't otherwise filled out.
      f782dbf9
  14. 04 Dec, 2007 1 commit
  15. 15 Jul, 2007 1 commit
  16. 30 Jun, 2007 1 commit
  17. 22 Jun, 2007 1 commit
  18. 30 May, 2007 1 commit
  19. 22 May, 2007 1 commit
  20. 10 May, 2007 1 commit