Use -ForceOAuth - update example text

[2ATCaroline]

You want to update the example as WS-trust authentication is deprecated to:

(Online - use oAuth and XrmTooling Ui by providing your UPN and the enviroment url)
connect-crmonline -Username "user@domain.com" -ServerUrl .crm.dynamics.com -ForceOAuth

[seanmcne]

Hi @2ATCaroline thanks for the suggestion! I was under the impression the XRM Tooling powershell connector library would default to oAuth but it looks like that might not be the case. I was thinking as an alternative we could ship an update that defaults to ForceOAuth for connect-CrmOnline.

[2ATCaroline]

Hi @seanmcne,
Even better! Or both (for now) :)

[MattB-msft]

Its coming, next drop of the lib will do it automatically.
We are pending a few updates for new GEO’s

Thanks

[seanmcne]

@MattB-msft - is there a graceful way now (in the latest update) to have the module attempt using oAuth and fallback to WS-Trust if it fails? Right now we're using a connectionstring to ensure consistent behavior of the connector but defaulting to WS-Trust. Can we change this to have a "try oAuth and fallback" or is this something we should attempt to handle within the module?

Thanks!