- Products
- Solutions
- Resources
- Trials
- Support
- Partners
- Communities
Remember that for ActiveRoles, the "anchor" object for an identity is an AD user. It's also the way the product is licensed.
I would propose two options (there are likely others):
1) Store these names in a readily accessible database that an Active Roles workflow-driven script could reach out to to perform its checks OR
2) Store the user names in Contact objects in AD that are made invisible in Exchange but could be queried by Active Roles.
Both approaches will require some customization efforts.
For 1) above, AD LDS might be a good choice because it's free and Active Roles "natively" supports it so you could easily query it.
For 1) above, AD LDS might be a good choice because it's free and Active Roles "natively" supports it so you could easily query it.