It has been suggested that I write a post explaining some of the big changes that we have been doing with the forums, wikis, and blogs over the last few weeks.Â Here is a quick list:
- Forums, wikis, and blogs have been moved from iChain to Novell Access Manager
- Wikis have been upgraded to MediaWiki 1.17
- Blogs have been upgraded to the latest version of WordPress
- Blog and wiki servers have been patched to the latest kernel, Apache, and PHP
Now for the details…
Novell Access Manager
Until a couple of weeks ago, the openSUSE blogs, wikis, and forums were running on a product called iChain.Â iChain is an appliance that acts as an accelerating (caching) proxy that can perform SSO, authorization, and identity injection for applications.Â While iChain does its job very well, it was discontinued a number of years ago, and it has become increasingly difficult to keep it in service.Â Some of the major problems are that the hardware it is running on is aging, and it will not run on newer hardware.Â It is also having trouble with the extensions and field formatting of newer certificates, and it also has a lot of trouble with clients attempting to use newer TLS protocols.Â Those of you who tried logging in to openSUSE.org with an iOS5 device more than two weeks ago have probably noticed this.
Novell Access Manager is the successor to iChain. While it is slightly more buggy, it has a lot of additional features, and is an actively developed and supported product. Recent builds have also been much more stable and issue-free. It works on a different principle than iChain in that it is based on a federation model. This makes SSO across domains and organizations much easier. For example, openSUSE.org is now single sign-on with www.novell.com and www.suse.com. We can also do SAML 2 federation with other sites, if that ever becomes necessary.
While we are working on moving the rest of the Novell related sites to Access Manager, we are running in what we call “migration mode”. In this setup, iChain continues to handle the authentication for itself and Novell Access Manager. This allows us to retain single sign-on between the two systems as we migrate. As some of you have noticed, a side effect of this is that the openSUSE sites now log in via a Novell-branded login page. When the rest of the sites have been moved off of iChain, we will be able to change back to an openSUSE branded login. This will probably take some time, but we will get there.
Since the openSUSE blogs, wikis, and forums were running on a single iChain server that is out of warranty and irreplaceable, they were among the first sites to be moved to Access Manager. While this provides some benefits, it has also led to a couple of problems that come with being the guinea pig.Â The first is that we are having a few problems with the IPv6 tunnel that was set up for these sites, and the IDP domain (login.novell.com) does not have an IPv6 address yet.Â I have reached out to the networking team to get this resolved, hopefully this week.Â The second is that the default Access Manager timeout is very short compared to what the openSUSE contributors are used to.Â I changed the timeout to 4 hours last night, so this should no longer be an issue.Â I know the change has been frustrating for a few of you, but I hope that you can agree that it’s better to work out the kinks now, rather than waiting for the old system to break down.
While MediaWiki 1.17 comes with a lot of improvements, many of you have also noticed that it came with a lot of heartburns.Â The biggest one was the UTF8 corruption that happened on most of the wikis.Â This seems to have come from a combination of an outdated collation on the “older” wikis and the way that the update script handled the schema changes.Â This highlighted a problem that I was not aware of before, which is that there are some major collation differences between the “new” (i.e. English and German) wikis, and the “older” wikis that were not recently rebuilt.Â After many hours, I found a way to fix the UTF8 corruption, andÂ I also worked with our DBA to get the collation of the other wikis to match the new wikis as best as we could.Â This should minimize the chance of future upgrade issues.
The WordPress upgrades are usually much easier than the MediaWiki upgrades, and this was no exception.Â Except for a minor glitch in the theme for logged in users, there are no known issues with the new software.
Similarly to the WordPress upgrades, this was a pretty uneventful change.Â This update fixes a lot of vulnerabilities, including the “Apache killer” DoS attack discovered over the summer.