Is it possible that the attribute is being set but is just not visible by the 
user admin portlet?

Rebecca M. Fountain
Applications Developer
Tacoma Community College
Information Systems
From: [email protected] 
[mailto:[email protected]] On Behalf Of Fountain, Rebecca
Sent: Monday, August 17, 2015 2:18 PM
To: [email protected]
Subject: RE: [uportal-dev] Ldap user attributes config QUESTION

James, thanks for your response.

The field I am trying to add is called EmployeeNumber in ActiveDirectory. It is 
a field we are just now starting to use and is different than sAMAccountName or 
employeeId.

I followed the instructions at the link provided, but when I go to manage users 
and look up a user, the new attribute still doesn't show.

How do I enable the logs that you described?
Are the attributes listed on the user admin screen after you look up a user 
managed elsewhere?

Rebecca M. Fountain
Applications Developer
Tacoma Community College
Information Systems
Ph: 253.566.5106

Please submit all requests for technical support via the 
Parature<http://tinyurl.com/tccreport> support ticketing system.
Thank you

For up-to-date system change and outage information please visit:
http://tcclearn.tacomacc.edu/link/portal/16054/16061/ArticleFolder/381/System-Changes-and-Outages


From: 
[email protected]<mailto:[email protected]>
 [mailto:[email protected]] On Behalf Of James Wennmacher
Sent: Monday, August 17, 2015 9:22 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [uportal-dev] Ldap user attributes config QUESTION

Hi Rebecca,

Which attribute field are you trying to add? Did you have an LDAP attribute 
source before?  Are any attributes from LDAP showing up for users?

The steps to follow are documented at 
https://wiki.jasig.org/display/UPM42/LDAP+User+Attribute+Sources.

>From a quick glance I see the documentation page suggests the Active Directory 
>field name is sAMAccountName.  I don't know if it is case sensitive but I see 
>you have something else.

Also, it looks like you had removed the CascadingPersonAttributeDao.  I suggest 
you retain the structure specified in the documentation; e.g.
              <property name="personAttributeDaos">
                  <list>
                      <!-- Provides a single attribute (but only for the 
current logged in user):  impersonating='true'|'false' -->
                      <bean 
class="org.jasig.portal.persondir.ImpersonationStatusPersonAttributeDao" />
                      <bean 
class="org.jasig.services.persondir.support.CascadingPersonAttributeDao">
                          <property name="usernameAttributeProvider" 
ref="usernameAttributeProvider" />
                          <property name="personAttributeDaos">
                              <list>
                                  <ref bean="uPortalAccountUserSource" />
                                  <ref bean="uPortalJdbcUserSource" />
                              </list>
                          </property>
                      </bean>
                      <!-- ADDITIONAL ATTRIBUTE SOURCES GET ADDED HERE

                      Don't add more sources to the 
CascadingPersonAttributeDao.personAttributeDaos
                      list above unless you're adding "special" DAOs tasked 
with augmenting/transforming
                      the attributes generated by uP-local DAOs. 
(CascadingPersonAttributeDao takes
                      the results from the first-DAO, transforms them into a 
query, and passes that
                      query to each subsequent DAO. I.e. subsequent DAOs in the 
cascade list will
                      *not* be given a chance to process the original query. 
But they will if you add
                      them directly to the 
MergingPersonAttributeDaoImpl.personAttributeDaos list here.)
                      -->
                      <!-- Add your LDAP Attribute source here.  <ref 
bean="uPortalLdapAttributeSource"/> -->
                  </list>
              </property>



To troubleshoot you can try enabling debug logging for 
org.jasig.services.persondir.support.ldap and org.springframework.ldap to see 
if the LDAP query is succeeding and what is happening.  I hope this helps.

James Wennmacher - Unicon

480.558.2420
On 08/16/2015 03:14 PM, Fountain, Rebecca wrote:
Hello all!

I am trying to include a new LDAP attribute field for users. I have added the 
field to the persondirectorycontext.xml file and added a reference to the 
userContext.xml file. The attribute I'm adding is employeeNumber.

However, when I run the portal with the changes, the new attribute is still not 
listed in the admin screen when I look up a user.

Am I missing something?

Thanks for your help!

Rebecca

Rebecca M. Fountain
Applications Developer
Tacoma Community College
Information Systems
Ph: 253.566.5106

Please submit all requests for technical support via the 
Parature<http://tinyurl.com/tccreport> support ticketing system.
Thank you

For up-to-date system change and outage information please visit:
http://tcclearn.tacomacc.edu/link/portal/16054/16061/ArticleFolder/381/System-Changes-and-Outages



--



You are currently subscribed to 
[email protected]<mailto:[email protected]> as: 
[email protected]<mailto:[email protected]>

To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


--

You are currently subscribed to 
[email protected]<mailto:[email protected]> as: 
[email protected]<mailto:[email protected]>
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

--


You are currently subscribed to 
[email protected]<mailto:[email protected]> as: 
[email protected]<mailto:[email protected]>
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Reply via email to