Lookup Transform - Default Value

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Does anyone know if it’s possible and if so, how to let an identity profile value pass through as the default value in a Lookup Transform?

Use Case: We have multiple authoritative sources with a “Company” value and need a transform to “standardize” the various values into a shortened consistent value for use downstream in Azure for dynamic distribution list membership.

Example:

  • XYZ Inc. => XYZ Inc (removing the “.”)
  • ABC /dba Special Name => ABC (removing the “doing business as” portion)
  • …
  • Default => Value passed directly from Identity Profile (Yes - it’s likely possible to do a FirstValid here, but trying to avoid that)

But if the value isn’t in the lookup table (i.e. lookup is corrections only) then the value passed in should be the actual value (Example ABC Inc => ABC Inc)

2

@edmarks Did you mean you need to pass the identity attribute as the default value? If yes you can pass it like this:

"default": {
                "type": "identityAttribute",
                "attributes": {
                    "name": "department"
                  }
            }

Thanks.

1 Like
3

Hi @edmarks,

Please try the below transform it may work for you.

{
“name”: “Testing”,
“type”: “lookup”,
“attributes”: {
“input”: {
“type”: “identityAttribute”,
“attributes”: {
“name”: “Company”
}
},
“table”: {
“XYZ Inc.”: “XYZ Inc”,
“ABC@12”: “ABC”,
“default”: {
“type”: “identityAttribute”,
“attributes”: {
“name”: “Company”
}
}
}
}
}

Thank you!

4

Hello,

Maybe it can be more practical if you try to use a replace all or trim. For example, if you want to rename ABD Inc. to ABD Inc, just do a replace inc. to inc. and, if you need wnat to delele all that comes after @ or /, do a split transform.

Maybe, if you give a little bit more information i can help you more with a transform example

Hope it helps,
Pablo

5

you could set your default value in the lookup as something static (like PASSTHROUGH, for example), and then wrap the lookup transform in a static transform, and if the value returned by the lookup is PASSTHROUGH or whatever you set that to, return the Company value, otherwise return the lookup result.

1 Like
6

@edmarks try below hope this will help

{
    "name": "calc Company",
    "type": "static",
    "attributes": {
        "companyAttr": {
            "type": "identityAttribute",
            "attributes": {
                "name": "company"
            }
        },
        "cmplookup": {
            "type": "lookup",
            "attributes": {
                "input": {
                    "attributes": {
                        "name": "company"
                    },
                    "type": "identityAttribute"
                },
                "table": {
                    "“XYZ Inc.": " XYZ Inc",
                    "ABC@12": "ABC",
                    "default": "Test"
                }              
            }
        },
        "value": "#if($cmplookup == 'Test') $companyAttr  #{else} $cmplookup #end"
    }
}
7

I appreciate the communities help with this, but wanted to clarify the specifics of what I’m hoping can be done. The screen shot below shows how one (of multiple) identity profile is configured. In the transform, I’d like to default value to reference the value passed in via the EM1-DelimitedFile.organization. YES - the above examples can do this via referencing the source system attribute directly, but this is precisely what I’m trying to avoid because with multiple authoritative sources this would require a nested FirstValid transform order to be in sync with the identity profile order to ensure things works as expected. An alternative would be to create a separate transform for each auth source, but this seems like overkill.

image
image894×150 3.08 KB

8

If I’m understanding the issue correctly, I believe the only way to achieve what you’re looking to do here would be to have two Identity Attributes. The first one, call it companyRaw, you map like in your screenshot with no transform. Then the second, call it company, would leverage the previously described transforms, and reference the companyRaw identity attribute that can be mapped per Identity Profile.

9

I ended up “solving” this by using a combination of ideas from those of you that contributed, but still wishing/hoping there was a way to just reference the passed in value.

{
    "name": "Identity-Department",
    "type": "lookup",
    "attributes": {
        "table": {
            "Value to Replace1": "ReplacementValue1",
            "Value to Replace2": "ReplacementValue2",
            "default": {
                "type": "firstValid",
                "attributes": {
                    "values": [
                        {
                            "type": "accountAttribute",
                            "attributes": {
                                "sourceName": "Auth Source 3 (Identity Profile Priority 1)",
                                "attributeName": "Department"
                            }
                        },
                        {
                            "type": "accountAttribute",
                            "attributes": {
                                "sourceName": "Auth Source 1 (Identity Profile Priority 2)",
                                "attributeName": "Department"
                            }
                        },
                        {
                            "type": "accountAttribute",
                            "attributes": {
                                "sourceName": "Auth Source 2 (Identity Profile Priority 3)",
                                "attributeName": "Department"
                            }
                        },
                        {
                            "type": "static",
                            "attributes": {
                                "value": "Unknown"
                            }
                        }
                    ]
                }
            }
        }
    }
}
10

I typically use the substring transform with a begin value of 0 to access the implicit input from the identity profile mapping within a transform. For example:

{
    "name": "Identity-Department",
    "type": "lookup",
    "attributes": {
        "table": {
            "Value to Replace1": "ReplacementValue1",
            "Value to Replace2": "ReplacementValue2",
            "default": {
                "type": "firstValid",
                "attributes": {
                    "values": [
                        {
                            "type": "substring",
                            "attributes": {
                                "begin": 0
                            }
                        },
                        {
                            "type": "static",
                            "attributes": {
                                "value": "Unknown"
                            }
                        }
                    ]
                }
            }
        }
    }
}
4 Likes
11

@nsorlien This is EXACTLY what I was trying to accomplish! THANK YOU!

1 Like