Make Identity attribute searchable bug

Feedback Bugs
1

What problem are you observing?

Hi Team, when we are trying to set custom attribute searchable it is throwing 500 error standard false and searchable true through beta API:
https://developer.sailpoint.com/docs/api/beta/put-identity-attribute/#_gl=1*xyp666*_gcl_au*Nzk0Njk3MDgwLjE3MDk3NjczNjk

{
    "sources": [
        {
            "type": "rule",
            "properties": {
                "ruleType": "IdentityAttribute",
                "ruleName": "Cloud Promote Identity Attribute"
            }
        }
    ],
    "name": "upn",
    "displayName": "User Principal Name",
    "standard": false,
    "type": "string",
    "multi": false,
    "searchable": true,
    "system": false
}

What is the correct behavior?

This is a bug we should have standard false and searchable true so that our correlation with this custom attribute upn works. We didn’t face this issue when we have cc API

What product feature is this related to?

beta AP:
https://developer.sailpoint.com/docs/api/beta/put-identity-attribute/#_gl=1*xyp666*_gcl_au*Nzk0Njk3MDgwLjE3MDk3NjczNjk

What are the steps to reproduce the issue?

  1. Create custom attribute
  2. Try to set searchable attribute true

Do you have any other information about your environment that may help?

This is API bug

2

I had to do this recently when working with a new connection in our Prod Tenant. And worked with no issues. Method used was PUT. I used POSTMAN to send this request.

Request URL

{{IdN_Prod_API_Uri}}/beta/identity-attributes/{{AttributeName}}

PayLoad

{
    "sources": [
        {
            "type": "rule",
            "properties": {
                "ruleType": "IdentityAttribute",
                "ruleName": "Cloud Promote Identity Attribute"
            }
        }
    ],
    "name": "{{AttributeName}}",
    "displayName": "{{Dispay Name}}",
    "standard": false,
    "type": "string",
    "multi": false,
    "searchable": true,
    "system": false
}
3

Hi Mark, Thank you for responding. Strange, we were not able to do that in Sandbox. Although I used same API through postman.

4

My guess is that one of the header values were different in Postman compared to whatever tool you were using previously.

1 Like
5

I’m also the similar issue, to make identity attribute as Searchable

6

It is because IDN has limit of 6 custom attributes only. We also had duplicate attributes created which w fixed by deleting duplicate attributes

7

Yup, agree on this. I faced the same. Is due to the limit of 6 enforced at the backend. This error can be seen by the ES team in their backend log. If you have engage ES, you can verify this with your ES counterpart on this.