Dynamic client configuration updating policy information
It is standardized by both the Open ID Foundation and by the IETF as RFC 7591.These specifications define how a client may submit a request to register itself and the response that the OAuth server should provide.Most home users who use DSL/Cable routers as DHCP/NAT servers to facilitate multiple host connections to the Internet should turn off dynamic DNS updates.
Both DHCP clients and servers can generate DNS updates.
Being able to keep a credential secret is a requirement imposed by the OAuth standard to issue a refresh token.
Without this, the mobile app needs the user to re-authenticate every time its access token expired resulting in a very poor User Experience (UX).
In this introduction, we will explain when Dynamic Client Registration is useful, what the protocol entails, and a brief overview of how it can be used in Curity.
The first case comes up when an i OS, Android, and other kind of native app is installed on a user's device.
It can be extracted from the application with relative ease.