Summary:
How to automate single-sign-on across multiple apps...on the MediaWiki-side
of things?
Details:
My project is making a collaboration web server that includes MediaWiki,
Bugzilla, phpBB forums, and other web-base applications.
We are trying to make our own single-login mechanism for all these
apps. We appear to have an LDAP-based "back end" account database working
for the above apps, and we think we can make our own "one-stop"
registration page form where a user can register once and instantly get
accounts on all the above apps.
The trickier part:
How can we make a one-stop *login* page (different from registration page)
that can automatically login said user to all the above apps, so they don't
have to login manually to each one separately?
We presume we have to provide some sort of automation to make the above
apps auto-download cookies to the client browser for each app.
A coworker of mine suggested some sort or "front end" form that passes
login/password parameters to the "back end" forms to do this,
automatically. I think he referred to this as "screen scraping" (although
I'm not sure of the nature or the meaning of that term). Further, I'm not
sure I'm thrilled about having the password flying inside my server via a
URL, but alas it's a SSL-wrapped session, so maybe it doesn't matter.
In any case, I'm looking for suggestion on how to do this for MediaWiki.
Thanks for any help,
-Matt
Hi,
How do you restrict editing rights to registered members only ? I have some
problems with people spamming links and emptying entire pages.
-Regards,
Kenny
What permissions are needed by Wiki to use the database?
Do all permissions need to be provided?
These are the choices I have:
Select
Insert
Update
Delete
Create
Drop
Index
Alter
Thanks.
Hi,
Is it possible to add a form button to a template? Or will I have to adda
button to a template as an image? I am trying to add a button to my template
which on clicking will point to a special page.
Thanks,
Amruta
Hi,
Is it possibe to make a template used on pages unediatble on those pages. I
am passing parameters in the template call so when a user hits edit page the
actual values in the parameter are shown which the user might edit and i
want to prevent that.
Thanks,
Amruta
I added 'xls' to the array $wgFileExtensions in LocalSettings.php,
and tried to upload a ~20kb spreadsheet.
I get the message: "The file is corrupt or has an incorrect
extension. Please check the file and upload again."
I tried uploading several times, and successfully opened the file in
MarinerCalc. (I don't do monopolies, so can't check it in Excel, but
I'll bet neither can MediaWiki... :-)
The server is case-sensitive; the client is case-preserving. The
actual file extension is lower case.
I've done the same procedure with 'pdf' files, and can successfully
upload those.
This is MediaWiki 1.5.3, on MacOS X 10.4.5 with MySQL 5.0.15.
Any ideas?
:::: Beware of the military-industrial complex. -- Dwight D. Eisenhower
:::: Jan Steinman <http://www.Bytesmiths.com>
Hi,
I have created a custom namespace and create certain pages in this namespace
automatically. I want to know how to create a button on every page created
within this namespace at the time the page is created. On clicking this button
the user will be directed to a special page associated with some function.
Thanks,
Amruta
> > Quick question. I have checked the FAQ and the documentation. Why
> > doesn't mediawiki use mysqli?
>
> Why would it?
Hello Brion,
Well, as Sylvain said, there are a few reasons NOT to support mysqli.
Like, for instance, the mysql package is installed by default and the
mysqli package is currently not installed by default. I'll admit,
right now that's a very good reason to refrain from making it the
default method.
The first reason TO use mysqli that you might care about (which was told
to me by someone on #MediaWiki) is that mysqli_stmt is much faster and
much more secure than mysql_query (you don't need to escape the inputs
to mysqli_stmt). The API is supposedly better, but they seem equally
simple to me.
The only reason *I* would like to see mysqli supported (even if it was
not the default method) would be so we could use mysqli_embedded.
mysqli_embedded allows people to use MediaWiki in standalone
applications much easier. In fact, it would allow people to use
MediaWiki without significant change in a wikipedia-on-dvd type
situation.
thanks for your time,
adrian