Use integrated identity information to create and manage identities and control access to enterprise resources. We provide identity and access management, single sign-on (SSO), access governance, and more.

Detect and respond to all potential threats quickly and decisively. By monitoring user activities, security events, and critical systems, we provide actionable security intelligence to reduce the risk of data breach.

Migrating from Windows XP or 2003 to SUSE Linux

We were looking the best way to integrate our Open Enterprise Server 2 SP2 Linux Cluster environment with our Apple mac labs. We looked for solutions like Kanaka, connecting directly every mac workstation to eDirectory (Simon Flood talk on BrainShare 2010) or trying to put every user identity from our eDirectory to our OpenDirectory Server (Snow Leopard 10.6.3 Server).

We focused our efforts on the last options so here are the steps that we followed.

Sometimes you may want to start a workflow, but delay specific parts of the workflow until a specified date or time has come: A new user might need to be created at a certain date, a workflow action should be performed at midnight, an object needs to be created at one time and be deleted some time later.

While all of these actions could be performed by IDM drivers, it may often be more flexible, easier and a matter of minutes to add such delays in the workflow itself.

One of the really neat features of Novell Identity Manager is the set of built in functionality. Now much of it is often a simple function, that is pretty commonly used, wrapped into a token with a nicer interface.

Recently there has been a growth of users wanting more e-mail storage, more collaboration and greater client access capabilities. IT professional are stuck administrating a multitude of services and applications. Now with Google Apps, it is possible to have all these features and more, but having your email and collaboration system disconnected from your production environment isn’t the best solution.

You’d think synching (add/modify/remove) an attribute like “Login Expiration Time” to AD would be simple, right? Well, there are a few quirks and a few hurdles you have to navigate to make it happen. But it can be done fairly easily… read on.

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.