Hi @Cindy.cicalese!
Apparently current version 2.0 does not include "Only create user pages for non-anonymous users" patch.
Of course I could deploy REL1_37 or master of that extension into my MW 1.35 installation, but I'd prefer to go by version tags.
I have backported that patch and one other and released version 3.0. Thanks for the reminder to do so!
Fix released with version 2.0 commit cda15e8 (april 9. 2021)
Our internal wiki is supposed to be read only for anonymous, and the users are authenticating with our AD through SAML, so $wgCreateUserPage_OnLogin is set to false.
When I enable the extension on the wiki, existing user pages are created but also pages with the name : User:10.XXX.XXX.XXX (10.XXX.XXX.XXX is the IP address). I think they come from our enterprise search which is using the mediawiki API to get results.
How can I prevent the extension from creating such pages ?
Feature added in Version 2.0.
This extensions assigns the newly created user page to the user. I think it should be possible to set a specific user to whom the edit is attributed like it is possible for the NewUserMessage extension or other extension creating content automatically. I believe it should be possible to see that not the user created the page initially but a "bot". Thanks for considering this enhancement.
That sounds like a great enhancement. Could you please add a Phabricator task for it? I will try to get to it soon.
Thank you! I have uploaded a patch. Once you have a chance to test, please give it a +1 if it's OK.
When using Extension:SimpleSamlAuth, you must set $wgCreateUserPage_OnLogin=false;
Hi Cindy,
I just installed v1.2 (d36a151) of this extension on my meza deployed mw 1.31.1 (a4c8065) using SAML as the SSO and was surprised that it didn't work. I'm not a SAML export but I'm wondering if you can think of any reason why this wouldn't work out of the box with SAML-based SSO authentication.
/Rich
If the SAML extension you are using does not support the UserLoginComplete hook, you would have the same problem that we discussed at Topic:U0mwtk3njfvf3moi. Did you try setting $wgCreateUserPage_OnLogin to false to see if that makes a difference?
You were using Extension:SimpleSamlAuth, correct? Extension:SimpleSAMLphp does support th UserLoginComplete hook.
Yes. per Meza 31.8 to be exact. Does this mean that since SimpleSAMLphp supports the UserLoginComplete hook that something is wrong with my SimpleSAMLphp integration?
No. There are two different MediaWiki extensions that work with the PHP simpleSAMLphp library: Extension:SimpleSamlAuth and Extension:SimpleSAMLphp. The former is the one that you are using (which is included in meza), and it does not support the UserLoginComplete hook. The latter does support the UserLoginComplete hook.
The Semantic Signup extension is no more maintained, I think this one could replace it. But in order to do this, the extension should be able to redirect the user to the page newly created, with an "action=formedit".
Do you think it is possible to implement this redirection in the extension ?
Interesting idea. That could potentially add quite a bit of complexity to this otherwise simple extension, increasing the maintenance burden. If a simple patch were proposed that did not introduce dependencies for those wanting the simple, non-redirecting behavior, I would consider it.
Added $wgCreateUserPage_OnLogin
Hi Cindy, the extension installed without issue, but it did not re-write/re-create my user page as I was thinking it would.
In my LocalSettings.php I have:
wfLoadExtension( 'CreateUserPage' );
$wgCreateUserPage_PageContent= "{{UserDetails|UserUsername=test1|UserDisplayName=test2|UserWorkEmail=test3|UserWorkOrgCode=test4}}";
I did a page refresh of my user page: no effect
I deleted my existing user page: no effect
My user page has subpages. Could that affect the way it works?
Here's my system:
| Product | Version |
|---|---|
| MediaWiki | 1.28.2 |
| PHP | 5.6.31 (apache2handler) |
| MariaDB | 5.5.56-MariaDB |
| ICU | 50.1.2 |
I tested to be sure, and subpages do not prevent the user page from being created. Did you log out and log back in? The extension creates the users's user pages if it does not exist when the user logs in.
Cindy
ok. hmm.. could it be because I am being auto-logged in with "Auth_remoteuser" extension that the "Create User Page" extension isn't being triggered?
Oh, yes, that's it. CreateUserPage relies upon the UserLoginComplete hook, which doesn't get invoked for Auth_remoteuser. I could add a flag that would optionally allow the check to be done on each page load.
I just released version 1.2 with a $wgCreateUserPage_OnLogin configuration variable. Set it to false to check for the user page on each page load rather than at login.
A patch was merged to fix the problem.
Text placed on a user: page by this extension for me was not wikitext -- {{user}} was consequently not executable.
By default, the extension places an invocation of a template named "User" on the page (with the wikitext {{User}}). If you want to accept that default, you will need create page Template:User and populate it as you wish. Otherwise, you can use the $wgCreateUserPage_PageContent configuration variable to set the default text to whatever you want.
If you are seeing something other than {{User}} on the page by default, I will need more information (what extension and MediaWiki versions are you using, what is your configuration/environment, what *exactly* are you seeing) in order to diagnose the problem.
A patch was just merged that may fix this problem. There was a problem that only affected MediaWiki 1.29+.