Jim Henderson wrote:
Thanks for this update, Per. A couple comments inline below:
On Mon, 02 Mar 2020 13:26:14 +0100, Per Jessen wrote:
- I am not yet able to actually run the vBulletin code - currently I get an HTTP 500, which I'm still trying to figure out.
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. The idea of running the existing code on the existing database was before we got our hands on the latest version of vB.
- authentication. The 'vb_user' table holds 40501 rows. The current system is tied in to the SSO setup in Provo, I don't know how or if this table is used.
The way it works (as I understand it) is that the SSO process sends over data to vBulletin so it can provision the records in the database. vBulletin itself doesn't know about the external authority, so each of those rows of data is a valid user. The passwords that are stored are bogus
Okay, thanks, good to know. [snip SSO] 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. -- Per Jessen, Zürich (3.9°C) Member, openSUSE Heroes -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org