Modify docs for ingress ssl passthrough and SSO (#2649)

docs/operator-manual/ingress.md

@@ -58,6 +58,10 @@ metadata:
     kubernetes.io/ingress.class: nginx
     kubernetes.io/tls-acme: "true"
     nginx.ingress.kubernetes.io/ssl-passthrough: "true"
+    # If you encounter a redirect loop or are getting a 307 response code 
+    # then you need to force the nginx ingress to connect to the backend using HTTPS.
+    #
+    # nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
 spec:
   rules:
   - host: argocd.example.com

docs/operator-manual/sso/index.md

@@ -116,6 +116,10 @@ data:
     cliClientID: vvvvwwwwxxxxyyyyzzzz
 ```
 
+!!! note
+    The callback address should be the /auth/callback endpoint of your Argo CD URL 
+    (e.g. https://argocd.example.com/auth/callback).
+
 ### Requesting additional ID token claims
 
 Not all OIDC providers support a special `groups` scope. E.g. Okta, OneLogin and Microsoft do support a special