We have two separate subdomains working with Drupal 7 and aMember 4 integration: http://www.mysite.com - Drupal 7https://account.mysite.com - aMember 4 I swear at one point, when I logged into one site, I was logged into both, but now that seems that only works one way. If I log into www/D7 first, I am logged into account/a4. Links crossing back and forth between both sites work, maintaining my user login. When I log out of www/D7, I am also logged out of account/a4. However, if a user logs into account/a4 first, then visits the www/D7 site, they are not logged in and must log in again. Is this a known issue and/or is there anything I can do about it? -- I have also found that aMember's Access Log and Account Sharing Prevention tools are not of much use anymore since they only track visits and logins to the account/a4 site, not the www/D7 site. What can I do to fix this? I was thinking about forcing all logins to go through the aMember login form instead of the Drupal login form to capture account access, but the first issue listed above makes that a non-option. -- Is there any way to link User Profile fields between the two user databases? For instance, aMember has a First Name and Last Name field for a user. Drupal allows you to add any custom fields you want. Can I create a link or integration between the two that will be maintained if a user modifies information on either site? Since both aMember and Drupal can both have custom Profile fields, this would be a very powerful feature for both systems to be able to use this kind of data. -- Any help is appreciated.