This follows extensive regression into InterTiki setup problems. There are 2 bugs in here, but they are likely related as they exhibit the same performance. I am unsure where the problem lies (someone familiar with the code could fix this in a heartbeat).
Both these apply to a fresh install of Tiki and getting InterTiki up and operational. I have replicated this bug on 2 different setups (2 different hosts).
During initial server setup, as Tiki Admin, setting up the KnownHosts information. Typically, I would only setup one known host for demo purposes. However, in spite of tweaks, I kept seeing the InterTiki response error Invalid Server Key.
I tracked through to code to the /remote.php validate function, around lines 58 or so. It seems like it always ended up inside the if clause (failing the validation).
Inserting
''print_r($prefs['known_hosts']);''
at the top of the validate function I received the following from the master:
Array ( [0] => Array ( [name] => tiki2 [key] => mysecretkey [ip] => 127.0.0.1 [contact] => mizraith ) )
No wonder it failed the test, as the if statement was indexing into "known_hosts" using the key.
''!isset($prefs['known_hosts'][$key]) or $prefs['known_hosts'][$key]['ip'] != $tikilib->get_ip_address())''.
As you can see, the initial setup from within Tiki failed to properly key the database entry. The database entry has a key of 0.
Adding another "known_host" in the InterTiki admin shows correct behavior:
Array ( [0] => Array ( [name] => tiki2 [key] => mysecretkey [ip] => 127.0.0.1 [contact] => mizraith ) [anotherkey] => Array ( [name] => another [key] => anotherkey [ip] => 123.123.123.123 [contact] => mizraith ) )
Editing that first Known Host in the InterTiki admin screen does not fix the key value. AFAIK, one has to delete the first known host that is entered (throwaway). From then on, it seems to work.
Although I didn't recognize it at the time, I have seen this same error during client setup of InterTiki. In that process, admin must enter a Known_Server. The first server you enter in seems to go into the database with a key of 0, even though InterTiki will search on the server's key name.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show.tikiwiki.org instance. To start, simply select a version and click on "Create show.tikiwiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show.tikiwiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |