久久久久久久av_日韩在线中文_看一级毛片视频_日本精品二区_成人深夜福利视频_武道仙尊动漫在线观看

在 .net core 3.1.1 Web 應用程序中更改 AzureAD 身份驗

Change redirectURI and CallbackPath for AzureAD authentication in .net core 3.1.1 web app(在 .net core 3.1.1 Web 應用程序中更改 AzureAD 身份驗證的 redirectURI 和 CallbackPath)
本文介紹了在 .net core 3.1.1 Web 應用程序中更改 AzureAD 身份驗證的 redirectURI 和 CallbackPath的處理方法,對大家解決問題具有一定的參考價值,需要的朋友們下面隨著小編來一起學習吧!

問題描述

限時送ChatGPT賬號..

我使用 Razor Pages 框架創建了一個新的 .net core 3.1.1 Web 應用程序.創建應用程序時,我將默認身份驗證設置為 AzureAd.當我運行應用程序時,身份驗證工作得很好.生成的 appsettings 文件如下所示:

I created a new .net core 3.1.1 web application with the Razor Pages framework. When creating the app I set up the default Authentication as AzureAd. When I run the application the authentication works just fine. The generated appsettings file looks like this:

{
  "AzureAd": {
    "Instance": "https://login.microsoftonline.com/",
    "Domain": "myDomain",
    "TenantId": "myTenantId",
    "ClientId": "myClientId",
    "CallbackPath": "/signin-oidc"
  },
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft": "Warning",
      "Microsoft.Hosting.Lifetime": "Information"
    }
  },
  "AllowedHosts": "*"
}

我在我的應用中創建了一個新控制器,看起來非常簡單,就像:

I created a new controller in my app which looks very simple, just like:

namespace WebApplication1.Controllers
{
    public class AccountController : Controller
    {
        [HttpGet]
        public void SignIn()
        {
           //here comes the logic which checks in what role is the logged User
           //the role management stuff will be implemented in the app
        }
    }
}

這就是我的 Startup.cs 的樣子:

This is how my Startup.cs looks like:

public class Startup
{
    public Startup(IConfiguration configuration)
    {
        Configuration = configuration;
    }

    public IConfiguration Configuration { get; }

    // This method gets called by the runtime. Use this method to add services to the container.
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddAuthentication(AzureADDefaults.AuthenticationScheme)
            .AddAzureAD(options => Configuration.Bind("AzureAd", options));
        services.AddMvc(options =>
        {
            options.EnableEndpointRouting = false;
        });
        services.AddRazorPages().AddMvcOptions(options =>{});
    }

    // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
    public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
    {
        if (env.IsDevelopment())
        {
            app.UseDeveloperExceptionPage();
        }
        else
        {
            app.UseExceptionHandler("/Error");
            // The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
            app.UseHsts();
        }

        app.UseHttpsRedirection();
        app.UseStaticFiles();

        app.UseRouting();

        app.UseAuthentication();
        app.UseAuthorization();

        app.UseEndpoints(endpoints =>
        {
            endpoints.MapRazorPages();
            endpoints.MapControllers();
        });

        app.UseMvc(routes =>
       {
            routes.MapRoute(
            name: "default",
            template: "{controller=Account}/{action=SignIn}");
       });
    }
}

我希望能夠將 AzureAd/CallbackPath 更改為不同于/signin-oidc"的內容,例如.我想將其更改為帳戶/登錄.然后我想從 azure 捕獲回調調用,并根據記錄的用戶電子郵件地址修改令牌以添加一些系統角色并根據用戶角色重定向到適當的儀表板頁面.管理員和客戶可以有不同的儀表板.

I'd would like to be able to change the AzureAd/CallbackPath to something different than "/signin-oidc" eg. I would like to change it to Account/SignIn. Then I'd like to catch the callback call from azure and based on the logged user email address I'd like to modify the token to add some system roles and make a redirect to the appropriate dashboard page based on the user role. There can be a different dashboard for admin and a client.

