C# 带Asp.Net Webforms的OWIN-未创建重定向URI侦听器
我正在尝试将Asp.NETWebForms应用程序与SSO身份验证结合起来,使用pingFederate和Kerberos。除了两件事外,一切似乎都正常:C# 带Asp.Net Webforms的OWIN-未创建重定向URI侦听器,c#,asp.net,owin,C#,Asp.net,Owin,我正在尝试将Asp.NETWebForms应用程序与SSO身份验证结合起来,使用pingFederate和Kerberos。除了两件事外,一切似乎都正常: 未创建重定向URI侦听器。由于缺少/无效URI,它无法访问令牌处理代码。用户只看到一个404错误 它使其与事件中接收到的AuthorizationCode保持一致,但到达时上下文身份验证票证为空 私有只读字符串_redirectUri=ConfigurationManager.AppSettings[“okta:redirectUri”
私有只读字符串_redirectUri=ConfigurationManager.AppSettings[“okta:redirectUri”];
app.UseOpenIdConnectAuthentication(新的OpenIdConnectAuthenticationOptions
{
AuthenticationMode=AuthenticationMode.Active,
ClientId=_ClientId,
ClientSecret=\u ClientSecret,
权威=_权威,
重定向URI=\u重定向URI,
ResponseType=OpenIdConnectResponseType.Code,
Scope=OpenIdConnectScope.OpenIdProfile,
TokenValidationParameters=新的TokenValidationParameters{NameClaimType=“name”},
通知=新的OpenIdConnectAuthenticationNotifications
有人知道RedirectURI目的地是如何构建的,或者它是否在vanilla ASP.NET上受支持吗?我看到它是为MVC应用程序自动生成的
<add key="okta:RedirectUri" value="http://localhost:44359/authorization-code/callback/" />
private readonly string _redirectUri = ConfigurationManager.AppSettings["okta:RedirectUri"];
app.UseOpenIdConnectAuthentication(new OpenIdConnectAuthenticationOptions
{
AuthenticationMode = AuthenticationMode.Active,
ClientId = _clientId,
ClientSecret = _clientSecret,
Authority = _authority,
RedirectUri = _redirectUri,
ResponseType = OpenIdConnectResponseType.Code,
Scope = OpenIdConnectScope.OpenIdProfile,
TokenValidationParameters = new TokenValidationParameters { NameClaimType = "name" },
Notifications = new OpenIdConnectAuthenticationNotifications