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