1) The Remote configuration page requires the 'rh-certified' repository to have an 'auth_url' value. See the validation code here.

This comes from the assumption that users will only sync certified content from c.rh.c to on-premise AH. This assumption is incorrect. Users may also sync certified content from Satellite, another on-premise AH, or some other source. Sources outside of c.rh.c will likely not require an 'auth_url' value.

2) Once the user modifies the configuration and removes the 'auth_url' value, the 'Sync' buttons goes away, and the 'Configuration' button appears. There's no indication of what needs to be configured or updated in order to make the 'Sync' button reappear.

3) Putting the 'auth_url' back does not cause the 'Sync' button to reappear, as one might expect from the code reference above.

4) Similar assumptions related to 'community' should be reviewed. It's possible that community content may also come from Satellite or another on-premise hub.