Alan Wong

This extension does not currently support authentication. To work around, download the metadata as a text file from the endpoint and then point the OData Connected Services URI to the...

I had not come across this issue on my environment. Can you try [these steps](http://odata.github.io/odata.net/OData-Client-Code-Generation-Tool/) as a smoke test first? If the above passes, then we can proceed to try...

@siberianguy the endpoint requires authentication and at the moment the project doesn't support it. We have this issue flagged as priority 1 and will be discussing it later this week.

@siberianguy at the moment, the discussion is scheduled for Friday. I'll keep this thread posted on updates. @nla-brandonjames does your endpoint also require authentication?

All, We discussed this particular topic regarding setting up authentication in the extension during the meeting I mentioned earlier. As of this moment, we don't have resources to allocate to...

@siberianguy, PR #67 is pending changes. We don't have resources allocated for support on this at this time, but it's in our backlog. My statement regarding using the current proposed...

We'll work on this after migrating the extension to VS2017.

Because this extension has a dependency on Microsoft.OData.Client of our OData Library, we'll have to move that binary to 7.x first, which I'll be working on. After that's done, we...

Here is [GitHub issue 731](https://github.com/OData/odata.net/issues/731) in the odata.net repo to help track the timeline.

There is a code delta between the Connected Services extension and the actively developed Client Code Gen extension; the state of the Connected Services extension is under review. A workaround...