Yes, I think so. I don't see any other way to definitively distinguish the SMW case.

I added some additional feedback on the patch. I think it needs some work, but it is a necessary addition to PluggableAuth. Thanks for the patch!

Ah, I see. We should not refer to Authority, since it was not introduced until after 1.35. I think that it is only used for a default value for a parameter, so we should be able to work around it. Thanks for reporting! Please feel free to submit a patch.

Yes, that sounds like a good idea.

Thank you for reporting this. I agree that it looks incorrect and appears to have been introduced in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/OpenIDConnect/+/426095/8/src/OpenIDConnect.php#342. Would you be able to submit a patch for this in gerrit?

Could this be related to the issue identified in https://gerrit.wikimedia.org/r/c/mediawiki/core/+/787907?

Thank you for reporting this. I will look into it as soon as I finish the update to PluggableAuth.

This capability is now fully available in PluggableAuth version 6.0. It requires a compatible authentication provider. OpenID Connect version 6.0 is compatible, and compatible versions of SimpleSAMLphp, WSOAuth, and others are in progress.

MediaWiki-extensions-OpenID-Connect only refers to mwuser in a migration script from ancient versions.

This bug has not been reported by anybody else in over 3 years. It may have been fixed by supporting software updates in the interim. I'm going to close for now, but please feel free to reopen if the issue arises again.

This was fixed by https://gerrit.wikimedia.org/r/c/mediawiki/extensions/PluggableAuth/+/544379.

Untagging MediaWiki-extensions-Semantic-Rating, since the question seems to have to do with editing ratings, which is not a feature of that extension. It only displays ratings.

Thank you for the report and the fix. Works great!

This capability was already available, although it was undocumented, It is now documented. The default behavior remains that usernames are normalized.

There are several topics discussing Azure at https://www.mediawiki.org/wiki/Extension_talk:OpenID_Connect. In particular, perhaps the discussion linked from there to https://stackoverflow.com/questions/28415234/whats-wrong-with-this-authorization-exchange would be helpful.

Thank you for reporting this. Unfortunately, there is no way to do the purging automatically in this case. You would need to either purge the page (action=purge) or do a null edit (which you were doing) to clear the cache for the page and cause the content to be regenerated. I would also have expected that refreshLinks would have worked, but it does not.

MediaWiki 1.33 is obsolete.

MediaWiki 1.33 is obsolete.

I am conflicted. While it may have been a better choice initially not to normalized the usernames by default, there is a significant user base now that has relied upon that behavior. If they upgrade without noting the change, they risk creating new accounts for some users, which would be a mess to clean up once they notice. I'd rather that we keep the current default but ensure that it is well documented (as @Seb35 did) that the default can be changed with the one line of configuration shown above.

There was a change in version 7.0 in the placement of the "default" comment block (<comment-streams/> with no id). It will always appear at the bottom of the page below the categories. If you want to place it somewhere else, you need to use a named comment block. The old behavior was very complicated since the default comment block is also used to enable comments on pages in namespaces that do not have comments enabled by default. I have now documented that as a change at https://www.mediawiki.org/wiki/Extension:CommentStreams#Placement_of_comments.

Oops.

You should be able to test it now. I will decline this once you confirm. Thanks!

Interesting. SRF is not required for CommentStreams and shouldn't affect it at all. And yet . . . when both are loaded, I get the same error you do, although each works by itself. I'll dig into it a bit more.

Thank you for the suggestion, @Lost_Student. Sorry it took so long to get to.

Is this still desired now that the UI has been upgraded to use OOUI icons?