I too am having this trouble.

I really wish there was a switch where you could specify whether protals have seperate membership DB's, or all one.  From my understanding there would be such an option in 4.3.3, but I haven't found it yet.  Same problem as before.

Does anyone know how to modify the source to have one global membership DB?  If so, would you mind posting it? 
I've been digging around in the code for a while now and still haven't come across a way of doing it.

Thanks in advance,

Josh

My solution to the problem of users not being added to children portals
Assumptions:  All users get access to all portals and all users get all auto assigned roles.
applied to new users and new portals

Complete the follwoing steps
1. Backup your database
2. add the AutoUpdateUsersToAllPortalAccess SPROC
3. Add "exec AutoUpdateUsersToAllPortalAccess" to the bottom of Adduser and AddPortalInfo SPROCs

How this works:  When a new user is created the AutoUpdateUsersToAllPortalAccess SPROC is run via the exec command.  the AutoUpdateUsersToAllPortalAccess SPROC will add all users to all portals and Roles for all portals that are not already added.

Tested:  I have a small user table, but this SPROC runs almost instantly, your performance may differ since it is using a cursor.

I hope this helps band-aid the real problem until another solution can be implemented.





/* Created by Chris Wood Portalsdirect.com */

CREATE procedure [dbo].[AutoUpdateUsersToAllPortalAccess]
as


/* Insert User Portal Values */

declare @UserID int, @PortalID int, @RowCount INT, @RoleID int
declare cur cursor fast_forward for
SELECT     Users.UserID, Portals.PortalID
FROM         Users CROSS JOIN
                      Portals
WHERE     (Users.IsSuperUser = 0)
open cur

fetch cur into @UserID, @PortalID

while @@fetch_status = 0
begin
Set @RowCount = (Select count(*) from UserPortals Where Userid = @Userid and PortalId = @portalid)
if @Rowcount = 0 -- check conditions
begin
INSERT INTO [UserPortals]
           ([UserId]
           ,[PortalId]
           ,[Authorised])
select @UserID, @PortalId,1
end

fetch cur into @UserID, @PortalID
end

close cur
deallocate cur

/* Insert AutoAssign Roles */
declare cur cursor fast_forward for
SELECT     Users.UserID, Roles.RoleID
FROM         Users CROSS JOIN
                      Roles
WHERE     (Roles.AutoAssignment = 1) AND (Users.IsSuperUser = 0)
open cur

fetch cur into @UserID, @RoleID

while @@fetch_status = 0
begin
Set @RowCount = (Select count(*) from UserRoles Where Userid = @Userid and RoleID = @RoleId)
if @Rowcount = 0 -- check conditions
begin
INSERT INTO [UserRoles]
           ([UserID]
           ,[RoleID])
select @UserId, @RoleId
end

fetch cur into @UserId, @RoleId
end

close cur
deallocate cur

Thank you VERY!!!! much for this post. Your solution fixed my Parent/Child AD problems. I am using 3.3.5, but the code in this area is the same. You saved me hours of searching. I think this is a universal problem that needs to be addressed and the fix added to the core. Something simple that I have been pulling my hair out for a week about. Thanks again.