Doorkeeper breaking change in token generator

We recently upgraded the doorkeeper gem via !40929 (merged).

This upgrade included a change in application ID and secret value format. For some users/customers this may be a breaking change.

For example, the Hashicorp integration does some light validation on the application ID and secret the customer provides to them from our OAuth Application. The different format now fails validation within the integration and customers are unable to configure new integrations.

• Do we consider this a breaking change? If so, this may be a production incident and we may need to get a fix deployed ASAP.
• Should we set the :hex generator configuration as described at https://github.com/doorkeeper-gem/doorkeeper/wiki/Migration-from-old-versions#api-changes-4?

cc/ @stanhu @igor.drozdov