Table of Contents generated with DocToc

• Introduction
• Installation
  • Configuration
  • Externalized Configuration
• Usage - ReCaptcha
  • Edit the Configuration
    • Proxy Server Configuration
  • Use the Tag Library
    • <recaptcha:ifEnabled>
    • <recaptcha:ifDisabled>
    • <recaptcha:recaptcha>
    • <recaptcha:script>
    • <recaptcha:recaptchaExplicit>
    • <recaptcha:renderParameters>
    • <recaptcha:ifFailed>
  • Verify the Captcha
  • Examples
    • Tag Usage for Automatic Rendering
    • Tag Usage for Explicit Rendering
    • Tag Usage with Separate Script
    • Customizing the Language
    • Verify User Input
    • Testing
• Usage - Mailhide
  • Edit the Configuration
  • Use the Tag Library
  • Examples
    • mailhide tag
    • mailhideURL tag
• Contributing
  • Before Submission
  • When Submitting
• Suggestions or Comments

Introduction

This plugin is designed to make using the ReCaptcha and Mailhide services within Grails 3 easy. In order to use this plugin, you must have a ReCaptcha account, available from http://www.google.com/recaptcha.

Installation

Add the following to your build.gradle

compile "org.grails.plugins:recaptcha:3.0.0"

Configuration

Add the following to your application's application.yml file:

recaptcha:
    publicKey: "your public key"
    privateKey: "your private key"
    includeScript: true
    includeNoScript: true

These configurations can also be placed at environment-specific locations in the configuration:

environments:
    development:
        recaptcha:
            enabled: false
    production:
        recaptcha:
            enabled: true

Externalized Configuration

See the Grails docs for examples of using externalized configuration files. The ReCaptcha config can be externalized as the .groovy file (easiest), or it can be converted into a Java .properties file.

Usage - ReCaptcha

The plugin is simple to use. In order to use it, there are four basic steps:

Edit the Configuration

The configuration values are pretty self-explanatory, and match with values used by the ReCaptcha service. You must enter your public and private ReCaptcha keys, or errors will be thrown when trying to display a captcha.

Proxy Server Configuration

If your server needs to connect through a proxy to the ReCaptcha service, add the following to the ReCapctcha configuration. These properties are not created by the quickstart script. They must be added manually.

recaptcha:
    proxy:
        server: ""   // IP or hostname of proxy server
        port: ""     // Proxy server port, defaults to 80
        username: "" // Optional username if proxy requires authentication
        password: "" // Optional password if proxy requires authentication

Only the server property is required. The port will default to 80 if not specified. The username and password properties need to be specified only when the proxy requires authentication.

Like other configurations, this can be placed at the top-level recaptcha entry, or it can be specified on a per-environment basis.

Use the Tag Library

<recaptcha:ifEnabled>

This tag is a simple utility that will render its contents if the captcha is enabled in the configuration.

<recaptcha:ifDisabled>

This tag is a simple utility that will render its contents if the captcha is disabled in the configuration.

<recaptcha:recaptcha>

This tag is responsible for generating the correct HTML output to display the captcha. It supports the following attributes:

• theme - Can be one of dark or light. Defaults to light.
• lang - Can be any one of the supported ReCaptcha language codes. See the list of supported language codes.
• tabindex - Optional tabindex of the widget.
• type - Type of captcha to display if the checkbox is not sufficient. Can be one of image or audio. Defaults to image.
• successCallback - Optional function to be called when the user submits a successful response.
• expiredCallback - Optional function to be called when the successful response has expired.
• includeScript - If includeScript is set to false at either the global or tag level, the <script> tag required by ReCaptcha will not be included in the generated HTML. The <recaptcha:script> tag is also required in this scenario.

See the ReCaptcha Client Guide for more details.

<recaptcha:script>

This tag will render the required <script> tag. Combine this with the global or tag-level includeScript=false setting to allow putting the <script> tag elsewhere in your markup. This tag also supports the "lang" attribute. This does not work in the <head> section of the page

<recaptcha:recaptchaExplicit>

This tag is responsible for generating the correct HTML output to support explicit display and usage of the captcha. It supports the following attributes:

• lang - Can be any one of the supported ReCaptcha language codes. See the list of supported language codes.
• loadCallback - The JavaScript function to be called when all dependencies have loaded. This function is usually responsible for rendering the captcha.

For more information about explicit mode captchas, see the ReCaptcha documentation.

<recaptcha:renderParameters>

This utility tag will generate the JSON string used as a parameter to the grecaptcha.render() function. It supports the following attributes:

• theme - Can be one of dark or light. Defaults to light.
• tabindex - Optional tabindex of the widget.
• type - Type of captcha to display if the checkbox is not sufficient. Can be one of image or audio. Defaults to image.
• successCallback - Optional function to be called when the user submits a successful response.
• expiredCallback - Optional function to be called when the successful response has expired.

See the ReCaptcha Client Guide for more details.

<recaptcha:ifFailed>

This tag will render its contents if the previous validation failed.

Verify the Captcha

In your controller, call recaptchaService.verifyAnswer(session, request.getRemoteAddr(), params) to verify the answer provided by the user. This method will return true or false. Also note that verifyAnswer will return true if the plugin has been disabled in the configuration - this means you won't have to change your controller.

Examples

Here's a simple example pulled from an account creation application.

Tag Usage for Automatic Rendering

This is the most common usage scenario.

In our GSP, we add the code to show the captcha:

<recaptcha:ifEnabled>
    <recaptcha:recaptcha theme="dark"/>
</recaptcha:ifEnabled>

In this example, we're using ReCaptcha's dark theme. Leaving out the theme attribute will default the captcha to the light theme.

