No author bio information
0 points earned on legacy (former) Cool Solutions site
700 points earned on this site
GCVs are immensely valuable components within an IDM solution. Use of GCVs can increase the configurability and reduce the amount of code customization required to both reproduce a solution, to move it between deployment stages (I.e, dev to test to production), and maximizes agility in case a solution’s name space or other factors need to…
I recently implemented the cool solution, “Setting a password in workflow” for one of my clients. This allows us to set userPassword within a workflow. But the source of the password data might often be a form. A common configuration is that when using a password field, you have the ability to provide a…
Nobody who works in the field of Identity Management will deny the value of software development disciplines in this endeavor. Novell’s embrace of Eclipse as the platform for Designer and integration with Sub Version (SVN) are examples of the value of these technologies. One that still needs attention, however, is staging.
Staging is the concept of taking a project through various stages between development and production. These can include QA and UAT but depending on the maturity of the project and the methodology of the client, no staging to many stages can been seen.
There have been some discussions of staging within Designer, but they have centered more around using features to copy projects, and add additional objects into the model which can be deployed along with the project.
Our client asked us to automatically produce a monthly report which would allow them to see all users and what their last logon time was. This is an audit requirement, and it needs to be done by someone other than the system administrators, making it a perfect candidate for automation.
This solution is an example of how the XML tokens can be used to create new HTML to be inserted into an eMail template. While this is a relatively simple task, it did offer an opportunity to utilize this new, unheralded feature of IDM 3.6.
Our client is concerned about a well known behavior in AD with regards to synchronization of the last logon time of a user. In Active Directory, the attribute lastLogon contains the last time a user logged in. This attribute, however, is not replicated between domain controllers. Therefore, since IDM runs off one of those domain controllers, only user who logged in at that specific DC would be synchronized. This solution demonstrates how to use the scripting driver to retrieve more updated data for lastLogon.
In addition to identity management consulting, our company provides outsourcing of Identity Management solutions to our clients. In some cases the client continues to operate their own Active Directory environment. But sometimes the client doesn’t pay attention to our instructions about AD maintenance leading to issues. To help solve this problem, we have crafted a little solution which will notify us automagically by eMail whenever a new domain controller appears on the network.
Come see how we used Password Management from Novell to make it easy for our client’s customers to manage their own passwords online. With an array of Novell’s password management software, we helped improve productivity and security in a B2C environment.
Ever find that some of your AD user synchronization doesn’t? Then you investigate and find that it’s the data in eDirectory not being acceptable to the schema in AD. Well this policy is designed to help alleviate some of that, without having to hand code policies for each attribute in the schema.
This article discusses a way you can use a mapping table even if the data you are searching for is not an exact match of the data stored in the table.