With the deadline for the CJIS Mandate nearing, I thought it would be a great time to discuss a highly capable strong authentication solution: Authasas. The software easily integrates with an ever-widening variety of card-readers and biometric devices. This particular solution is ideal for organizations that currently have physical access already in place, as the proximity cards can most likely be re-used for logical access after its implementation.
Working in multiple systems, applications, domains, and environments can be very frustrating and time consuming when controlling and maintaining growing businesses needs and requirements. Such things like passwords can be forgotten, lost, or even stolen more frequently in organizations that do not use any type of secure identity and access management solution. Also, provisioning users for authentication and authorization into various systems can sometimes take an entire team of resources days, weeks, or even months, depending on the size of the organization. This is why identity and access security are extremely important in almost every enterprise today. Many companies have already started to put into place different security solutions using software for two-factor authentication, and/or using identity and access management products like those offered by NetIQ, Oracle, CA, and ForgeRock.
Recently, I customized an i5/OS connector to an AS/400 system. This was a system that I had limited experience with in the past, so the first step was researching what made a user within the system, what objects get attached to that user, and what permissions needed to be set for the user to have access to the subsystems they need. In doing that, I was able to gain a generic understanding of the OS/400 server, some basic commands, and how to traverse myself through the applications.
HealthcareIDM.com just launched a few weeks ago and it got us to thinking. We wanted to know what others were doing with this technology and we decided to scour the web for other information regarding identity and access management in healthcare. We were thrilled when we saw our identity management connectors on Novell’s (Now NetIQ) website.
In the course of installing a policy agent last week, I ran into the following error: “Access denied as Agent profile not found in Access Manager”. Although the agent profile name and password were correct, it was unable to authenticate itself to ForgeRock’s OpenAM. I’ll recap it for you and give you the solution I found. By the way, I am using OpenAM 9.5.4 and policy agent 3.0.5.
Recent Comments