If you're using PingOne for Enterprise Directory as an identity repository, and your organization uses PingFederate, you should have PingFederate verify user credentials stored in the PingOne for Enterprise Directory. You don't need to make any configuration changes in PingOne for Enterprise when you configure the PingOne for Enterprise Directory Password Credential Validator in PingFederate.
We implement rate limiting on PingOne for Enterprise Directory
APIs to maintain a high quality of service for all our customers. Rate limiting
restricts any one API client from flooding PingOne for Enterprise
Directory APIs with an unusually high amount of traffic, which could affect usage of
PingOne for Enterprise Directory by other customers. If a
customer reaches the defined rate limit, the PingOne for Enterprise Directory API responds with a 429 HTTP status code Too Many
Requests.
If your integration hits the rate limit, you must reduce the rate at which your API client is making requests in order to complete any further API calls successfully. The enforcement of an API rate limit is standard practice for software as a service (SaaS) services. If rate limits are negatively affecting your usage of the PingOne for Enterprise Directory API, contact our support team to review your integration.
To enable users to change or reset their passwords, see Changing user passwords for PingFederate Bridge .