Category: <span>password management</span>

What Is Unsolicited Login? Unsolicited login is the functionality where users access some part or feature of an application anonymously, but another part or feature requires them to login/authenticate before using those features. An Unsolicited Login Scenario For OAM Let’s assume that there’s an application ABC which we access using www.abc.com. By default, any user

One of the many exciting features of the Hitachi ID Identity and Access Management (IAM) Suite is the web services API which is accessible using SOAP over HTTPS with a WSDL specification. This API allows other enterprise applications to access workflow request queue, user data and resources that exist within an instance of the Hitachi

While upgrading a client to NetIQ IDM 4.6, I ran across some debug code that I had written to display a trace message with a user’s password that was no longer working as intended.  When trying to track down password sync issues, this type of policy can be extremely useful.  The problem is that in

Recently we ran into this error after installing SSPR in a new environment.  After completing the install of IDM and SSPR we were doing some User Activation testing through SSPR and this error reared its ugly head. The SSPR login page loaded fine and we were able to click the User Activation link with no

We’ve put together a short list of some best practices for unique login names.  Users having a unique name is important for auditing and security. Define a method early on to help assure users are always unique across all systems and helps pinpoint any security and audit concerns quickly. Avoid recognizable naming standards. Such as

As part of the provisioning process, it is common that users have to perform an account activation or claiming step. Sometimes this as simple as clicking a link in an email, while others require you to type in some code or value from and email, and even others goes as far as to require you

Problem: So maybe my pain will help someone else. I recently encountered an issue when combining OAM, Unsolicited Login and SSL. I had configured everything properly in a test environment so that Unsolicited Login worked properly over HTTP. Testing verified everything worked properly. As soon as we switched to using our HTTPS-only endpoints everything broke.

One of the new features in OAM 11g R2 PS2 (11.1.2.2) is called Persistent Login also known as Remember Me. Basically this means that OAM will have the option to remember a user’s session for some defined period of time so even if they close their browser, they’ll be able to log back in again

Just a helpful hint that may save you time, if you are attempting to configure the security store as a final step in the OIM 11gR2 process ensure that the PREFIX_OPSS schema password does not contain special characters. The database and OPSS don’t have issues with it but configuring the OPSS security store via wlst.sh