Conversation

Notices

1. Embed this notice
   teknomunk (teknomunk@pl.polaris-1.work)'s status on Friday, 23-Dec-2022 02:24:58 JST teknomunk

   • Alex Gleason
   @alex
   
   I am having an issue attaching Soapbox to my own custom backend. When performing a login, I get three requests that Soapbox makes to the backend (/api/v1/apps, /oauth/token, /api/v1/accounts/verify_credentials). The last has the server providing this data:
   
   {
   "name": "Soapbox",
   "website": "https://soapbox.pub/",
   "vapid_key": "705178736"
   }
   
   But then, the login just sits there. I get no additional requests to the server and no modal error messagess and no errors on the dev console. I am pretty sure I'm not doing something correct, but I am getting no indication of what is wrong so I can correct it.
   
   I installed using a modified version of step 5 on the page https://soapbox.pub/install/, My data is installed under assets/soapbox/, and assets appear to be loading mostly correctly (I have an outstanding bug where things load slowly)
   
   Any help would be appreciated.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Friday, 23-Dec-2022 02:24:54 JST Alex Gleason

     in reply to

     @teknomunk The response from GET /api/v1/accounts/verify_credentials should return the full account object of the current user. If your custom backend is returning the json data you showed, that isn’t going to work. That seems like the response I’d expect from GET /api/v1/apps/verify_credentials

   • Embed this notice
     teknomunk (teknomunk@pl.polaris-1.work)'s status on Friday, 23-Dec-2022 02:31:25 JST teknomunk

     in reply to

     • Alex Gleason
     @alex That makes sense, because the backend only has /api/v1/apps/verify_credentials implemented.
     
     This is exactly what I needed. Thanks.
     Alex Gleason likes this.