New User Default Home Space??

[jayvrod]

I finally got AD Auth setup.
When a User logs in for the first time.  There User Home Space is being created in the Company Home instead of User Homes 

I want it to go to User Homes or what ever.. What do I change to make this happen??

Also how do I give another User Admin Privileges??

Thanks
Jay

[andy]

Hi

There is no need to define the authentication component again - and it will break NLTM as it redefines the same bean.

Just add the changes to the homeFolderManager bean.

Andy

[fogo]

Hi

Is there a way to configure the ldap person import so that it does not create a space for each user it imports?

[hodsons]

I am interested how to set it up not to create the user home folders as well.  In the meantime, I have about 600 user home folders in out company home space. 

How can I delete all of these spaces?

Thanks,
Steve

[andy]

Hi

Yes, it can be configured to use a homeFolderProvider that uses a shared folder - there are examples for company home and guest home in the config.

Andy

[eron123]

I am running 2.1 with LDAP authorization.  In order to get user homes to show up in the "User Homes" space, I did the following (rather than change to the personalHomeFolderProvider).

1. in ldap-authentication-context.xml:

    <property name="attributeDefaults">
            <map>
                <entry key="cm:homeFolderProvider">
                    <value>userHomesHomeFolderProvider</value>
                </entry>
            </map>
        </property>

2.  in the unzipped alfresco.war, I modified the WEB-INF/classes/alfresco/authentication-services-context.xml file:

   <bean name="homeFolderManager" class="org.alfresco.repo.security.person.HomeFolderManager">
        <property name="nodeService">
            <ref bean="nodeService" />
        </property>
        <property name="policyComponent">
            <ref bean="policyComponent" />
        </property>
        <property name="defaultProvider">
            <ref bean="userHomesHomeFolderProvider" />
        </property>
    </bean>


I hadn't seen anyone else post that second piece, and I believe it was required in our environment.