Tag Usage for Explicit Rendering

In our GSP, we add code like the following:

<script type="text/javascript">
  var onloadCallback = function() {
    grecaptcha.render('html_element', <recaptcha:renderParameters theme="dark" type="audio" tabindex="2"/>);
  };
</script>
<g:form action="myAction" method="post">
  <recaptcha:ifEnabled>
    <recaptcha:recaptchaExplicit loadCallback="onloadCallback"/>
    <div id="html_element"></div>
  </recaptcha:ifEnabled>
  <br/>
  <g:submitButton name="submit"/>
</g:form>

In this example, we're using ReCaptcha's dark theme, with an audio captcha and a tabindex of 2.

For more information about explicit mode captchas, see the ReCaptcha documentation.

Tag Usage with Separate Script

Set the includeScript value to false either at the tag level (below), or in the global ReCaptcha settings.

<body>
  <g:form action="validateNormal" method="post" >
    <recaptcha:ifEnabled>
      <recaptcha:recaptcha includeScript="false"/>
    </recaptcha:ifEnabled>
    <br/>
    <g:submitButton name="submit"/>
  </g:form>
  <recaptcha:script/>
</body>

This will cause the <script src="https://www.google.com/recaptcha/api.js?" async="" defer=""></script> tag to be output separately at the bottom of the document instead of just before the <div> containing the captcha.

Customizing the Language

If you want to change the language your captcha uses, set lang = "someLang" in the <recaptcha:recaptcha> or <recaptcha:recaptchaExplcit> tags.

See ReCaptcha Language Codes for available languages.

Verify User Input

Here's an abbreviated controller class that verifies the captcha value when a new user is saved:

import com.megatome.grails.RecaptchaService
class UserController {
    RecaptchaService recaptchaService

    def save = {
        def user = new User(params)
        ...other validation...
        def recaptchaOK = true
        if (!recaptchaService.verifyAnswer(session, request.getRemoteAddr(), params)) {
            recaptchaOK = false
        }
        if(!user.hasErrors() && recaptchaOK && user.save()) {
            recaptchaService.cleanUp(session)
            ...other account creation acivities...
            render(view:'showConfirmation',model:[user:user])
        }
        else {
            render(view:'create',model:[user:user])
        }
    }
}

Testing

You can look at the test cases in the plugin itself, or you can implement something similar to:

private void buildAndCheckAnswer(def postText, def expectedValid, def expectedErrorMessage) {
    def mocker = new MockFor(Post.class)
    mocker.demand.getQueryString(3..3) { new QueryString() }
    mocker.demand.getResponse { new JsonSlurper().parseText(postText) }
    mocker.use {
        def response = r.checkAnswer("123.123.123.123", "response")

        assertTrue response == expectedValid
    }
}

The postText parameter represents the response from the ReCaptcha server. Here are examples of simulating success and failure results:

public void testCheckAnswerSuccess() {
    def answer = """{ "success": true }"""
    buildAndCheckAnswer(answer, true)
}

public void testCheckAnswerFail() {
    def answer = """{ "success": false }"""
    buildAndCheckAnswer(answer, false)
}

Usage - Mailhide

Edit the Configuration

Add the following to your application's application.yml file:

mailhide:
    publicKey: "mailhide public key"
    privateKey: "mailhide private key"

Use the Tag Library

The plugin includes two Mailhide tags: <recaptcha:mailhide> and <recaptcha:mailhideURL>.

• The <recaptcha:mailhide> tag creates a Mailhide URL that opens in a new, pop-up window per the Mailhide specification. It supports one attribute: "emailAddress", to specify the email to be hidden. The link will be created around whatever content is in the body of the tag.
• The <recaptcha:mailhideURL> tag creates a "raw" URL that can be used however desired. This is useful if the pop-up behavior of the other tag is not wanted. It supports two attributes: "emailAddress" and "var". The "emailAddress" attribute specifies the email to be hidden, while the "var" attribute specifies the name of the variable that the created URL should be available under in the page. The URL variable is only available in the context of the tag body.

Examples

mailhide tag

<recaptcha:mailhide emailAddress="x@example.com">Some text to wrap in a link</recaptcha:mailhide>

will create:

<a href="http://www.google.com/recaptcha/mailhide/d?k=...publicKey...&c=..encryptedEmail..."
     onclick="window.open('http://www.google.com/recaptcha/mailhide/d?k=...publicKey...&c=...encryptedEmail...', '', 
     'toolbar=0,scrollbars=0,location=0,statusbar=0,menubar=0,resizable=0,width=500,height=300'); return false;" 
     title="Reveal this e-mail address">Some text to wrap in a link</a>

mailhideURL tag

<recaptcha:mailhideURL emailAddress="x@example.com" var="mu">
    Created Mailhide URL: ${mu}
</recaptcha:mailhideURL>

will create:

Created Mailhide URL: http://www.google.com/recaptcha/mailhide/d?k=...publicKey...&c=...encryptedEmail...

Contributing

Contributions are welcome, but there a couple of guidelines that will make everything easier.

Before Submission

• Make sure that all unit tests before submitting a pull request.

When Submitting

• Be sure to submit pull requests against the current "target branch". This will ensure that changes are applied to the correct version.
• Make sure that commits have descriptive text that clearly explains the change. (See http://chris.beams.io/posts/git-commit/ for tips on writing good commit messages.)
• Reference appropriate issues or pull requests if needed. (Use refs XXX instead of fixes XXX or closes XXX)

Suggestions or Comments

Feel free to submit questions through GitHub or to StackOverflow.

Alternatively you can contact me directly - cjohnston at megatome dot com