On Tue, 03 Mar 2020 07:25:58 +0100, Per Jessen wrote:
Looking at the error message, I think Gertjan is on track - this is coming from vBulletin 5. I know we talked about the database needing to be upgraded, and that was the plan - but to confirm, did you install the database on version 4 first and then upgrade to version 5?
This is with vb5 connect - I am expecting the code to spot the back-level database and do the upgrade automagically.
vBulletin hasn't traditionally been that smart. There should be an upgrade script in the installation directory IIRC (I haven't looked at vb5, because I don't have access to download it). I do have a Docker container that has a fully-running vBulletin instance in it - I can make that available to you if that would help with validating the database dump you got from Jared.
The idea of running the existing code on the existing database was before we got our hands on the latest version of vB.
I understand - the thing is that vB just doesn't have the brains to automatically upgrade the database. That has to be initiated by the admin.
I am expecting to use the authentication scheme we use for e.g. our wikis and progress.o.o - any reason this would not work? I don't know much about it myself, I'll need some help with that.
I believe we use a SAML 2.0 add-on in our current implementation; logging in through the wiki and progress.o.o, I don't see any SAML traffic from my browser. Kim or Jared could confirm what the plugin we use is for SSO currently. This looks like a MicroFocus Access Manager front-end reverse proxy (the ICSLogin/ICSLogout URIs were originally used as part of the old iChain appliance, but aren't part of the current version of MFAM), which I do remember you mentioning in other messages here. It's possible it's an OAuth 2.0 authentication process that's handled completely by the proxy, and is configured to bypass the typical authorization screen (the one that defines which pieces of data you want to share with the application - that's a typical OAuth 2.0 flow, but it's not unusual to bypass that page, either). I've got a plugin in Chrome to diagnose issues with SSO logins, but it doesn't seem to be working at the moment, so it may well be a SAML connection and I'm just not seeing the traffic for some reason. I don't know the current access manager product very well (I work for a company that makes a competing product), but I know someone who at least used to be active in the openSUSE community who ISTR has pretty good knowledge of it. Let me see if he's amenable to lending a hand. -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org