Active Directory IdM Driver and GCV Limits

Hi

Novell IdM 3.5.1
Windows Server 2003 R2


I was just wondering, is there any limitiation on the (number of
parameters) that we can define under the GCV (Global Config Values) on
the Active Directory IdM driver ?

We can see that we are going to define hundreds of parameters on the
the Active Directory IdM driver, so thats why i just  wanted to check
before we design the spec.

that is required because of customization of differnet AD/Exchange
specifc parameters per OU. so that Administrators can easily modify
such values per OU without going into the Policies for making changes.

Upgrading these GCVs parameters to new IDM 3.5.1 Mapping table features
is not the option. 

thanks.

Maqsood.


-- 
love anything that talks binary!
------------------------------------------------------------------------
belaie's Profile: http://forums.novell.com/member.php?userid=4368
View this thread: http://forums.novell.com/showthread.php?t=327641

As I read this, I was going to suggest a Mapping table which you vetoed 
at the end.  (On a side note, a Mapping table can be updated and take 
affect without a driver restart.  A GCV change requires a driver restart).

Another option is to store the values you need on another object.  I.e. 
Take a Profile object in eDirectory, add an Aux Class called 
AcmeADSpecailValue.

Name each profile object in a way that indicates the OU it should 
represent in AD, and then fill the value into the AcmeADSpecailValue.

Then you can write a tool, (or use C1, iManager, LDAP) to manipulate 
those values.  Since they are looked up on every call, inside your 
driver, changes take affect immediatly.


belaie wrote:
> Hi
> 
> Novell IdM 3.5.1
> Windows Server 2003 R2
> 
> 
> I was just wondering, is there any limitiation on the (number of
> parameters) that we can define under the GCV (Global Config Values) on
> the Active Directory IdM driver ?
> 
> We can see that we are going to define hundreds of parameters on the
> the Active Directory IdM driver, so thats why i just  wanted to check
> before we design the spec.
> 
> that is required because of customization of differnet AD/Exchange
> specifc parameters per OU. so that Administrators can easily modify
> such values per OU without going into the Policies for making changes.
> 
> Upgrading these GCVs parameters to new IDM 3.5.1 Mapping table features
> is not the option. 
> 
> thanks.
> 
> Maqsood.
> 

Thanks for the suggestion.

But I just want to keep my GCVs option with my solution. so my question
again is there any limitation on the number of parameter one could
define on the IdM Driver?

Regards,

Maqsood.

Geoffrey Carman;1556028 Wrote: 
> As I read this, I was going to suggest a Mapping table which you vetoed
> at the end.  (On a side note, a Mapping table can be updated and take
> affect without a driver restart.  A GCV change requires a driver
> restart).
> 
> Another option is to store the values you need on another object. 
> I.e.
> Take a Profile object in eDirectory, add an Aux Class called
> AcmeADSpecailValue.
> 
> Name each profile object in a way that indicates the OU it should
> represent in AD, and then fill the value into the AcmeADSpecailValue.
> 
> Then you can write a tool, (or use C1, iManager, LDAP) to manipulate
> those values.  Since they are looked up on every call, inside your
> driver, changes take affect immediatly.
> 
> 
> belaie wrote:
> > Hi
> >
> > Novell IdM 3.5.1
> > Windows Server 2003 R2
> >
> >
> > I was just wondering, is there any limitiation on the (number of
> > parameters) that we can define under the GCV (Global Config Values)
> on
> > the Active Directory IdM driver ?
> >
> > We can see that we are going to define hundreds of parameters on the
> > the Active Directory IdM driver, so thats why i just  wanted to
> check
> > before we design the spec.
> >
> > that is required because of customization of differnet AD/Exchange
> > specifc parameters per OU. so that Administrators can easily modify
> > such values per OU without going into the Policies for making
> changes.
> >
> > Upgrading these GCVs parameters to new IDM 3.5.1 Mapping table
> features
> > is not the option.
> >
> > thanks.
> >
> > Maqsood.
> >
> >


-- 
love anything that talks binary!
------------------------------------------------------------------------
belaie's Profile: http://forums.novell.com/member.php?userid=4368
View this thread: http://forums.novell.com/showthread.php?t=327641

No specific limitation that I know of, though I suspect the UI in 
iManager and designer could become difficult to use or even crash with 
very large numbers of GCV's.

-Father Ramon


belaie wrote:
> Thanks for the suggestion.
> 
> But I just want to keep my GCVs option with my solution. so my question
> again is there any limitation on the number of parameter one could
> define on the IdM Driver?
> 
> Regards,
> 
> Maqsood.
> 
> Geoffrey Carman;1556028 Wrote: 
>> As I read this, I was going to suggest a Mapping table which you
vetoed
>> at the end.  (On a side note, a Mapping table can be updated and take
>> affect without a driver restart.  A GCV change requires a driver
>> restart).
>>
>> Another option is to store the values you need on another object. 
>> I.e.
>> Take a Profile object in eDirectory, add an Aux Class called
>> AcmeADSpecailValue.
>>
>> Name each profile object in a way that indicates the OU it should
>> represent in AD, and then fill the value into the AcmeADSpecailValue.
>>
>> Then you can write a tool, (or use C1, iManager, LDAP) to manipulate
>> those values.  Since they are looked up on every call, inside your
>> driver, changes take affect immediatly.
>>
>>
>> belaie wrote:
>>> Hi
>>>
>>> Novell IdM 3.5.1
>>> Windows Server 2003 R2
>>>
>>>
>>> I was just wondering, is there any limitiation on the (number of
>>> parameters) that we can define under the GCV (Global Config
Values)
>> on
>>> the Active Directory IdM driver ?
>>>
>>> We can see that we are going to define hundreds of parameters on
the
>>> the Active Directory IdM driver, so thats why i just  wanted to
>> check
>>> before we design the spec.
>>>
>>> that is required because of customization of differnet AD/Exchange
>>> specifc parameters per OU. so that Administrators can easily
modify
>>> such values per OU without going into the Policies for making
>> changes.
>>> Upgrading these GCVs parameters to new IDM 3.5.1 Mapping table
>> features
>>> is not the option.
>>>
>>> thanks.
>>>
>>> Maqsood.
>>>
>>>
>