This refers to the *foreman* params rather than the *foreman_proxy* params.  The idea is that an all-in-one installation would by default take the secret that was computed by the generate password routine in `foreman::params`, so they both match.

It then allows a user to override `oauth_consumer_*` in both classes if they want their own key or secret.

Another way of doing it I guess would be to use the same cache_data construct in foreman_proxy::params, since it's "cached", we'd get the same key+secret initialised in both classes.  I'm happy with this current method though, less duplication.