taphillips Absent Member.
Absent Member.
1189 views

Ldap attribute for Filr name

Hello,
Just installed a small Filr installation. Using Edirectory. Originally used emailAddress for Filr name. The imported user id ended up a 7#user@ourdomain.com .
Should I have used another item for email address to avoid the 7# at the beginning of the email address and hence the username? Also if I wanted to change the attribute to uid would I have to purge all users and their workspaces and do a re-sync after changing to uid?
Thanks,
Tom
0 Likes
4 Replies
jmarton2 Absent Member.
Absent Member.

Re: Ldap attribute for Filr name

taphillips wrote:

> Just installed a small Filr installation. Using Edirectory. Originally
> used emailAddress for Filr name. The imported user id ended up a
> 7#user@ourdomain.com .
> Should I have used another item for email address to avoid the 7# at
> the beginning of the email address and hence the username? Also if I
> wanted to change the attribute to uid would I have to purge all users
> and their workspaces and do a re-sync after changing to uid?


I haven't personally tried using the mail attribute as the Filr name.
In theory I would think it should work but it sounds like it could be
problematic. If you switch to uid, yes, you'll want to purge all the
users and their workspaces and then run a manual LDAP sync to bring
everyone back.

--
Your world is on the move. http://www.novell.com/mobility/
We know what your world looks like. http://www.novell.com/yourworld/

Joe Marton Emeritus Knowledge Partner
0 Likes
Bob-O-Rama
Visitor.

Re: Ldap attribute for Filr name

The e-mail attribute is a structured multivalued attribute. The type 7 prefix indicates an internet e-mail address. I thought a simpler representation was also available, use ldapsearch to see what is available.

We have groupwise for everyone, and before there was a "unique ID" we were using ngwObjectID - which, for us, is unique. So any attribute that user's normally use is fine provided its unique.

For our student container ( a single flat OU, we use cn. You can mix approaches, provided there are no name collisions, by defining multiple LDAP servers..

But yeah, you do need to remove the old accounts and start over as Joe says. Or reinstall the appliance(s).

-- Bob
0 Likes
taphillips Absent Member.
Absent Member.

Re: Ldap attribute for Filr name - Thanks to both

Thanks,
Really appreciate the quick response.
Tom
0 Likes
jmarton2 Absent Member.
Absent Member.

Re: Ldap attribute for Filr name

taphillips wrote:

> Just installed a small Filr installation. Using Edirectory. Originally
> used emailAddress for Filr name. The imported user id ended up a
> 7#user@ourdomain.com .
> Should I have used another item for email address to avoid the 7# at
> the beginning of the email address and hence the username? Also if I
> wanted to change the attribute to uid would I have to purge all users
> and their workspaces and do a re-sync after changing to uid?


BTW, if you use the mail attribute instead of emailAddress that should
get rid of the 7# issue. My understanding is that emailAddress is an
attribute specific to GW, and GW adds that, whereas using mail should
just be the e-mail address. Just because both attributes are
multivalued shouldn't pose a problem with the extra characters.

However, keep in mind that with current LDAP code in Filr, if you use a
multivalued attribute there's no way to tell Filr which value to use.
So, for example, if users have multiple e-mail addresses in the mail
attribute you can't guarantee which e-mail address Filr will import.
That's why you're better off sticking with attributes which aren't
multivalued unless you know for certain that all your users only have a
single value in the particular multivalued attribute you'd like to use.

--
Your world is on the move. http://www.novell.com/mobility/
We know what your world looks like. http://www.novell.com/yourworld/

Joe Marton Emeritus Knowledge Partner
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.