Cannot run on localhost after deploying app registered with Azure

Binu THOMAS

Hi All,

I am new to the Azure app registration and SSO applications.

I have created an ASP.NET Web forms application with single sign on to MS365. Registered with Azure and published to a local server in company.

Now I cannot continue the development, when I run on localhost, after authentication, it is redirecting to the redirect url mentioned in the app registration for deployment.

I have given both localhost and live url in redirect url section.

how can I continue development/run on localhost without affecting deployment

Thanks in advance

6 Replies

Know the answer? Post it — somebody with the same question will find it here.

Binu THOMAS5y ago
Hi @Sachin Singh

I gave the local host address in web.config and in reply url in StartupAuth.cs

now i am getting the below error

AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application

both the url is mentioned in appregistration
Binu THOMAS5y ago
@Sachin Singh

yes i have mentioned both the url,
I followed the link you mentioned, its still the same.
Binu THOMAS5y ago
@Sachin Singh
I have included both the url as reply url
first one is live and second one is localhost
Sachin Singh5y ago
hii
@Thomas
have you included both urls (localhost and deployment) as replyUrl?
I will suggest you to have a look at this thread
https://stackoverflow.com/questions/52690775/azure-active-directory-application-registration-for-localhost-and-production
Binu THOMAS5y ago
@sachin Singh

i didnt mention any redirect url in startupauth.cs

PFB the default code.
private static string clientId = ConfigurationManager.AppSettings["ida:ClientId"];
private static string aadInstance = EnsureTrailingSlash(ConfigurationManager.AppSettings["ida:AADInstance"]);
private static string tenantId = ConfigurationManager.AppSettings["ida:TenantId"];
private static string postLogoutRedirectUri = ConfigurationManager.AppSettings["ida:PostLogoutRedirectUri"];
string authority = aadInstance + tenantId;
public void ConfigureAuth(IAppBuilder app)
{
app.SetDefaultSignInAsAuthenticationType(CookieAuthenticationDefaults.AuthenticationType);
app.UseCookieAuthentication(new CookieAuthenticationOptions());
app.UseOpenIdConnectAuthentication(
new OpenIdConnectAuthenticationOptions
{
ClientId = clientId,
Authority = authority,
PostLogoutRedirectUri = postLogoutRedirectUri,
Notifications = new OpenIdConnectAuthenticationNotifications()
{
AuthenticationFailed = (context) =>
{
return System.Threading.Tasks.Task.FromResult(0);
}
}
}
);
// This makes any middleware defined above this line run before the Authorization rule is applied in web.config
app.UseStageMarker(PipelineStage.Authenticate);
}
Sachin Singh5y ago
check the redirectURI in your startup.Auth.cs