Pleroma Web FrontEnd Login failed if logged to portal

What app is this about, and its version: Pleroma 2.8.0~ynh2
What YunoHost version are you running: 12.1.29
What type of hardware are you using: Raspberry Pi 3, 4+

Describe your issue

Login with user password on the portal https://domain or https://domain/web fails.
To get it working persistently i had to disable the ssowat configuration on the dedicated domain.
This works with my users in ldap.

I searched for issues but related one Can't login into any Pleroma account · Issue #216 · YunoHost-Apps/pleroma_ynh · GitHub was marked as closed with a workaround. The workaround : not to be connected to portal. This workaround is working, but unconvenient.

This Application is the only application on the dedicated domain.

  • This Application is set as sso false in its manifest, i would think this means ssowat won’t do any action.
  • Documentation of Application indicates a /web for portal, it works without…

My ssowat workaround works, but i dislike having notifiaction about locally modified files, and i wonder too how others installs get it working.

Note : It works well from my mobile Husky application.

I use firefox

Share relevant logs or error messages

client post this

POST apps/

a json reply comes with client_secret and client_id.

web app does
POST token/

------geckoformboundary1860ab77e93a9c0aadee4be4ee725840
Content-Disposition: form-data; name="client_id"

undefined
------geckoformboundary1860ab77e93a9c0aadee4be4ee725840
Content-Disposition: form-data; name="client_secret"

undefined
------geckoformboundary1860ab77e93a9c0aadee4be4ee725840
Content-Disposition: form-data; name="grant_type"

password
------geckoformboundary1860ab77e93a9c0aadee4be4ee725840
Content-Disposition: form-data; name="username"

artlog
------geckoformboundary1860ab77e93a9c0aadee4be4ee725840
Content-Disposition: form-data; name="password"

<REDACTED>
------geckoformboundary1860ab77e93a9c0aadee4be4ee725840--

server replies with a json error 400

When working (no current login or no ssowat) the token/ request client_id and client_secret is filled and server replies with a usable token.

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