2025-10-10 10:37 UTC
@ShadowRZ@miruku.cafe Looks like matrix-authentication-service just proxies varying other APIs as OIDC, but pleroma API is already compatible and regardless - it shouldn't be noticeable for clients correctly implementing https://spec.matrix.org/latest/client-server-api/#sso-client-loginauthentication
Also issue is overly specific, "pleroma" is just a name of OIDC app in case of eientei.
Replies (2)
-
@iamtakingiteasy@eientei.org 2025-10-10 10:50
@ShadowRZ@miruku.cafe Hm, from further docs it seem to actually take over the authentication state management and rely on internal endpoints to expose state changes to the HS. Doesn't seem to be worth it, considering only some phone client is affected.
-
@ShadowRZ@miruku.cafe 2025-10-10 11:21
@iamtakingiteasy@eientei.org To be fair, actually what Element X Android wants to talk to is the Matrix Authentication Service, it explictly doesn't support the SSO method you linked. It links like this: Element X Matrix Authentication Service Synapse Upstream IdP Additionally The eventural plan is to inline MAS to be a part of Synapse (currently it's deployed alongside Synapse)