When you configure integrity QOP policy membership by Vantage profile, the corresponding tdatProfile object must already exist in the directory.
When users log on to the Vantage through an application that uses pooled sessions, the users are subject to the profile for the application user, not profiles in which the users have membership or to which they are mapped.
Using Teradata schema extensions:
dn: cn=low,cn=integ-qops,cn=policy1,cn=tdatrootP,dc=domain1,dc=com changetype: modify add: member member: cn=profile1,cn=profiles,cn=system1,cn=tdatrootA,dc=domain1,dc=com -
Using native directory schema:
dn: cn=low,cn=integ-qops,cn=policy1,cn=tdatrootP,dc=domain1,dc=com changetype: modify add: member member: cn=profile2,ou=profiles,ou=system1,ou=tdatroot,dc=domain1,dc=com -