Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service Reference vs Connected Service. UserID Password missing #55

Open
darrelluk opened this issue May 26, 2017 · 9 comments
Open

Service Reference vs Connected Service. UserID Password missing #55

darrelluk opened this issue May 26, 2017 · 9 comments
Labels

Comments

@darrelluk
Copy link

Hi,

With a Service Reference, it correctly requests a user id and password. With Connected Service I cannot see how to achieve the same result - being prompted for, or fields for storing the user id and password.

Any ideas on how to achieve this now that Service Reference for OData no longer works in VS2017?

Thx, Darrell

p.s. same issue with Connected Service in VS2015.

@Dima1c
Copy link

Dima1c commented May 26, 2017

same problem (((

@BruceLofland
Copy link

I had to set my service authentication to anonymous temporarily to get this to work.

@mdressel
Copy link

mdressel commented Sep 1, 2017

Same here.

@TaviTruman
Copy link

TaviTruman commented Sep 9, 2017

In my case I don't own the OData Service and can't disable the OpenID Connect Authentication so I'm BLOCKED and can't use this capability at all. I find more and more that commercial web accessible OData Service Endpoints are incorporating OAuth/OpenID Connect Authentication layers and that currently runs against the grain with just about every tool I personally know of where access to the OData Service Endpoint is required in order to generate Typed OData Client proxy.

@robward-ms robward-ms added the P1 label Sep 11, 2017
@TaviTruman
Copy link

For those interested in OpenID Connect and OAuth 2 Authentication layered a top OData server endpoint I have forked the code and am working to add support for Client Credentials Grant and Authorization Code Grant workflows.

@fartwhif
Copy link

a work-around for some may be to set up an IIS website, save and copy the $metadata.xml file to it, and put this in the web config:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<staticContent>
<mimeMap fileExtension="." mimeType="text/xml" />
</staticContent>
</system.webServer>
</configuration>

and then use something like this in the proxy class generator:
http://localhost:654/$metadata

This worked for a Navision web service that requires basic authentication.

@unchase
Copy link

unchase commented Jul 21, 2019

Or you can try Unchase OData ConnectedService with login and password network credentials for endpoint (including web proxy credentials).

@fartwhif
Copy link

fartwhif commented Sep 14, 2019

you know i did end up using unchase, was the only tool that actually worked, Microsoft SMH

edit: I still had to download the metadata file and point unchase at it, but its main function actually works and you can choose a file, making it the first usable tool i've found.

@unchase
Copy link

unchase commented Sep 14, 2019

@fartwhif, thanks for your feedback.
You can offer your wishes for improving the Unchase OData Connected Service at the following link.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants