# PAID: Create Open Source SSO plugin to auth with Wild Apricot

**URL:** https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530
**Category:** Marketplace
**Created:** [9월 21, 2015, 4:55오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530 "2015-09-21T16:55:13Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![eliot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eliot/32/116735_2.png) [@eliot](https://meta.discourse.org/u/eliot)
#### Post date: [9월 21, 2015, 4:55오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/1 "2015-09-21T16:55:13Z")

</div>

A non-profit I work with is looking for SSO integration for Wild Apricot membership management software.

Wild Apricot (WA) provides an oAuth implementation ([info on that is here](http://help.wildapricot.com/display/DOC/API+V2+authentication)), but I am not familiar enough with Ruby to successfully create a plugin. Since this may benefit others who use Wild Apricot, we would like for the code to be made available on GitHub under a BSD license.

I attempted to implement it (you can see my attempt [here](https://github.com/eliotlandrum/oauth-wildapricot-discourse)), but had no success nor enough understanding of Discourse to troubleshoot (I’m looking at the code and it looks like I left a few Slack references in there.. whoops).

The Discourse docker installation that we need this on is not currently in use, so it will be available for development use. And of course I’ll provide the Wild Apricot API keys as needed.

---

<div class="post-metadata">

### Author: ![Frans\_Thamura](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frans_thamura/32/116704_2.png) [@Frans\_Thamura](https://meta.discourse.org/u/Frans_Thamura)
#### Post date: [9월 21, 2015, 9:20오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/2 "2015-09-21T21:20:48Z")

</div>

hi there

i am working with your case also

we have an Oauth2 server (cybers.id) and we implement discourse (forum.cybers.id)

and in several case it work login using cybers.id account (register and login using FB), but in several case wont esp my fb :).

we just use sso plugin

glad if you work smiliar like us, you can share.. dont need to create sso plugins.

---

<div class="post-metadata">

### Author: ![eliot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eliot/32/116735_2.png) [@eliot](https://meta.discourse.org/u/eliot)
#### Post date: [9월 21, 2015, 9:23오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/3 "2015-09-21T21:23:37Z")

</div>

If I understand correctly, you’ve used the standard sso plugin but have somehow provided it details to login to your own oAuth server? That would be nice, it sounds simpler. 😄

---

<div class="post-metadata">

### Author: ![eliot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eliot/32/116735_2.png) [@eliot](https://meta.discourse.org/u/eliot)
#### Post date: [9월 21, 2015, 9:31오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/4 "2015-09-21T21:31:21Z")

</div>

I looked at the [Official SSO Plugin](https://meta.discourse.org/t/official-single-sign-on-for-discourse/13045), but Wild Apricot provides an API Key, a Client ID, and a Client Secret. All of that seemed to be too much for the Official SSO Plugin.

 ![](https://global.discourse-cdn.com/meta/original/3X/3/c/3c1c6b485f2ed70ddc6dc34386fa887b51decb94.jpg)

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [9월 22, 2015, 6:20오전 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/5 "2015-09-22T06:20:21Z")

</div>

Yup, that’s for OAuth, not Discourse’s custom SSO protocol.

---

<div class="post-metadata">

### Author: ![eliot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eliot/32/116735_2.png) [@eliot](https://meta.discourse.org/u/eliot)
#### Post date: [9월 22, 2015, 3:51오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/6 "2015-09-22T15:51:57Z")

</div>

Aha! Lightbulb moment! I was _not_ understanding that the SSO referred to in the settings was not actually oAuth. Thanks for that insight.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [9월 22, 2015, 4:08오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/7 "2015-09-22T16:08:44Z")

</div>

Do you want a Discourse plugin that implements another auth strategy OR a SSO implementation, that Discourse calls on access and can live elsewhere and communicate with Wild Apricot via the REST api and respond to Discourse?

---

<div class="post-metadata">

### Author: ![eliot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eliot/32/116735_2.png) [@eliot](https://meta.discourse.org/u/eliot)
#### Post date: [9월 22, 2015, 4:12오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/8 "2015-09-22T16:12:56Z")

</div>

I’m looking for Discourse to authenticate with Wild Apricot. As far as I understand it, Wild Apricot can be an oAuth provider and a plugin can be created for Discourse to use this authentication method.

---

<div class="post-metadata">

### Author: ![Frans\_Thamura](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frans_thamura/32/116704_2.png) [@Frans\_Thamura](https://meta.discourse.org/u/Frans_Thamura)
#### Post date: [9월 26, 2015, 10:26오전 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/9 "2015-09-26T10:26:36Z")

</div>

correct eliot

we create our own OAuth2, and try to make sure we implement correctly, but also need to “trust” the official SSO also stable enough, here, we blame each other between discourse team that setup it, and developer team that develop our Oauth2 server

we will implement multitenant also 🙂 so we can make more complex implementation

---

<div class="post-metadata">

### Author: ![Frans\_Thamura](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frans_thamura/32/116704_2.png) [@Frans\_Thamura](https://meta.discourse.org/u/Frans_Thamura)
#### Post date: [9월 26, 2015, 10:49오전 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/10 "2015-09-26T10:49:14Z")

</div>

any idea to test an oauth2 provider, so we believe that the oauth providers are compatible.

---

<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: [10월 20, 2015, 3:53오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/11 "2015-10-20T15:53:29Z")

</div>

I would be interested in working on this if it’s still required.

Hopefully this is slightly less of a draw-out and traumatic experience as compared to my last foray into the world of Discourse and OAuth2: [GitHub - LeoMcA/discourse-webmaker-id: Discourse plugin which adds Webmaker authentication · GitHub](https://github.com/LeoMcA/discourse-webmaker-id)

---

<div class="post-metadata">

### Author: ![eliot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eliot/32/116735_2.png) [@eliot](https://meta.discourse.org/u/eliot)
#### Post date: [10월 20, 2015, 4:12오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/12 "2015-10-20T16:12:26Z")

</div>

I haven’t been able to figure it out, would love for some help. Can PM me?

---

<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: [10월 28, 2015, 7:06오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/13 "2015-10-28T19:06:24Z")

</div>

Created and posted in the plugin directory: [Wild Apricot login plugin](https://meta.discourse.org/t/wild-apricot-login-plugin/35032)

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [11월 27, 2015, 7:06오후 UTC](https://meta.discourse.org/t/paid-create-open-source-sso-plugin-to-auth-with-wild-apricot/33530/14 "2015-11-27T19:06:31Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
