For more information, installation instructions and configuration, refer to the link above. Users are still able to create an account, but the account has to be confirmed before the user can log in. Using the extension ConfirmAccount, account creation has to be manually confirmed by website administrators. Add the following line to LocalSettings.php: For more information about this option, there is the documentation page Securing MediaWiki using Centrale KU Leuven Login.Īccount creation can be restricted to only website administrators ('sysop'). Wikis connected to the KU Leuven Association can install an extension to use the Centrale KU Leuven Login. Would it be safe by using Mediawiki on a hosting platform and secure Mediawiki by avoiding unregistered users to read and also removing the registration option Is this secure enough I find ton of options and one I came across is installing Mediawiki on a VPS with a VPN server but that is a ton of work :-( and costs more. However, the problem is not solved, as bots can automatically create an account to perform the spamming. Now only registered users can edit or create pages.To enable this, locate the LocalSettings.php file in your MediaWiki installation folder and add the following lines to it: More information about the configuration options for advanced usage can be found here: Restricting account creationÄ«ecause MediaWiki allows unregistered (anonymous) users to edit pages, this technique obviously relies on restricting page edits to logged-in users. For organizations we build state of the art solutions that really make the difference, like knowledge management systems and internal platforms promoting collaboration. $wgCaptchaTriggers = true // Trigger captcha for login hacking attempts. In 2012 Wikibase consciously chose the open source MediaWiki platform: there isnât a single platform in the world as well known and user friendly at the same time. $wgCaptchaTriggers = true // Trigger captcha for account creation. $wgCaptchaTriggers = true // Trigger captcha for page edits containing URLs. $wgCaptchaTriggers = true // Trigger captcha for page creation. $wgCaptchaTriggers = true // Trigger captcha for page edits. $wgReCaptchaSecretKey = ' your private/secret key here' $wgReCaptchaSiteKey = ' your public/site key here' Locate the LocalSettings.php file in your MediaWiki installation folder and add the following lines to it: Now you have to install and configure the ConfirmEdit extension. After registering your website, you will be presented with a public site key and a private secret key. You will need to select reCAPTCHA v2, and "I'm not a robot" Checkbox. Go to Google's ReCaptcha administrator page and register your website. The NoCaptcha ConfirmEdit extension requires MediaWiki 1.26 or higher.įirst, you have to get an API key from Google. ConfirmEdit is bundled with MediaWiki by default, but to enable NoCaptcha, you will have to get an API key from Google. Using the MediaWiki extension ConfirmEdit, NoCaptcha can be used to prevent spam on wikis. Google introduced a new generation of ReCaptcha, called NoCaptcha in 2014.
0 Comments
Leave a Reply. |