ISC documentation "Gets connector list" shows non-existing scope

Feedback Bugs
1

What problem are you observing?

The documentation for the “Gets connector list” lists a required scope that does not exist.

Authorization: oauth2
type: Personal Access Token
scopes: idn:connector-source-config:read
user levels: ORG_ADMIN

What is the correct behavior?

It should list a scope that does exist within ISC.

What product feature is this related to?

This applies to ISC.

What are the steps to reproduce the issue?

Please review the documentation.

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

N/A

1 Like
2

I’ve reported a similar issue in September (which is still not fixed), and it seems SailPoint doesn’t want to check that all document scopes can be selected in the UI. We have to create for each missing scope a ticket and wait a couple of months.

I thought solving a class of problems at once would be more efficient than solving the same problem over and over again, with all the overhead of detecting the issue, reporting it, creating an internal ticket, discussing about the priority, planning it over months, working on the issue, testing the issue, deploying the issue, informing the customers that the issue is resolved, the customer testing the issue themselves.
Well… I guess we won’t be informed when the issue is resolved.