Dmitry,
You will just need to ensure that the transformation rule is triggered by a POP, rather than the request path. This will make the credential attributes, as defined by the the 'cred-attr-name' configuration entry, available to the transformation rule.
Thanks.
------------------------------
Scott Exton
IBM
Gold Coast
------------------------------
Original Message:
Sent: Wed September 02, 2020 03:39 AM
From: Dmitry Tomko
Subject: concatenate tagvalue headers (ldap fields)
Hello Scott,
thanks for your response, i will try that. Am I right that ldap tagvalue fields already present in request field, i.e. they inserted by isam before transformations?
------------------------------
Dmitry Tomko
JV IBA
Minsk
Original Message:
Sent: Wed September 02, 2020 12:25 AM
From: Scott Exton
Subject: concatenate tagvalue headers (ldap fields)
Dmitry,
The easiest way to do this would be to create a HTTP transformation rule on the request which creates the new request header based on the contents of the relevant attributes found in the credential.
------------------------------
Scott Exton
IBM
Gold Coast
Original Message:
Sent: Tue September 01, 2020 12:34 PM
From: Dmitry Tomko
Subject: concatenate tagvalue headers (ldap fields)
Hello colleagues,
i have following question: our ISAM 9.0.7.1 is connected to AD and there are some AD fields: like first name and last name. But I need to present FirstName + LastName as a one "Full Name" and provide it as one header for back-end. It seem HTTP-tag-Values is what I need, but I could provide only one ldap field at time in http-tag-value attributes, but not concatenate them. Is it possible to concatenate them to provide as one header How to do that?
Is it possible to use transformations to concatenated "tagvalue" ldap fields? Are they presented in the Request object?