Dev Issues:
https://issues.redhat.com/browse/GITOPS-1042 (1.2)
https://issues.redhat.com/browse/GITOPS-547 (1.3)
Notes for 1.2 (please read notes for 1.3 as well below this section):
Developer docs for this issue is available here: https://argocd-operator.readthedocs.io/en/latest/usage/keycloak/
Also see the Dev user guide (UG): https://docs.google.com/document/d/1147S5yOdj5Golj3IrTBeeci2E1CjAkieGCcl0w90BS8/edit#heading=h.21mpc3as6cii
A lot of this content already exists: https://docs.openshift.com/container-platform/4.8/cicd/gitops/configuring-sso-for-argo-cd-on-openshift.html though not in the exact flow as that in the UG.
Need to verify the sections that are missing. On first skim, the unistallation and disconnected sections are missing on our docs, I have asked for more information from Abhishek, too.

Notes for 1.3:
In 1.3 we are trying to do away with the manual approach and automate SSO.
AC for dev issue:

• After Argo CD is installed, RH SSO is automatically configured and users can log in to the default Argo CD instance in the openshift-gitops namespace using their OpenShift credentials.
• Admin can disable the RH SSO installation after operator is installed which would result in removing the RH SSO deployment from the openshift-gitops namespace
• Any new Argo CD instance can be enabled with RH SSO by setting the flag to true. (Default is disabled, if the flag is not present)