Client registration policies can provide additional control over which registrations and configurations are accepted and stored for each client created with the OAuth 2.0 Dynamic Client Registration protocol.
If multiple policies are configured, PingFederate executes all of them based on the display order. If PingFederate completes the current policy, it moves on to the next policy. Otherwise, PingFederate returns an error message to the developers.
Note:
PingFederate must complete all policies successfully before a client can be created with the OAuth 2.0 Dynamic Client Registration protocol.