Hello. Need help sorting out commons profiles. Prior to this change at http://drupalcode.org/project/commons.git/blobdiff/0a801ee59ad390bfabcef312b2ee826eb2467378..c42d2defcf747a2f211326e7d1ead442a0671aca:/modules/features/commons_status_streams/commons_status_streams.info the "commons_status_streams.info" did not have a dependency on "commons_profile". Prior to this change we also used the core "profile" module couple with ldap_integration to auto-fill about 20 profile fields from our corporate Active Directory for our users. The Commons Profile module doesn't allow for this from what I can tell and we cannot disable Commons Profile module without now losing the Activity Streams which we want.

Is there a way to have custom profile fields from AD work within Commons Profile or another way to over-ride Commons Profile (back to core profile or another module) so both custom AD fields and Activity Streams work?

For what it's worth; seeing how the Commons distribution is trying to compete with commercial social platforms for business, tighter integration with AD and other LDAP systems seems like a must have or at least is for our company.

Thanks for any pointers or assistance with this issue!

Comments

Andrea C’s picture

Agree. LDAP integration, that can be used also for AD, is a must.

We use it for authentication. But because sAMAccountName, the AD field used by the Microsoft Domain as username is usually an alfanumeric code, it would be very usufull also the features offered by the module RealName, to login with a username that must be hidden and be presented in Commons with an alias than can be autofilled from the CN field in AD or can be asked to the user during the signup (if the user is external).

Last, but not least, to compete with commercial platform, Single SignOn capabilities are really important too.

lightsurge’s picture

Status: Active » Postponed (maintainer needs more info)

@trevorw Commons profile still depends on core profile http://drupalcode.org/project/commons.git/blob/c42d2defcf747a2f211326e7d...

The Commons Profile module doesn't allow for this from what I can tell and we cannot disable Commons Profile module without now losing the Activity Streams which we want.

I'm pretty sure the Commons maintainers are very much interested in making Commons compatible with single sign on implementations... Are you saying you've tried the ldap_integration module and it doesn't work with 6.x-2.7 or that you've discovered some reason that it can't work? With either the former or the latter, I expect this issue would benefit from a description of any particular problems experienced, or details of why you think ldap_integration won't work.

trevorw’s picture

Hello @lightsurge, we do use ldap_integartion for authentication and it works very well.

What we have setup using ldap_integartion > data; we added new core Profile fields (/admin/user/profile > add new field) such as work address, work phone, job title, department, phone numbers, manager, etc. and then using ldap_integartion > data settings mapped those new core Profile fields to the correct LDAP attributes.

To make all of this show up in the Commons (started on v 2.4) user profile "about" page we had to disable Commons Profile and fall back on the core Profile which worked very well. Now that Commons Profile is required with Streams, we cannot fall back on the core Profile without losing the Streams functionality -- which we would like to keep active.

The Commons Profile does not display the added core Profile fields by default and I see no way to make Commons Profile do so. Hopefully I'm just missing something with the setup, or maybe Commons Profile should be showing these and isn't, don't know. I do know I could just removed the dependency from the Streams module but it was added for a reason, and will come back with next update, so don't want to go that route.

Happy to provide whatever I can to get our system back to where we had it, basically showing the added profile fields auto-populated with the users LDAP attributes.

lightsurge’s picture

Status: Postponed (maintainer needs more info) » Active

Think I follow you, so with Commons Profile enabled - your profile fields populated fine from LDAP attributes, but those profile fields weren't displayed as you wanted them on the 'About' page. So previously you had- disabled Commons Profile and fell back to just the default profile About pages. That right?

So this is more about making display of profile fields more configurable, than incompatibility between modules.

trevorw’s picture

Very close, change out Commons for Core and we're on the same page:
"...with core Profile enabled - your profile fields populated fine from LDAP attributes, but those profile fields weren't displayed as you wanted them on the 'About' page. So previously you had- disabled Commons Profile and fell back to just the default profile About pages..."

Thought this was only a display issue, which by modifying "profile_about_page" view could probably add back the created profile fields but again, would be nice if they would be displayed auto-magically like the core Profile does.

Just checked my database and for the newest users to our site, LDAP data is missing in the profile_values table... maybe there is a module compatibility issue too. Using ldap_integartion (6.x-1.0-beta3) with Commons 6.x-2.7. I'll play around with other version of ldap_integration in my test environment and see what I can find out there.
Scratch that, it's working as it should so it is only the display issue. That's good at least! :)

ezra-g’s picture

Issue tags: +Commons 2.8 radar

Adding to the Commons 2.8 radar.

ezra-g’s picture

Title: Commons Profile now dependent for Streams, breaks core Profile custom field integration from LDAP » Commons_status_streams shouldn't list commons_profile as a dependency
Category: support » bug

Thanks for pointing to the commit where commons_profile was introduced as a dependency for Commons_status_streams. Seems like this was unintentional, so I've removed the dependency manually.

http://drupalcode.org/project/commons.git/commitdiff/571e793?hp=8ebb27e2...

ezra-g’s picture

Status: Active » Fixed

Marking as fixed but please re-open if this doesn't address the original motivation for filing the issue.

trevorw’s picture

Will do, thanks.

Automatically closed -- issue fixed for 2 weeks with no activity.