Darmstadt, December 11, 2009 - Multiple login procedures with different user
name/password combinations are often productivity-sapping inconvenience for
employees. Corporate regulations on password complexity do not provide
sufficient security. Users just write down complex passwords instead of
memorizing them. Such practices are a great security risk making vital data
easily accessible to unauthorized personal.
Secure SignOn for Enterprise Single Sign-On (E-SSO) ensures high user
acceptance, high user productivity, and efficiency by significantly reducing
helpdesk calls and by reducing the time required to login to various business
applications. These factors result in a rapid and large Return-on-Investment
(ROI) after only a short period of time.
About Secure SignOn
Secure SignOn provides a comprehensive Enterprise Single Sign-On (E-SSO)
solution based on an Activ... (more)
Whether working on user provisioning, password management, compliance,
directory virtualization or meta-directory projects, the first step has
always been about checking the data and making sure that it is clean.
What constitutes clean data, and how do we get it that way? This is almost
certainly the most important question that should be addressed when
considering an Identity Management project.
When considering User Provisioning project, there are a few basic things to
Is the data authoritative? It’s important that the data going into the
provisioning solution comes f... (more)
If you've checked the SDN Marketplace lately, you'll notice that NetWeaver
Identity Management 7.2 has finally come out of Ramp-up and into General
Availability! There's also a slew of new and updated documentation available
for the new product.
I'm anxious to try it out. Looks like it is somewhat involved and you will
need to read carefully to make sure that you do the correct steps in the
correct order. This will be unlike any other IdM/Identity Center upgrade I
have ever done. I have started to review the documentation and it looks
fairly straightforward. Rest assured that ... (more)
Recently I've been thinking about what happens to an identity through its
life cycle and how the identity data is treated during this process. I
think you will also see that the Enterprise itself has differing methods of
dealing with it as well. I am considering this to be the beginning of a
framework and nomenclature that one can use for expressing how people relate
to their Identity data on a number of different levels. I think we can pretty
much consider this to be a "work in progress," and I would greatly appreciate
So why do we need this, anyway? I have observed ... (more)
People often ask me what comes after Identity Management? My answer is that
As I've discussed before, it's really up to what the organization requires
and simply tacking on new workflows, approvals, and functionality is only
really useful if it will actually be used. However, I think we can make a
few generalizations about what might occur as part of a far reaching and
comprehensive IdM program.
Assuming that the initial project succeeded in its goal of creating an
authoritative data store and basic provisioning, there's always the goal of
adding more applications an... (more)