Imanami Community

We have a need to create a dynasty based on data values in an external DB.

Database contains the SAM Account Name and another field value. We need to be able to create Groups based on this additional value.

e.g.
ODBC Data Structure
jsmith | Cambridge
sjones | Cambridge
award | Oxford
jsmith | Oxford

AD Groups to be created
Cambridge - with members = jsmith,sjones
Oxford - with members = jsmith, aware

As you can see users can have multiple values, and so need to be members of multiple groups

When running through the setup wizard I can specify the DB field as a group by value, but it then prompts me for a link in the AD. We tried linking the username field to the SAM Account field, but that doesn't create a dynasty it simply generates a group with the listed users as member.

The help is pretty light on the ground  - can anyone shed some light on solutions to our requirement.

 

in follow up to this post.

I tried adding the multple entries (oxford, cambridge) into an attribute (comma separated) in the AD and then attempted to build a dynasty from there.

The job ran and created the master group but added the users directly to it instead of creating an Oxford and Cambridge child group and populating those?

I can achieve the desired results if I create a standard SmartDL group and use a WHERE statement in the SQL query (WHERE [Loc] = 'Oxford'). However, I potentially have to create hundreds of these groups is there any provision to setup jobs via a script of commandline, I see that the querystructure is stored in the Extended Data Attribute - If I created a group via a script and populated this attribute with an LDAP query would SmartDL recognise it as a native SmartlDL group? 

 

Hello --

Dynasties can only be grouped by data that exists in Active Directory.  Database dynasties allow you to "merge" the concept of a dynasty and the concept of an imported group.  Database dynasties allow you to create a dynasty and using a source outside of Active Directory to filter which values of Active Directory attributes are allowed.

For example, you have the office attribute populated in Active Directory and you have 50 offices.  You want to create a dynasty with users from 18 offices.  These 18 offices are defined in offices.txt and this list will change over time.  You can create a dynasty pointing to Offices.txt that will include only Active Directory users who have an office that is defined in offices.txt.  As Offices.txt is updated, or users are added to your directory, the dynasty groups and membership of these groups will change as the dynasty is updated.

We do have a feature on the product roadmap to create dynasties grouped by attributes outside of Active Directory, which sounds like what you'd like to do. Unfortunately, I don't have a release date when this will be available.  I will update this post once we do have this feature available.

Best regards!

Marya

---

Marya Gomez
Imanami Corporation

Thanks for the update. We were able to come up with a solution in the meantime.