所以我嘗試更改 "CallbackPath": "/Account/SignIn" 并且我還更新了 Azure 中的 RedirectURI:

So I tried to change the "CallbackPath": "/Account/SignIn" and I also updated RedirectURI in Azure:

然后我再次運行應用程序,在 void SignIn() 中設置斷點,我再次登錄,而不是點擊 /Account/SignIn 我剛剛被重定向到主頁,https://localhost:44321.我還嘗試在瀏覽器中手動運行 https://localhost:44321/Account/SignIn 并看到以下錯誤消息:

Then I run the app once again, set a breakpoint in void SignIn(), I signed in once again, and instead of hitting the /Account/SignIn I was just redirected to the main page, the https://localhost:44321. I also tried to manually run the https://localhost:44321/Account/SignIn in the browser and I saw the following error message:

An unhandled exception occurred while processing the request.
Exception: OpenIdConnectAuthenticationHandler: message.State is null or empty.

我試圖檢查 documentation 但我沒有發現任何有用的東西.關于我應該怎么做才能讓它發揮作用的任何想法?干杯

I tried to check if there is something in the documentation but I didn't find anything useful. Any ideas about what should I do to make it work? Cheers

我也使用 Microsoft.AspNetCore.Authentication.AzureAD.UI 框架.

推薦答案

CallbackPath 是服務器在認證過程中重定向的路徑.它由 OIDC 中間件本身自動處理,這意味著我們無法通過創建新的控制器/動作并將 CallbackPath 設置為它來控制邏輯.大致流程如下:

The CallbackPath is the path where server will redirect during authentication. It's automatically handled by the OIDC middleware itself, that means we can't control the logic by creating a new controller/action and set CallbackPath to it . Below is the general process :

在身份驗證過程中,整個過程由 OpenID Connect 中間件控制,用戶在 Azure 的登錄頁面驗證憑據后,Azure Ad 會將用戶重定向回 OIDC 配置中設置的應用程序重定向 url,以便您獲得授權代碼(如果使用代碼流)并完成身份驗證過程.身份驗證后,用戶將被重定向到重定向 url.

During authentication , the whole process is controlled by OpenID Connect middleware , after user validate credential in Azure's login page ,Azure Ad will redirect user back to your application's redirect url which is set in OIDC's configuration , so that you can get the authorization code(if using code flow) and complete the authentication process . After authentication , user will then be redirected to the redirect url .

基于登錄的用戶電子郵件地址,我想修改令牌以添加一些系統角色并根據用戶角色重定向到相應的儀表板頁面.管理員和客戶可以有不同的儀表板.

based on the logged user email address I'd like to modify the token to add some system roles and make a redirect to the appropriate dashboard page based on the user role. There can be a different dashboard for admin and a client.

第一件事是你不能修改令牌,你不需要修改它.

The first thing is you can't modify the token and you don't need to modify that .

您可以在 OIDC OWIN 中間件中使用通知事件,該中間件調用以啟用開發人員對身份驗證過程的控制.OnTokenValidated 為您提供了修改從傳入令牌獲得的 ClaimsIdentity 的機會,您可以根據本地數據庫中的用戶 id 查詢用戶的角色并添加到用戶的聲明中:

You can use notification events in OIDC OWIN Middlerware which invokes to enable developer control over the authentication process . OnTokenValidated offers you the chance to modify the ClaimsIdentity obtained from the incoming token , you can query user's role based on user's id from local database and add to user's claims :

 services.AddAuthentication(AzureADDefaults.AuthenticationScheme)
            .AddAzureAD(options => Configuration.Bind("AzureAd", options));


services.Configure<OpenIdConnectOptions>(AzureADDefaults.OpenIdScheme, options =>
{
    options.Events = new OpenIdConnectEvents
    {
        OnTokenValidated = ctx =>
        {
            //query the database to get the role

            // add claims
            var claims = new List<Claim>
            {
                new Claim(ClaimTypes.Role, "Admin")
            };
            var appIdentity = new ClaimsIdentity(claims);

            ctx.Principal.AddIdentity(appIdentity);

            return Task.CompletedTask;
        },
    };
});

