Skip to content

Conversation

@hughns
Copy link
Member

@hughns hughns commented May 24, 2022

Rendered

  • Spec is feature complete
  • Reviewed for consistency with MSC3861
  • Implementations believed to be complete enough
  • Update since MSC3861 was accepted
  • Reconcile with MSC4191

Dependencies:

Servers

Clients


SCT Stuff:

FCP tickyboxes

MSC checklist

@hughns hughns changed the title Add an optional query parameter to SSO redirect MSC3824: Add an optional query parameter to SSO redirect May 24, 2022
@hughns hughns changed the title MSC3824: Add an optional query parameter to SSO redirect MSC3824: Add optional action= query parameter to SSO redirect May 24, 2022
@hughns hughns changed the title MSC3824: Add optional action= query parameter to SSO redirect MSC3824: Login/register indication on SSO redirect May 24, 2022
@uhoreg uhoreg added proposal A matrix spec change proposal client-server Client-Server API needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. kind:maintenance MSC which clarifies/updates existing spec labels May 24, 2022
@hughns

This comment was marked as duplicate.

@turt2live
Copy link
Member

(implementation nor the MSC have been sufficiently reviewed to remove the label - when someone on the SCT is comfortable with where things are at, they'll remove the label. Personally, I haven't gotten as far as deciding if I'm comfortable with it 😅)

@sandhose
Copy link
Member

sandhose commented May 25, 2022

I think an important part of this would also be to be able to advertise what actions are available with each login method, e.g.

{
  "flows": [{
    "type": "m.login.password",
    "actions": ["login"],
  }, {
    "type": "m.login.sso",
    "actions": ["login", "register"]
  }]
}

This would allow clients to properly display what's really available for each login method

hughns and others added 2 commits May 25, 2022 11:13
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
@hughns hughns changed the title MSC3824: Login/register indication on SSO redirect MSC3824: Ability to distinguish between login and registration May 30, 2022
@hughns
Copy link
Member Author

hughns commented May 31, 2022

I've had an initial go at Synapse support in matrix-org/synapse#12924.

Matrix Authentication Service support within it's compatibility layer is in matrix-org/matrix-authentication-service#221

@hughns hughns changed the title MSC3824: Ability to distinguish between login and registration MSC3824: OIDC aware clients Jun 15, 2022
@hughns hughns requested a review from dbkr October 8, 2025 12:55
Co-authored-by: Hubert Chathi <hubertc@matrix.org>
@richvdh richvdh requested review from richvdh and removed request for richvdh October 16, 2025 15:12
@turt2live
Copy link
Member

Though it's not my concern, we can run the FCP process for these concurrently. If something comes up which blocks MSC4191, it also blocks this one.

@mscbot resolve MSC4191 has not landed

@mscbot
Copy link
Collaborator

mscbot commented Nov 18, 2025

🔔 This is now entering its final comment period, as per the review above. 🔔

@mscbot mscbot added final-comment-period This MSC has entered a final comment period in interest to approval, postpone, or delete in 5 days. and removed proposed-final-comment-period Currently awaiting signoff of a majority of team members in order to enter the final comment period. unresolved-concerns This proposal has at least one outstanding concern labels Nov 18, 2025
@turt2live turt2live removed the 00-weekly-pings Tracking for weekly pings in the SCT office. 00 to make it first in the labels list. label Nov 18, 2025
@turt2live turt2live moved this from Ready for FCP ticks to In FCP in Spec Core Team Workflow Nov 18, 2025
@mscbot
Copy link
Collaborator

mscbot commented Nov 23, 2025

The final comment period, with a disposition to merge, as per the review above, is now complete.

@mscbot mscbot added finished-final-comment-period and removed disposition-merge final-comment-period This MSC has entered a final comment period in interest to approval, postpone, or delete in 5 days. labels Nov 23, 2025
@turt2live turt2live merged commit e9f0f31 into main Nov 24, 2025
1 check passed
@turt2live turt2live added the spec-pr-missing Proposal has been implemented and is being used in the wild but hasn't yet been added to the spec label Nov 24, 2025
@turt2live turt2live moved this from In FCP to Requires spec writing in Spec Core Team Workflow Nov 24, 2025
@zecakeh
Copy link
Contributor

zecakeh commented Dec 17, 2025

Spec PR: matrix-org/matrix-spec#2272

@tulir tulir added spec-pr-in-review A proposal which has been PR'd against the spec and is in review and removed spec-pr-missing Proposal has been implemented and is being used in the wild but hasn't yet been added to the spec labels Dec 17, 2025
@tulir tulir moved this from Requires spec writing to Requires spec PR review in Spec Core Team Workflow Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec matrix-2.0 Required for Matrix 2.0 proposal A matrix spec change proposal spec-pr-in-review A proposal which has been PR'd against the spec and is in review

Projects

Status: Requires spec PR review

Development

Successfully merging this pull request may close these issues.