Update "oc login"

As of 4.7, "oc login" alone won't prompt you for a username and password. Update all instances in the doc set (if appropriate) that currently do so to pass in a username (or token, etc.).

distributed tracing (6 files)

• distr-tracing-accessing-jaeger-console.adoc
• distr-tracing-deploy-default.adoc
• distr-tracing-deploy-otel-collector.adoc
• distr-tracing-deploy-production-es.adoc
• distr-tracing-deploy-streaming.adoc
• distr-tracing-removing-instance-cli.adoc

Service mesh (11 files)

• ossm-control-plane-cli.adoc
• ossm-control-plane-deploy-1x.adoc
• ossm-federation-config-smcp.adoc
• ossm-federation-create-export.adoc
• ossm-federation-create-import.adoc
• ossm-federation-create-meshPeer.adoc
• ossm-jaeger-accessing-console.adoc
• ossm-member-roll-create.adoc
• ossm-observability-addresses.adoc
• ossm-troubleshooting-proxy.adoc
• ossm-updating-smcp.adoc

 Jaeger (4 files)

• jaeger-removing-instance-cli.adoc
• jaeger-deploy-production-es.adoc
• jaeger-deploy-streaming.adoc
• jaeger-deploy-default.adoc

************************************

Upstream GitHub issue https://github.com/openshift/openshift-docs/issues/31619

"oc login" no longer works in the "oc" cli 4.7 version

See...  https://bugzilla.redhat.com/show_bug.cgi?id=1920427

and...  openshift/oc@cb6b001

You must specify "--username=NAMEOFUSER" to log in.

The example output the the documentation is also incorrect.

If you type "oc login https:....." you will get:

{{oc login https://api.cluster-XXX.sandboxXXX.opentlc.com:6443
The server uses a certificate signed by an unknown authority.
You can bypass the certificate check, but any data you send to the server could be intercepted by others.
Use insecure connections? (y/n): y

You must obtain an API token by visiting https://oauth-openshift.apps.cluster-XXX.sandboxXXX.opentlc.com/oauth/token/request}}

Instead, you must type:

oc login --username=NAMEOFUSER https://api.cluster-XXX.sandboxXXX.opentlc.com:6443

Example:

{{oc login --username=NAMEOFUSER https://api.cluster-XXX.sandboxXXX.opentlc.com:6443
The server uses a certificate signed by an unknown authority.
You can bypass the certificate check, but any data you send to the server could be intercepted by others.
Use insecure connections? (y/n): y
Authentication required for https://api.cluster-XXX.sandboxXXX.opentlc.com:6443 (openshift)
Username: NAMEOFUSER
Password: }}