MediaWiki + phpBB + WordPress的单一用户名/密码

[英]Single username/password for MediaWiki+phpBB+WordPress


I am building a web consisting of MediaWiki and phpBB as its subcomponents. Also WordPress may be added in future. My current problem is to choose a single unified authentication method (not to force users to have a special MediaWiki account, a special phpBB account, etc.).

我正在构建一个由MediaWiki和phpBB组成的网络作为其子组件。也可以在将来添加WordPress。我目前的问题是选择一种统一的身份验证方法(不强迫用户拥有特殊的MediaWiki帐户,特殊的phpBB帐户等)。

Which approach would you recommend me? The basic limitation is that it is a simple LAMP server (no LDAP database). Possibilities I know about:

你会推荐我哪种方法?基本限制是它是一个简单的LAMP服务器(没有LDAP数据库)。我所知道的可能性:

  1. Use a decentralized protocol such as OpenID, OAuth 2.0, etc. I would prefer this approach. However, OpenID is not supported by Google any more so OAuth 2.0 would be probably more appropriate.
  2. 使用分散协议,如OpenID,OAuth 2.0等。我更喜欢这种方法。但是,Google不再支持OpenID,因此OAuth 2.0可能更合适。

  3. Use DB of users from phpBB and install some plugin to other subcomponents (MediaWiki extension for phpBB auth.)
  4. 使用来自phpBB的用户数据库并将一些插件安装到其他子组件(用于phpBB身份验证的MediaWiki扩展名。)

  5. Use DB of users from MediaWiki and install some plugin to phpBB.
  6. 使用MediaWiki中的用户数据库并安装一些插件到phpBB。

  7. Use some specialized web application for user credentials management and install plugins both to MediaWiki and phpBB.
  8. 使用一些专门的Web应用程序进行用户凭据管理,并为MediaWiki和phpBB安装插件。

2 个解决方案

#1


At the end of the day a login is a login is a login. All the custom fields specific to individual applications can be properly bridged with plug-ins. Make the app that will require the most babysitting your main database and thus login system. In many cases it's the forum, but that really varies by site.

在一天结束时,登录是登录是登录。可以使用插件正确桥接特定于各个应用程序的所有自定义字段。使应用程序需要最多照顾您的主数据库,从而登录系统。在许多情况下,这是论坛,但这确实因网站而异。

I would caution that many new forum admins eventually want to upgrade from phpBB to something that's more powerful and modern. I was one of those admins. Yes, phpBB is as good as an open-source forum gets, but it just doesn't compete with the commercial forum apps. So keep that in mind if you make phpBB your main database.

我会提醒许多新的论坛管理员最终想要从phpBB升级到更强大和更现代的东西。我是其中一位管理员。是的,phpBB和开源论坛一样好,但它不会与商业论坛应用竞争。因此,如果您将phpBB作为主数据库,请记住这一点。

#2


I think the main point you already understand: You need one of your new platforms to be the central user store. The problem you know have to find out: What platform has the plugins to interact with each other? It's possible, that you find plugins, that only works "in one direction", and for mediawiki itself you will find a log of outdated extensions, that maybe won't work anymore with the latest mediawiki versions and updates.

我认为您已经理解的要点是:您需要将一个新平台作为中央用户存储。你知道的问题必须找出:哪些平台有插件互相交互?你可以找到只能在“一个方向”工作的插件,而对于mediawiki本身,你会发现过时扩展的日志,这可能不再适用于最新的mediawiki版本和更新。

The other point is, that you should think about WordPress now, too. After you selected one central user store you mostly can't change it with a lot of work, so I would check for an integration of WordPress now, too.

另一点是,你现在也应该考虑WordPress。在您选择了一个中央用户商店之后,您通常无法通过大量工作来更改它,因此我现在也会检查WordPress的集成。

Looking at that and a short search i wouldn't prefer MediaWiki to be the central user storage, and i'm not sure, if phpBB is the best solution, too :/

看看那个和一个简短的搜索,我不希望MediaWiki成为中央用户存储,我不确定,如果phpBB也是最好的解决方案:/

I think one of the best would be to use LDAP, extensions and plugins seems to be supported and working for the latest versions of each software. You yould have a central user store, which could be easily integrated in other applications, too. What is the reason you can't use it, an LAMP stack could handle this, too?

我认为最好的方法之一是使用LDAP,扩展和插件似乎得到支持,并且适用于每个软件的最新版本。您有一个中央用户存储,也可以轻松集成到其他应用程序中。你不能使用它的原因是什么,LAMP堆栈也能解决这个问题?

The second solution i would consider to choose is to use Google's user store and access it vi OAuth 2.0. MediaWiki, phpBB and WordPress supports this with plugins and/or extensions.

我要考虑选择的第二个解决方案是使用Google的用户存储并通过OAuth 2.0访问它。 MediaWiki,phpBB和WordPress通过插件和/或扩展支持此功能。

关注微信公众号

注意!

本站翻译的文章,版权归属于本站,未经许可禁止转摘,转摘请注明本文地址:https://www.itdaan.com/blog/2015/05/09/bf5a6d3ec39385386eb4279b58003c1d.html



 
粤ICP备14056181号  © 2014-2020 ITdaan.com