Sorry for the bad english... I have Site A (with a lot of user accounts) and Site B (only Admin). Users with Accounts on Site A should login with the same Account on Site B.

My Steps:
- i have installed account sync on both sites (same provider / server)

My Questions:
- Global settings: where can i find the server key? Can I use a key like "123456"?
- what is UID 1?
- is the configuration of sender settings and reciever settings on both sites the same?

I hope that someone can give me support in "easy english" :-)
A Installationguide would be nice...

thanks
Thomas

Comments

hadsie’s picture

hadsie commented

Hi Thomas,

- Global settings: where can i find the server key? Can I use a key like "123456"?

That's correct. You will set the key to whatever you want and this key must be the same across all sites you wish to connect to. So both Site A and Site B must have the key "123456" if that's what you're using. This will allow them to more securely talk to each other.

- what is UID 1?

UID 1 is the user id of the main admin user. Often you would want to exclude syncing on this account as it could lead to major security issues.

- is the configuration of sender settings and reciever settings on both sites the same?

If both sites are running on the same IP address then these could be the same. Otherwise you'll want to configure the IP address section appropriately so that each site has proper access to submit and receive data from the other site.

Also, I have a ton of logging in place to catch and identify errors. Make sure to enable watchdog / logging on both sites and then read through the watchdog error logs for account sync as this will provide more insight into the problem.

Hope that's "easy english" enough, but just let me know if you need further clarifications. Also, did you read the README.txt as there are a few more instructions in terms of installation and configuration in there I believe.

Cheers!
- Scott

hadsie’s picture

hadsie commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.