Acionando a criação de conta/login em serviço externo quando um usuário faz login no discourse

[renato (Renato Atilio)]

My answer assumes you are using Discourse as your identity provider (with its login/signup UIs), and wants to keep it that way.

@Chris_Dawson

If connect is just an additional layer on top of the existing discourse user auth management, then that seems workable.

On the Discourse side, enabling it is as simple as

@Discourse

enable setting enable discourse connect provider and add a secret string to discourse connect provider secrets (used to hash SSO payloads).

However, you mentioned you’re building a plugin.

@Chris_Dawson

My first attempt was to have the JS plugin make a call to a path on the server and include discourse auth cookies. Then, for that path, let nginx proxy it to a service (“login proxy”) which can decode the auth cookies and determine who the user is. With verified user information, the login proxy can then make a special call to pocketbase and get back a pocketbase auth cookie, and then send back that pocketbase auth cookie which the client side JS can use to make subsequent requests directly to pocketbase.

If you build “a path on the server” in a new controller action in a Discourse plugin, you can get the user from the session, call 3rd parties and return the JWT to your client.