# Wild Apricot login plugin

**URL:** https://meta.discourse.org/t/wild-apricot-login-plugin/35032
**Category:** Plugin
**Created:** [28 oktober 2015 om 19:05 UTC](https://meta.discourse.org/t/wild-apricot-login-plugin/35032 "2015-10-28T19:05:20Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![LeoMcA](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/leomca/32/87233_2.png) [@LeoMcA](https://meta.discourse.org/u/LeoMcA)
#### Post date: [28 oktober 2015 om 19:05 UTC](https://meta.discourse.org/t/wild-apricot-login-plugin/35032/1 "2015-10-28T19:05:20Z")

</div>

[https://github.com/LeoMcA/discourse-wildapricot-auth](https://github.com/LeoMcA/discourse-wildapricot-auth)

[Creation generously sponsored by](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530) @eliot

## Installation

Follow the Discourse [Install a Plugin](https://meta.discourse.org/t/install-a-plugin/19157) guide, using `git clone https://github.com/LeoMcA/discourse-wildapricot-auth.git` as the command.

Ensure you set the `wildapricot_server`, `wildapricot_client_id`, `wildapricot_client_secret` and `wildapricot_account_id` settings either in the admin interface or through the `DISCOURSE_WILDAPRICOT_SERVER`, `DISCOURSE_WILDAPRICOT_CLIENT_ID`, `DISCOURSE_WILDAPRICOT_CLIENT_SECRET` and `DISCOURSE_WILDAPRICOT_ACCOUNT_ID` environment variables.

## Licence

MIT

---

<div class="post-metadata">

### Author: ![bfc](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bfc/32/121052_2.png) [@bfc](https://meta.discourse.org/u/bfc)
#### Post date: [27 april 2017 om 12:53 UTC](https://meta.discourse.org/t/wild-apricot-login-plugin/35032/2 "2017-04-27T12:53:58Z")

</div>

Hi @LeoMcA

First – thanks very much for this plugin. It’s working very well for us.

I’ve run into one issue though: if our members change their email address in their account on Wild Apricot, that change does not propagate to their account on Discourse. This has undesirable effects, because we have email replies enabled. An example scenario:

1. Fred has a membership account on Wild Apricot, with email “[fred@fred.com](mailto:fred@fred.com)”
2. Fred signs up for our Discourse forum, which grabs “[fred@fred.com](mailto:fred@fred.com)” from Wild Apricot. He chooses the username “Fred”
3. Fred changes his email on Wild Apricot to “[fred@gmail.com](mailto:fred@gmail.com)” but his email on Discourse is still [fred@fred.com](mailto:fred@fred.com)
4. Fred receives an email reply to one of his posts, and replies to it using [fred@fred.com](mailto:fred@fred.com). This now appears on discourse, but using the username “Fred1” – “Fred1” is greyed out in the admin list of users, and the email is listed as “unverified”

Can this plugin be configured to keep the user email addresses synced with Wild Apricot?

Thanks for your help.

---

<div class="post-metadata">

### Author: ![bfc](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bfc/32/121052_2.png) [@bfc](https://meta.discourse.org/u/bfc)
#### Post date: [27 april 2017 om 13:39 UTC](https://meta.discourse.org/t/wild-apricot-login-plugin/35032/3 "2017-04-27T13:39:57Z")

</div>

Sorry, I just looked at this again, let me make a correction, because I’m not sure I am seeing consistent behavior.

I created a test account to test the scenario I described above, which gave the results above.

Another user ran into this problem, and “Fred” did get the updated email address “[fred@gmail.com](mailto:fred@gmail.com)”. However, when he replied to an email reply using [fred@fred.com](mailto:fred@fred.com), a second account (Fred1) was created with the [fred.com](http://fred.com) address.