In one of the recent installations in a client environment we faced the below error in “application server.logs” “ 12:35:25,797 INFO [org.apache.catalina.core] (ServerService Thread Pool — 60) JBWEB001093: The listener com.sun.faces.config.ConfigureListener is already configured for this context, the duplicate definition has been ignored 12:35:26,188 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/identityiq]] (ServerService Thread Pool — 60) JBWEB000287: Exception sending context […]
As mentioned in one of the earlier post, few organizations have carried out IdentityIQ implementations in such a way that application data (access and permissions) are fetched in form of csv files using read-only delimited file connector.The greatest negative aspect of such type of architectural pattern is that the organization has to depend upon application support teams (manual process) for decisions to be […]
There can be many architectural patterns followed during a IdentityIQ implementation but the one shown below is a generic way as most of the organizations have a mixed set of applications which are to be integrated with IIQ as connected applications(using direct connectors) and disconnected applications(using Read-Only connectors).
A few months back we saw that Sailpoint released their 6.0 and then 6.1 versions of IdentityIQ. Still in many of the ongoing implementations around the world many organizations are still using IdentityIQ 5.5 version. Talking about connectors, what’s that we have been missing in version 5.5 and what’s new that we have got in […]
Certification processes are very important when we speak of Access Governance using Sailpoint IdentityIQ. Generally the concepts remain the same as in any other Access Governance product ,but let us try to gain some more insight into IdentityIQ certifications. The Certification processes allow reviewersmanagerscertifiers to review and remediate accesses granted to users on various resources […]