I’m not familiar enough with Ghost to properly advise here, but, I can say this:
- our recommended approach is to use existing standards for authentication, because, well, security is key when it comes to accounts and logins. For example, GitHub - discourse/discourse-oauth2-basic: A basic OAuth2 plugin for use with Discourse or Discourse OpenID Connect, available on the business tier of our official hosting. Or SAML, for the enterprise-inclined.
- Given these plugins above, I don’t think a specific Ghost auth plugin for Discourse is warranted. Ghost would need to support one of these standards, and once they do, you don’t need a specific Ghost plugin. We’re open to collaborating here, but my gut feeling is that Ghost would need to do the heavy lifting of adding some IDP features to their offering.
- The JWT route is also an option, as @RGJ noted, the plugin exists and it can likely be configured to do the same thing as the D-o-G intermediary. It’s a bit of an outdated standard though and we generally recommend OAuth, OpenID, SAML or DiscourseConnect.