1. 09 Nov, 2015 2 commits
  2. 30 Oct, 2015 2 commits
  3. 29 Oct, 2015 1 commit
  4. 22 Oct, 2015 1 commit
  5. 13 Oct, 2015 1 commit
  6. 24 Jul, 2015 1 commit
    • Richard Midwinter's avatar
      OF-631: Implement SCRAM support · 44826566
      Richard Midwinter authored
      This implements the SCRAM-SHA1 mechanism, and includes extending the existing
      DefaultAuthProvider to store the Scram hashes for faster authentication.
      
      If user.scramHashedOnly is set to true, then only these non-reversable hashes
      are stored (and thus security is increased in exchanged for removing support
      for DIGEST-MD5 et al).
      44826566
  7. 15 Jun, 2015 1 commit
  8. 15 May, 2015 1 commit
  9. 20 Apr, 2015 1 commit
  10. 10 Apr, 2015 2 commits
  11. 09 Feb, 2015 1 commit
    • Christian Schudt's avatar
      Revert fix for OF-874 because it introduced a critical regression. · c677c99b
      Christian Schudt authored
      Appearently there can only be one ServerItemsProvider. What happened here is that disco#items requests were now routed to SessionManager, which returned an empty result, which means service discovery fails.
      
      It seems like Openfire can only host items for the whole server, not for single users, so the real fix needs some more investigation.
      c677c99b
  12. 03 Feb, 2015 1 commit
  13. 22 Dec, 2014 1 commit
  14. 30 Oct, 2014 1 commit
    • Tom Evans's avatar
      OF-460: Persist log.debug.enabled property · af77674e
      Tom Evans authored
      Fix settings for debug log so the admin UI setting is retained across
      restarts. The system property "log.debug.enabled" may also be used to
      manage this setting. If provided via openfire.xml, the property will be
      migrated into the DB during startup.
      af77674e
  15. 10 Aug, 2014 1 commit
    • Shawn Debnath's avatar
      In setup, some of the host settings are loaded from XML properties specified... · 8b2743f6
      Shawn Debnath authored
      In setup, some of the host settings are loaded from XML properties specified in openfire.xml, while others are incorrectly loaded from whats currently in JiveGlobals. Since we are in setup mode, JiveGlobals.getProperty returns null thereby ignoring any property overrides in openfire.xml specified by the user.
      
      Changelog: 
      1. Instead of just blindly setting anonymous auth to true, check if user has an override property in XML configuration, if not, default to true.
      2. Call getXMLProperty to load user configuration override values and not what is currently in JiveGlobals. During setup mode, this is always null.
      3. Instead of setting default values for auth, user, group, card, lockout, securityAudit and admin class names, check if the user has provided overrides for those properties, and if so, use those, otherwise use defaults.
      4. Expose a method to retrieve XML property names, and then in finishSetup, go through the rest of the XML properties overridden by user that were not touched by setup and individually set those. This is particularly useful when users have to specify primary and secondary * hybrid providers.
      8b2743f6
  16. 06 May, 2014 2 commits
  17. 02 May, 2014 1 commit
  18. 01 May, 2014 2 commits
  19. 05 Apr, 2014 1 commit
  20. 04 Apr, 2014 1 commit
  21. 14 Feb, 2014 1 commit
  22. 08 Feb, 2014 1 commit
  23. 06 Feb, 2014 4 commits
  24. 05 Feb, 2014 4 commits
  25. 13 Sep, 2013 1 commit
  26. 28 May, 2013 2 commits
  27. 15 May, 2013 2 commits