rrawson Honored Contributor.
Honored Contributor.
440 views

Application to Identity Collection Mapping Case Sensitive?


Folks,

I have a client we are configuring AR 1.1 for with a JDBC based
application collector that is collecting data but matching to the
identity collected data is incomplete. We see 7 users with accounts when
we should see over 50 on this application.

It appears to me that the matching between the Identity and Application
collectors (which I have configured using eMail address) is behaving as
case sensitive when we need it to be case insensitive. I was able to
look at the database using SQL Squirrel and the directory using an LDAP
browser, two users I checked that were among the 7 had a case exact
match for eMail, one “miss” I examined the case was different… I also
tried changing the SQL that the collector uses to force the eMail to all
lower case using the lower() function. That resulted in zero matches. I
can’t find a similar ability in the identity collector to transform the
collected address as all one case or the other.

My investigation was that for the sample user I found, Mark Hermann
there are THREE records in the database, with email of
Mhermann@acme.com, MHERMANN@ACME.COM and mhermann@acme.com with three
different IDs. They all came up in the result set from the SQL
statement, “SELECT * from P21_VIEW_USR where
email_address=’mhermann@acme.com’. The directory has mhermann@Acme.com
which is an exact match for none of them.

I could work around this if I could understand how to implement a
transformation when data is collected from the LDAP Identity source to
transform the value of the mail attribute stored in the AR database,
forcing it to lower case. Not sure if / where that can be done.

Thanks
Rob


--
rrawson
------------------------------------------------------------------------
rrawson's Profile: https://forums.netiq.com/member.php?userid=403
View this thread: https://forums.netiq.com/showthread.php?t=54404

0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: Application to Identity Collection Mapping Case Sensitive?

On 10/05/2015 04:24 PM, rrawson wrote:
>
> Folks,
>
> I have a client we are configuring AR 1.1 for with a JDBC based
> application collector that is collecting data but matching to the
> identity collected data is incomplete. We see 7 users with accounts when
> we should see over 50 on this application.
>
> It appears to me that the matching between the Identity and Application
> collectors (which I have configured using eMail address) is behaving as
> case sensitive when we need it to be case insensitive. I was able to
> look at the database using SQL Squirrel and the directory using an LDAP
> browser, two users I checked that were among the 7 had a case exact
> match for eMail, one �miss� I examined the case was different� I also
> tried changing the SQL that the collector uses to force the eMail to all
> lower case using the lower() function. That resulted in zero matches. I
> can�t find a similar ability in the identity collector to transform the
> collected address as all one case or the other.
>
> My investigation was that for the sample user I found, Mark Hermann
> there are THREE records in the database, with email of
> Mhermann@acme.com, MHERMANN@ACME.COM and mhermann@acme.com with three
> different IDs. They all came up in the result set from the SQL
> statement, �SELECT * from P21_VIEW_USR where
> email_address=�mhermann@acme.com�. The directory has mhermann@Acme.com
> which is an exact match for none of them.
>
> I could work around this if I could understand how to implement a
> transformation when data is collected from the LDAP Identity source to
> transform the value of the mail attribute stored in the AR database,
> forcing it to lower case. Not sure if / where that can be done.
>
> Thanks
> Rob
>
>

Greetings Rob,
Since you have a SR on this, I will update there.

--

Sincerely,
Steven Williams
Lead Software Engineer
Micro Focus
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.