Prior to "Update django-oauth-toolkit #2710" #2727 we stored our CLI app secret in the database: and exposed that value within the Web-UI (to admin Web-UI users) for use in replication. However the linked PR introduced a replication regression contextualised in "Replication regressions #2748".

It is proposed that, given the recent resolution of:

Issue: "Adopt dedicated secrets management library" #2728
PR: "Adopt dedicated secrets management library #2728" #2758

has again returned us to an install static CLIENT_SERCRET, we can approach the issue of surfacing this secret within the Web-UI again, and not in its current hashed form: an artifact of upstream changes in django-oauth-toolkit.