Anonymous_User Absent Member.
Absent Member.
707 views

Enabling users in locality objects

Hi, I work for a systems integrator in the UK. I've got a problem with
a
customer relating to iFolder?

The customer is using locality objects within eDirectory to apply
policies
to remote users. When you try and enable iFolder access for a user
then
the iFolder management console does not parse the locality object
properly
and so cannot find the user object.

The strange thing is that the locality object is recognised in the
contexts to search setting within the LDAP object.

Has anyone managed to get locality objects to work with iFolder 2.1?
If so
How?

Help Please

Andrew Matthews



Labels (1)
0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Enabling users in locality objects

,
> Has anyone managed to get locality objects to work with iFolder 2.1?

If so
> How?
>

You mean that you use L= in your naming, ie
CN=Dave.OU=Sales.O=Acme.L=Islington?

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop (http://support-forums.novell.com)
Pedago, The Aaland Islands (N60 E20)
Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195




0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Enabling users in locality objects

I personally do not use the L= object in an eDirectory, however a
customer
does use this convention in their eDirectory in the manner that you
describe, except that they use Locality containers underneath the main
Org
unit. The localities tend to be used for mobile users and branch
offices.

In the iFolder manager if you go to the user management section and
search
for a user then the users within the locality objects show up. However

when you try and enable the user then the iFolder admin console
returns a
cannot find object error. The object error lists a distinguished name

where the locality object is listed as OU= and not L= in the path.

Any Ideas?


> >

> You mean that you use L= in your naming, ie
> CN=Dave.OU=Sales.O=Acme.L=Islington?
>





0 Likes
Highlighted
Anonymous_User Absent Member.
Absent Member.

Re: Enabling users in locality objects

,
> Any Ideas?
>

No. Let me ask Novell.

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop (http://support-forums.novell.com)
Pedago, The Aaland Islands (N60 E20)
Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195




0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Enabling users in locality objects

It is a bug. It has been entered as a defect against iFolder. I cannot

say when it will be fixed though.

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop (http://support-forums.novell.com)
Pedago, The Aaland Islands (N60 E20)
Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195




0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Enabling users in locality objects

Thank you very much for your assistance. I have advised the customer
to
not use locality objects.

> It is a bug. It has been entered as a defect against iFolder. I

cannot
> say when it will be fixed though.
>
> - Anders Gustafsson, Engineer, CNE6, ASE
> NSC Volunteer Sysop (http://support-forums.novell.com)
> Pedago, The Aaland Islands (N60 E20)
> Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195
>





0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Enabling users in locality objects

,
> I have advised the customer to
> not use locality objects.
>

That is the sensible thing. Silly bug though.

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop (http://support-forums.novell.com)
Pedago, The Aaland Islands (N60 E20)
Using VA 4.52 build 277 (32-bit) on Windows 2000 build 2195




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.