Storing complex types in source connectorAttributes custom properties

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

I routinely use connectorAttributes to store custom configuration I need in before provisioning and connector operation rules.

I’ve got a use case where a map of string to string values would very useful.

With connector rules, I can see how the product serializes and deserializes data, plus I can repro the case by manually executing the IQService utils library.

However, trial and erroring this with cloud rules is to prohibitive.

Does anyone already do this and know how the product makes a nested object available in a before provisioning rule?

For example, what type is the myMap key exposed as in the rule?

{
    "name": "My Source",
    "connectorAttributes": {
        "myMap": {
            "foo": "bar",
            "baz": "bof"
        }
    }
}
2

Probably a Map or HashMap. Why not just use application.getAttributeValue() to populate a variable, then log out variable.getClass().getName() to see exactly what the type is. Is that prohibitive trial and erroring?

3

Because I have to submit a rule for deployment, then wait, then open a case to schedule a log capture, and wait :frowning:

But I suspect you are right.

4

I see - I assumed that by connector rule you were referring to something like a web services before/after operation rule that runs on the VA. You upload those yourself, and can see the logs in the VA.

On that note, it’s not outside the realm of possibility that you create a temp web services source, add your attribute, add a rule, and then log that out to the VA.

5

Good point, but, I wouldn’t know for certain whether the same code serialized/deserialized web services before/after operation rules compared to before provisioning rules.

However, that’s more likely to work than my initial example. For regular before/after operation rules (e.g., AD), I can even see the source to understand how those get deserialized, but there is no reason to assume the cloud rule works the same.