Unable to provision the targetAddress through AD provisioning policy

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hye guys,

i have applied a trasnsform for targetaddress attribute in prov policy of AD :

{
“name”: “targetAddress”,
“transform”: {
“type”: “static”,
“attributes”: {
“userId”: {
“attributes”: {
“values”: [
{
“attributes”: {
“name”: “userId”
},
“type”: “identityAttribute”
},
“NONE”
]
},
“type”: “firstValid”
},
“value”: “#if($userId != ‘NONE’)[email protected]#end”
}
},
“attributes”: {},
“isRequired”: false,
“type”: “string”,
“isMultiValued”: false
},

And my AD is succesffuly getting created but when i see targetattribute it is coming blank any idea why?
PS : I can see in search account activity that the targetaddress attribute is getting added properly in povisioning plan but cant see in account it is blank

2

I believe that you need to set the targetaddress as

SMTP:[email protected]

Also, if that doesn’t work, check your exchange settings in the connector configuration.

3

Hi @Rakesh_Singh_1234

While agreeing with @agutschow that you do need the SMTP: prefix, if the transform worked correctly, the connector would still be able to provision targetAddress with the “wrong” value.

As it is not, you need to check the syntax of your transform. See First Valid | SailPoint Developer Community and Identity Attribute | SailPoint Developer Community

4

@agutschow i have done as u suggested now my transform is below but once thing is now account is gerting created with status completed but still i cant see target address attribute populated in account that i created. is this transform below correct:
{
“name”: “targetAddress”,
“transform”: {
“type”: “static”,
“attributes”: {
“userId”: {
“attributes”: {
“values”: [
{
“attributes”: {
“name”: “userId”
},
“type”: “identityAttribute”
},
“NONE”
]
},
“type”: “firstValid”
},
“value”: “#if($userId != ‘NONE’)SMTP:[email protected]#end”
}
},

5

Can you tell us your configuration settings from this screen:

image
image905×655 37.6 KB

6

Are you not seeing the value in the account in Active Directory or the aggregated AD account in ISC?

I’m not sure if this is environment-specific, but in our case, we are provisioning the targetAddress attribute, and it is populated in Active Directory. However, we don’t see the value in the aggregated account in ISC. Instead, we are seeing the targetAddress attribute’s value in the externalEmailAddress attribute in ISC.

Thanks,
Sushant

7

it is blank nothing configured here @agutschow

image
image898×733 27.8 KB

8

Hi Rakesh. As I implied above there is nothing special about the targetAddress attribute, it is a simple LDAP attribute which AD does not validate. If you are having a problem populating it, it will be in your transform. I would recommend going back to basics: send a static value and then build your transform in stages, diagnosing as you go. I included the links above. Also, why are you doing a transform rather than simple concatnate?

9

i tried concatenate in prov policy but still wont be able to populate target address @j_place

10

Hi Rakesh - are you running an enable-remoteMailbox powershell after provisioning?

11

whats that i am not sure ? @j_place

12

HI Rakesh - this community is designed to help people who have followed all the documentation and are still having issues getting ISC to work. With all due respect, I suggest you go back to the documentation and research the use cases you are trying to implement.