Idea - Allows 'Find Usages' for API client in ODC portal

Allows 'Find Usages' for API client in ODC portal

New

Backend

To have a 'Find Usages' function for API clients created in ODC portal.

When we expose API thru libraries, we can add ClientId and ClientSecret as settings. Then we will add the values, in the actual consumer app settings in ODC portal. Since there can be a lot of application using same ClientId and ClientSecret, it will be useful to have a 'Find Usages' for the actual API client created.

This will allows for easy governance, and also ensure the correct app is using the correct API client.

06 Jan

Daniël Kuhlmann

MVP

I don't understand this idea. When in the ODC Portal you go to your library, the Consumers tab list all consumers of your library. For each of them you can then see the settings and edit them.

07 Jan

Jun Mun Chan

It sounds workable also, will take a look at the portal tomorrow.

Thou the actual reason why i suggested this idea, is because sometimes developer set both ClientId and ClientSecret as secret. So which means, there is no way for us to find out which API Client the app is using.

As such, i actually did delete some API clients, create new ones, and then use them. But this time round, clientId is set as NOT secret

07 Jan

Daniël Kuhlmann

MVP

I really don't understand your issue. settings like ClientId and ClientSecret, can all be set via the ODC portal. And the portal lists all the consumers of your library. What does this have to do with if a setting is set to secret. The IsSecret only refers to the fact that the setting value is stored encrypted and is not by default readable. It doesn't mean that you cannot find or edit the setting.

07 Jan