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), 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), 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.
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.
I looked at the Official SSO Plugin, 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.
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?
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.
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