Hi Rebecca,

It looks to me that the property employeeNumber is in your 
resultAttributeMapping map so if it is in the LDAP query result, I don't 
see why it would not be in the attributes in the portal. Did you verify 
your change is in the deployed tomcat folder; e.g. 
webapps/uPortal/WEB-INF/classes/properties/contexts/personDirectoryContext.xml? 
Did you verify the case of the attribute is the same (not sure if this 
matters); e.g. the field is employeeNumber in LDAP?

Also did you try enabling DEBUG logging in 
uportal-war/src/main/resources/logback.xml? E.g. adding in

   <logger name="org.jasig.services.persondir.support.ldap" 
additivity="false" level="DEBUG">
     <appender-ref ref="PORTAL"/>
   </logger>
   <logger name="org.springframework.ldap" additivity="false" level="DEBUG">
     <appender-ref ref="PORTAL"/>
   </logger>

The debug logging may not provide enough information, but it is worth a 
try.  Sorry I don't see why it wouldn't be showing in the portal.

James Wennmacher - Unicon
480.558.2420

On 08/18/2015 01:40 PM, Fountain, Rebecca wrote:
>
> *All of the other LDAP attributes listed in persondirectorycontext.xml 
> are pulling in and showing, except the new attribute that I added 
> which is “employeeNumber”. I have confirmed the field exists in our 
> Active Directory and I added it to the persondirectorycontext.xml file 
> and the usercontext.xml file as the documentation says to do. But the 
> portal still isn’t getting the field. *
>
> **
>
> *Any idea’s anyone? I’m desperate to get this resolved today. *
>
> **
>
> **
>
> *From:*[email protected] 
> [mailto:[email protected]] *On Behalf Of *James 
> Wennmacher
> *Sent:* Monday, August 17, 2015 2:52 PM
> *To:* [email protected]
> *Subject:* Re: [uportal-dev] Ldap user attributes config QUESTION
>
> Are the other attributes from LDAP displayed, such as employeeId?  
> Also are you looking at the user using Manage Users or the Directory?
>
> You'd enable the logs by modifying 
> uportal-war/src/main/resources/logback.xml.
>
>
> James Wennmacher - Unicon
> 480.558.2420
>
> On 08/17/2015 02:40 PM, Fountain, Rebecca wrote:
>
>     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]>
>     [mailto:[email protected]] *On Behalf Of
>     *Fountain, Rebecca
>     *Sent:* Monday, August 17, 2015 2:18 PM
>     *To:* [email protected]
>     <mailto:[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 [email protected]  
> <mailto:[email protected]>  as:[email protected]  
> <mailto:[email protected]>
>
>         To unsubscribe, change settings or access archives, 
> seehttp://www.ja-sig.org/wiki/display/JSG/uportal-dev
>
>     -- 
>
>     You are currently subscribed [email protected]  
> <mailto:[email protected]>  as:[email protected]  
> <mailto:[email protected]>
>
>     To unsubscribe, change settings or access archives, 
> seehttp://www.ja-sig.org/wiki/display/JSG/uportal-dev
>
>     -- 
>
>       
>
>     You are currently subscribed [email protected]  
> <mailto:[email protected]>  as:[email protected]  
> <mailto:[email protected]>
>
>     To unsubscribe, change settings or access archives, 
> seehttp://www.ja-sig.org/wiki/display/JSG/uportal-dev
>
>     -- 
>
>       
>
>     You are currently subscribed [email protected]  
> <mailto:[email protected]>  as:[email protected]  
> <mailto:[email protected]>
>
>     To unsubscribe, change settings or access archives, 
> seehttp://www.ja-sig.org/wiki/display/JSG/uportal-dev
>
> -- 
>
> You are currently subscribed [email protected]  
> <mailto:[email protected]>  as:[email protected]  
> <mailto:[email protected]>
> To unsubscribe, change settings or access archives, 
> seehttp://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


-- 
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