然后在控制器中,您可以獲得如下聲明:

Then in controller , you can get the claim like :

var role = User.Claims.FirstOrDefault(c => c.Type == ClaimTypes.Role)?.Value;

然后您可以根據特定聲明過濾操作.

Then you can filter the actions based on specific claim .

如果您想在身份驗證后將用戶重定向到特定的路由/頁面,請將 url 放入 AuthenticationProperties :

If you want to redirect user to specific route/page after authentication , put the url to AuthenticationProperties :

if (!User.Identity.IsAuthenticated)
{
    return Challenge(new AuthenticationProperties() { RedirectUri = "/home/redirectOnRole" } , AzureADDefaults.AuthenticationScheme);
}  

在該路徑中,您可以根據用戶的角色重定向用戶.

And in that path , you can redirect user based on user's role .

這篇關于在 .net core 3.1.1 Web 應用程序中更改 AzureAD 身份驗證的 redirectURI 和 CallbackPath的文章就介紹到這了,希望我們推薦的答案對大家有所幫助,也希望大家多多支持html5模板網!

【網站聲明】本站部分內容來源于互聯網,旨在幫助大家更快的解決問題,如果有圖片或者內容侵犯了您的權益,請聯系我們刪除處理,感謝您的支持!

相關文檔推薦

ASP.NET Core authenticating with Azure Active Directory and persisting custom Claims across requests(ASP.NET Core 使用 Azure Active Directory 進行身份驗證并跨請求保留自定義聲明)
ASP.NET Core 2.0 Web API Azure Ad v2 Token Authorization not working(ASP.NET Core 2.0 Web API Azure Ad v2 令牌授權不起作用)
ASP Core Azure Active Directory Login use roles(ASP Core Azure Active Directory 登錄使用角色)
How do I get Azure AD OAuth2 Access Token and Refresh token for Daemon or Server to C# ASP.NET Web API(如何獲取守護進程或服務器到 C# ASP.NET Web API 的 Azure AD OAuth2 訪問令牌和刷新令牌) - IT屋-程序員軟件開發技
.Net Core 2.0 - Get AAD access token to use with Microsoft Graph(.Net Core 2.0 - 獲取 AAD 訪問令牌以與 Microsoft Graph 一起使用)
Azure KeyVault Active Directory AcquireTokenAsync timeout when called asynchronously(異步調用時 Azure KeyVault Active Directory AcquireTokenAsync 超時)
主站蜘蛛池模板: 国产1区2区在线观看 | 国产电影一区二区在线观看 | 中文字幕精品一区二区三区精品 | 日韩在线小视频 | 日本不卡一区二区三区在线观看 | 精品国产乱码久久久久久久久 | 久久99精品久久久久久 | 久久综合狠狠综合久久综合88 | 99热播精品| 国产 欧美 日韩 一区 | 自拍偷拍第一页 | 亚洲第一黄色网 | 五月婷婷激情网 | 亚洲国产精品久久久久婷婷老年 | 黄色在线免费看 | 欧美日韩精品在线免费观看 | 国产午夜一级 | 99精品欧美一区二区三区综合在线 | 国产精品国产精品国产专区不卡 | 精品久久久久久久 | 日韩欧美中文 | 日韩区 | www.国产精品| 五月天婷婷久久 | 精品在线播放 | av毛片| 成人黄视频在线观看 | 亚洲精品久久久久久一区二区 | 91久久精品国产91久久 | 国产精品久久久久无码av | 亚洲成人在线视频播放 | 99热激情 | 欧美激情一区二区 | 亚洲欧洲成人av每日更新 | 久久伊人精品 | 欧美日韩成人在线 | 国产成人精品一区二区三区网站观看 | 日韩av福利在线观看 | 中文字幕一区二区三区四区不卡 | 综合久| 做a网站|