How to connect Ping Directory API in postman

:bangbang: Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.

Hi Team,
We have a openLdap source which named as pingd but we are not able to handle the OU movement change when LCS change from active to inactive. So we are trying to use the ping directory api to update the DN. Is there any way to connect with postman and IDN tenant? Any solution will be appreciated.
Here is the link for the pingD api: https://apidocs.pingidentity.com/pingdirectory/directory/v1/api/guide/

Thanks,
Shantha Kumar

Hi @Santhakumar,

You cannot link ping Directory → IDN → postman directly.

IDN have is own collections of api for postman that you can use for test IDN apis.

As IDN i don’t now if ping already have it’s own collection but you can create your ping directory collections on postman for testing ping apis.

For your use case, you have to choice :

  • Using Before provisioning :

    • In your lifecyclestate “inactive” configuration, configure account disable
    • Using beforeprovisioning rule for disable
  • Using worlflow :
    - Trigge your lifecycle state change
    - Use “http request” action to do ou mouvement with ping api.

1 Like

Hi @baoussounda I have tried to append the pingD api collection in postman but can’t able to trigger the api call. Is there any link or steps to connect pingD api in postman?

Hi @Santhakumar,
After search, i found Ping Identity official documentation here : Postman but in existing collections i not see Directory api, you can look your self.

I found anoteher public Workspace that use PingDirectory collection :

https://www.postman.com/winter-star-928760/workspace/team-workspace/collection/18324977-2c7b3c9b-c496-4833-a9d8-a76bb35d095c

You can fork this and use it. Be aware to not put your sensitive information directly into public workspace.

It’s simple with Postman to test api without collections by simple create requests.

Sorry, my first impression was what Ping Identity is doing in SailPoint discussions :smiley:

Anyway, we do move OU when there is a change in user LCS to inactive. Perhaps, you should focus on fixing it there.

The basis of any IDM solution is to manage the user LCM, if you do some stuff outside the IDM product manually using some API calls, that doesn’t sound good.

We have tried with OU change in ldap but it’s not happening so then we decided to try the OU change through pi gone api, also does Open Ldap support OU movement or update provisioning policies?

Closing this topic as it is not related to SailPoint. For more information about Ping APIs, please see Ping’s developer portal.

1 Like