Can anyone help in migrating a ASP.NET 4.5.2 client to core 2.0

Question

0.00/5 (No votes)

See more:

Hello,

I have an Asp.Net 4.5.2 web application client that makes calls to a OAuth 2.0 application running on my server Core 2.0 website. It works without a problem.

The problem is when it returns from an authorization call to the server, it does not execute the return method specified in the redirect url.

When I take it through the Visual Studio 2017 debugger, the authorization string sent to the server is the same as when I run it in the .Net 4.5.2 version of the client.

When it returns from the server in the .Net 4.5.2 client, it executes a method.

When it returns from the server in the .Net Core 2.0 client, it does not executes that method. It just hangs up with no error message.

Is there anyone that can help me to migrate my web client from Asp.Net 4.5.2 to Asp.Net Core 2.0?

I would appreciate it if anyone can tell me how to find out what the server is returning to the client. I can't figure out how to do that. If I knew that, I might be able to know what is causing the hangup.

Thanks,
Tony

What I have tried:

I have read numerous documents, some more than once, on OAuth 2.0 and Routing and other technologies related to the client side.

I created the client application in C#, Core 2.0 code, but cannot get it to work the way the .Net 4.5.2 client does.

Posted 16-Jun-18 6:30am

Tony Girgenti

Updated 18-Jun-18 4:14am

v4

Add a Solution

Comments

[no name] 16-Jun-18 13:19pm

Could it be that you forgot to describe what the problem is?

Tony Girgenti 16-Jun-18 13:56pm

The problem is when it returns from an authorization call to the server, it does not execute the return method specified in the redirect url.

When I take it through the Visual Studio 2017 debugger, the authorization string sent to the server is the same as when I run it in the .Net 4.5.2 version of the client.

When it returns from the server in the .Net 4.5.2 client, it executes a method.

When it returns from the server in the .Net Core 2.0 client, it does not executes that method. It just hangs up with no error message.

Thanks,
Tony

[no name] 16-Jun-18 14:10pm

Ok, please use "Improve question" and add this there. It would help others to help you ;)

Afzaal Ahmad Zeeshan 16-Jun-18 13:30pm

What is the problem?

Tony Girgenti 16-Jun-18 14:13pm

The problem is when it returns from an authorization call to the server, it does not execute the return method specified in the redirect url.

When I take it through the Visual Studio 2017 debugger, the authorization string sent to the server is the same as when I run it in the .Net 4.5.2 version of the client.

When it returns from the server in the .Net 4.5.2 client, it executes a method.

When it returns from the server in the .Net Core 2.0 client, it does not executes that method. It just hangs up with no error message.

2 solutions

Solution 1

Read the following : Authenticate with OAuth 2.0 in ASP.NET Core 2.0 • Jerrie Pelser's Blog[^]

Posted 16-Jun-18 21:41pm

Mehdi Gholam

Comments

Tony Girgenti 17-Jun-18 9:03am

Hello,

Yes, I did read that several times. Although it contains a good explanation of the OAuth flow, I don't see anything in there related to my problem of not executing the method in the redirect Url.

Thanks,
Tony

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Tony Girgenti · Accepted Answer · 2018-06-18T04:15:00

Solution 2

To fix this issue, I added this route to the Startup.cs file:

C#

routes.MapRoute(
   name: "token",
   template: "token",
   defaults: new { controller = "API", action = "GetAccessToken" });

Posted 18-Jun-18 4:15am

Tony Girgenti