Third party oidc authentication with SPSE failed
Following the new https://docs.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/oidc-1-0-authentication , I managed configuring oidc authenticate in SPSE with ADFS. I then tried third party oidc authentication in SPSE with Keycloak, but failed with following errors : 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Monitoring nasq Medium Entering Monitored Scope (Request (POST:https://teamse1/_layouts/15/Authenticate.aspx?Source=%252F)). Parent=None 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:https://teamse1/_layouts/15/Authenticate.aspx?Source=%252F) 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwhz Medium SPRequestModule.BeginRequestHandler End, SP Build Version: '16.0.14326.20450' 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brd4 Medium SPContextCookie : Using full host domain for cookie. CookieName: 'nSGt'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brdr Medium SPCryptoContextCookie : Initial Secondary certificate is null and we did not receive a secondary certificate thumbprint. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brc8 Medium SPNonceCookie : The Identifier is set successfully. Identifier: '', NonceToSendToIdentityProvider: '2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A-CB0F14DA2F6FF1E6302B9120B3FDACE0CE6B228FA26DC9915A3264E4EEF4FA74'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication 9w647 Medium Using input cookie name. CookieName: 'nSGt-2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brbv Medium SPNonceCookie : Successfully read nonce cookie. Version: '0', Seed: '94DC58B58F1B35EFF01163B1124CC9539C338C80D3829F09', Identifier: '2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brc8 Medium SPNonceCookie : The Identifier is set successfully. Identifier: '2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A', NonceToSendToIdentityProvider: '2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A-CB0F14DA2F6FF1E6302B9120B3FDACE0CE6B228FA26DC9915A3264E4EEF4FA74'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication 9w647 Medium Using input cookie name. CookieName: 'nSGt-2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Authentication Authorization deffe Medium The browser does support SameSite at revision 3 of RFC6265. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brbj Medium SPNonceCookie : Deleted nonce cookie if present. Identifier: '2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Security Token Handler 8p0r7 Medium Audience GUID matches trusted login provider default client identifier. Audience: 'new-sharepoint', provider Default Identifier: 'new-sharepoint', provider Uri: ''. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Topology aeayb Medium SecurityTokenServiceSendRequest: RemoteAddress: 'http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc' Channel: 'System.ServiceModel.Security.IWSTrustChannelContract' Action: 'http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue' MessageId: 'urn:uuid:8ed01142-6684-422a-8d99-6028560b88a0' 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Topology aeax9 Medium SecurityTokenServiceReceiveRequest: LocalAddress: 'http://spdev-se1.:32843/SecurityTokenServiceApplication/securitytoken.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue' MessageId: 'urn:uuid:8ed01142-6684-422a-8d99-6028560b88a0' 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Monitoring nasq Medium Entering Monitored Scope (ExecuteSecurityTokenServiceOperationServer). Parent=None 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Security Token Service 9w6kv Medium STS Call: Creating Claims Operations Scope for Applies To Uri: 'https://teamse1/'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Claims Authentication a6oo7 Medium Created claims operation context from uri. ContextUri: 'https://teamse1/', Source: 'SiteWithoutSiteSubscription'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Security Token Service 9w6k3 Medium Creating SPSecurityTokenRequestContextV2 object for security token service Issue request. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Security Token Service 9w6k0 Monitorable STS Call: Failed to issue new security token. Exception: 'System.IdentityModel.Tokens.SecurityTokenException: Validate signature failure : no found matched security key for token signature. 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateSignature(String token, TokenValidationParameters validationParameters) 在 System.IdentityModel.Tokens.JwtSecurityTokenHandler.ValidateToken(String securityToken, TokenValidationParameters validationParameters, SecurityToken& validatedToken) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(String tokenString, TokenValidationParameters validationParameters, SecurityToken& token) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(SecurityToken token) 在 Microsoft.SharePoint.IdentityModel.SPSecurityTokenRequestContextV2..ctor(ClaimsIdentity identity, RequestSecurityToken request, Boolean initializeForActor, SPSecurityTokenRequestTypeV2 overrideRequestType) 在 Microsoft.SharePoint.IdentityModel.SPSecurityTokenServiceV2.Issue(ClaimsPrincipal principal, RequestSecurityToken request)'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope: (ExecuteSecurityTokenServiceOperationServer) 执行时间=3.7961; CPU Milliseconds=3; SQL 查询计数=0; Parent=None 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Security Token Service Caller btgia High SPSecurityContext: Request for security token failed with exception. Exception: 'System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Validate signature failure : no found matched security key for token signature. (错误详细信息等于 很可能由 IncludeExceptionDetailInFaults=true 创建的 ExceptionDetail，其值为: System.IdentityModel.Tokens.SecurityTokenException: Validate signature failure : no found matched security key for token signature. 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateSignature(String token, TokenValidationParameters validationParameters) 在 System.IdentityModel.Tokens.JwtSecurityTokenHandler.ValidateToken(String securityToken, TokenValidationParameters validationParameters, SecurityToken& validatedToken) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(String tokenString, TokenValidationParameters validationParameters, SecurityToken& token) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(SecurityToken token) 在 Microsoft.SharePoint.IdentityModel.SPSecurityTokenRequestContextV2..ctor(ClaimsIdentity identity, RequestSecurityToken request, Boolean initializeForActor, SPSecurityTokenRequestTypeV2 overrideRequestType) ...)。'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication 8306 Critical An exception occurred when trying to issue security token: Validate signature failure : no found matched security key for token signature.. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication 9w636 Unexpected Claims Saml Sign-In: Could not get local token for trusted third party token. FaultException: 'System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Validate signature failure : no found matched security key for token signature. (错误详细信息等于 很可能由 IncludeExceptionDetailInFaults=true 创建的 ExceptionDetail，其值为: System.IdentityModel.Tokens.SecurityTokenException: Validate signature failure : no found matched security key for token signature. 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateSignature(String token, TokenValidationParameters validationParameters) 在 System.IdentityModel.Tokens.JwtSecurityTokenHandler.ValidateToken(String securityToken, TokenValidationParameters validationParameters, SecurityToken& validatedToken) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(String tokenString, TokenValidationParameters validationParameters, SecurityToken& token) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(SecurityToken token) 在 Microsoft.SharePoint.IdentityModel.SPSecurityTokenRequestContextV2..ctor(ClaimsIdentity identity, RequestSecurityToken request, Boolean initializeForActor, SPSecurityTokenRequestTypeV2 overrideRequestType) ...)。'. Stack: ' 在 System.ServiceModel.Security.WSTrustChannel.ReadResponse(Message response) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForOnBehalfOfContext(Uri context, SecurityToken onBehalfOf) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.ExchangeArgumentTrustedThirdPartySessionSecurityTokenFo... 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09* w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication 9w636 Unexpected ...rLocalToken(SecurityToken thirdPartyToken, SessionSecurityTokenCreatedEventArgs arguments)'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwhw Medium SPRequestModule.ErrorAppHandler Begin 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation General 8nca Medium Application error when access /_layouts/15/Authenticate.aspx, Error=Validate signature failure : no found matched security key for token signature. 在 System.ServiceModel.Security.WSTrustChannel.ReadResponse(Message response) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForOnBehalfOfContext(Uri context, SecurityToken onBehalfOf) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.ExchangeArgumentTrustedThirdPartySessionSecurityTokenForLocalToken(SecurityToken thirdPartyToken, SessionSecurityTokenCreatedEventArgs arguments) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.OnSessionSecurityTokenCreated(SessionSecurityTokenCreatedEventArgs eventArgs) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.SetPrincipalAndWriteSessionToken(SessionSecurityToken sessionToken, Boolean isSession) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequestBase request) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.OnAuthenticateRequest(Object sender, EventArgs eventArgs) 在 System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 在 System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) 在 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Runtime tkau Unexpected System.ServiceModel.FaultException`1[[System.ServiceModel.ExceptionDetail, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]: Validate signature failure : no found matched security key for token signature. 在 System.ServiceModel.Security.WSTrustChannel.ReadResponse(Message response) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForOnBehalfOfContext(Uri context, SecurityToken onBehalfOf) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.ExchangeArgumentTrustedThirdPartySessionSecurityTokenForLocalToken(SecurityToken thirdPartyToken, SessionSecurityTokenCreatedEventArgs arguments) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.OnSessionSecurityTokenCreated(SessionSecurityTokenCreatedEventArgs eventArgs) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.SetPrincipalAndWriteSessionToken(SessionSecurityToken sessionToken, Boolean isSession) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequestBase request) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.OnAuthenticateRequest(Object sender, EventArgs eventArgs) 在 System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 在 System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) 在 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously... 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09* w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Runtime tkau Unexpected ...) 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Validate signature failure : no found matched security key for token signature. (错误详细信息等于 很可能由 IncludeExceptionDetailInFaults=true 创建的 ExceptionDetail，其值为: System.IdentityModel.Tokens.SecurityTokenException: Validate signature failure : no found matched security key for token signature. 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateSignature(String token, TokenValidationParameters validationParameters) 在 System.IdentityModel.Tokens.JwtSecurityTokenHandler.ValidateToken(String securityToken, TokenValidationParameters validationParameters, SecurityToken& validatedToken) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(String tokenString, TokenValidationParameters validationParameters, SecurityToken& token) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(SecurityToken token) 在 Microsoft.SharePoint.IdentityModel.SPSecurityTokenRequestContextV2..ctor(ClaimsIdentity identity, RequestSecurityToken request, Boolean initializeForActor, SPSecurityTokenRequestTypeV2 overrideRequestType) ...)。 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation General aat87 Monitorable 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=False, UserIdentityName=, ClaimsCount=0 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation General agxkz High calling GetCurrentGenericSetupPath for a versioned path: TEMPLATE\LAYOUTS 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Application Authentication 9s97c Medium SPApplicationAuthenticationModuleV2.IsBearerChallengeRequested: Return 'False'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Application Authentication 9s97n Medium The request isn't made to a page which allows NeverAuth to be specified in the query string 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication crpqx Medium STS setting for SuppressModernAuthForOfficeClients:'True'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Application Authentication 9s976 Medium IsClaimsTrustedAuthenticationOnly: 'False', IsOfficeClientIDCRLRequest: 'False', HasSPTrustedSecurityTokenIssuer: 'False', ForceIdcrlForOfficeClients: 'True'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwh5 Medium SPRequestModule.PreSendRequestHeaders End 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwhx Medium SPRequestModule.ErrorAppHandler End 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwia Medium SPRequestModule.PostLogRequestHandler Begin 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwib Medium SPRequestModule.PostLogRequestHandler End 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwic Medium SPRequestModule.EndRequestHandler Begin 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 avwhy,0 nasq,0 avwhz,0 9brd4,0 9brdr,0 9brc8,0 9w647,0 9brbv,0 9brc8,0 9w647,0 deffe,0 9brbj,2 8p0r7,0 aeayb,11 btgia,0 9w636,0 avwhw,0 8nca,0 tkau,0 ajlz0,1 aat87,5 agb9s,0 agxkz,1 9s97c,0 9s97n,0 crpqx,0 9s976,0 avwh5,0 avwhx,0 avwia,0 avwib,0 avwic 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Runtime aoxsq Medium Sending HTTP response 200 for HTTP POST request 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Unified Audit bm7sm High SPRequestModule::CreatePageViewedAuditEntry: Required parameters not set properly,exiting creating PageViewed SPUnifiedAuditEntry 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope: (Request (POST:https://teamse1/_layouts/15/Authenticate.aspx?Source=%252F)) 执行时间=29.1365; CPU Milliseconds=18; SQL 查询计数=0; Parent=None 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwid Medium SPRequestModule.EndRequestHandler End 28bc00a0-1979-300a-3da4-d9c46cbf4124 Through browser F12 debug, the authentication flow had successfully gone from Keycloak to Sharepoint : _layouts/15/Authenticate.aspx?Source=%2F, and id_token successfully generated and could be verified through https://jwt.ms/ How to integrate 3rd party oidc server with SPSE?
Modern webparts in SharePoint Server subscription Edition?
I would like to know, when it is planned to close as much as possible the gap between OnPrem and Online in terms of webparts? When we expect some modern webparts? In few month? Half year? I appreciate some of the admin features, but what about improvements for users? wbaer any thoughts on this? Customers are really asking for. Thx
SPFx Version
Hi everybody, in our company we use SharePoint online and SPSSE onpremise. At the current state they support SPFx version 1.15.2 and 1.4.1. This causes some problems: Entire development process is unnecessarily complicated Each developer needs different node.js version or tricky workarounds (NVM Manager, multiple VMS, ...) Constantly switching react/typescript version Code quality/audit/dependency checks are not possible on onpremise due it's very old framework version (2018) We can't use PnP libraries in it's glory (example: have to use old peoplepicker-control, workaround to run pnpjs, ...) We can't use most of the community webparts for on-premise (example: https://github.com/pnp/sp-dev-fx-webparts/tree/main/samples) or we have to use a old/buggy version The same technical requirement must be implemented differently, because controls didn't exists onpremise or working differently For the reasons mentioned, we continue to develop server-side components for on-premises and do not use the SPFx framework at all (for on-premise). Developing with an old framework version (almost 5 years) is generally bad practice. We wouldn't do that with any other framework either. Please consider making SPFX updates and provide a basic roadmap, best regardsSP Server 2016 Custom Font
I am trying to install a custom font into a site and I can't for the life of me figure out what is wrong. I am using SharePoint Designer to modify an existing SPFONT file and uploading it to the correct location in the ...theme/15 folder location with all the other SPFONT files. It will not show in the Change the look font selection. I have successfully loaded Arialbut this one requiresme to supply all the font files since it is not a common font. Here is part of my SPFON <?xml version="1.0" encoding="utf-8"?> <s:fontScheme name="Replica" previewSlot1="title" previewSlot2="body" xmlns:s="http://schemas.microsoft.com/sharepoint/"> <s:fontSlots> <s:fontSlot name="title"> <s:latin typeface="ReplicaRegular" eotsrc="https://MySharepointSite.com/sites/hr/_catalogs/theme/15/ReplicaStdRegular.eot" woffsrc="https://MySharepointSite.com/sites/hr/_catalogs/theme/15/ReplicaStdRegular.woff" tfsrc="https://MySharepointSite.com/sites/hr/_catalogs/theme/15/ReplicaStdRegular.ttf" svgsrc="https://MySharepointSite.com/sites/hr/_catalogs/theme/15/ReplicaStdRegular.svg" largesrc="https://MySharepointSite.com/sites/hr/_catalogs/theme/15/ReplicaLrg.png" smallsrc="https://MySharepointSite.com/sites/hr/_catalogs/theme/15/ReplicaSml.png" /> <s:ea typeface=""/> <s:cs typeface="Segoe UI Light" /> <s:font script="Arab" typeface="Tahoma" /> <s:font script="Deva" typeface="Mangal" /> <s:font script="Grek" typeface="Segoe UI Light" /> <s:font script="Hang" typeface="Malgun Gothic" /> <s:font script="Hans" typeface="Microsoft YaHei" /> <s:font script="Hant" typeface="Microsoft JhengHei" /> <s:font script="Hebr" typeface="Tahoma" /> <s:font script="Hira" typeface="Meiryo" /> <s:font script="Thai" typeface="Tahoma" /> <s:font script="Armn" typeface="Tahoma" /> <s:font script="Beng" typeface="Vrinda" /> <s:font script="Cher" typeface="Plantagenet Cherokee" /> <s:font script="Ethi" typeface="Nyala" /> <s:font script="Geor" typeface="Sylfaen" /> <s:font script="Gujr" typeface="Shruti" /> <s:font script="Guru" typeface="Raavi" /> <s:font script="Knda" typeface="Tunga" /> <s:font script="Khmr" typeface="DaunPenh" /> <s:font script="Laoo" typeface="DokChampa" /> <s:font script="Mlym" typeface="Kartika" /> <s:font script="Mymr" typeface="Myanmar Text" /> <s:font script="Orya" typeface="Kalinga" /> <s:font script="Sinh" typeface="Iskoola Pota" /> <s:font script="Syrc" typeface="Estrangelo Edessa" /> <s:font script="Taml" typeface="Latha" /> <s:font script="Telu" typeface="Gautami" /> <s:font script="Thaa" typeface="MV Boli" /> <s:font script="Tibt" typeface="Cordia New" /> <s:font script="Yiii" typeface="Microsoft Yi Baiti" /> </s:fontSlot> Any help to figure out why it isn't working. I was told that I couldn't use relative paths and I thought that was the case, but it still won't worlk. In SharePoint Designer I can CTRL+Click and the files open just fine in a browser. I have run out of options. Please do not tell me to use ShortPoint. I'm not a Farm Admin and they told me they won't install the solution. 😞
New features?
Hi, I've installed Sharepoint Server Subscription Edition, but I've not managed to find anything new in regards to the gui. I was hoping we would get some of the more useful features that Sharepoint Online have which Sharepoint2019 didn't, like formatting options for list views, more webparts or better support for PowershellPNPs classic page upgrades. Can we expect any upgrades to the modern page features in Sharepoint Server Subscription Edition compared to Sharepoint 2019?
Feature Roadmap, SP2010 workflow in particular
Any chance we can get some confirmation of the roadmap for old SP2010 workflows? SP2010 workflow is still present in the preview SPSE installation, but how long is this going to be around? It has already been deprecated from SPOnline what's the strategy for SPSE? For customers with solutions based on old versions of things like Nintex or SPD workflows based on SP2010, they'll need to know when they're going to have to make the jump to something more current and deal with the redevelopment.
SharePoint subscription edition -- sql authentication
I have been working with SharePoint for the better part of 15 years. During that time, I almost always installed SharePoint in a domain environment where the Application Server(s) and Database Server(s) were within the same AD domain. I am increasingly seeing use cases where SharePoint could/should be in a DMZ and simply having SharePoint utilise a SQL server cluster (deployed in a different domain, for example). Historically Microsoft's support for SharePoint services to authenticate to SQL utilising SQL authentication has not been very well documented. The "support" was typically limited to a subset of services (e.g. a Content DB). And the wider SharePoint farm (and services) still needed to be deployed within the same domain at the SQL server. Can you point me to some documentation/article that outlines how to install SharePoint Subscription Edition where all of SharePoint is authenticating to its SQL backend using SQL Authentication (rather than Windows authentication)? Does anyone have any experience doing this and stories/lessons you can share?
SharePoint Subscription Edition and Remote Share Provider, new RBS provider
Hello, everybody, I wanted to try the new RBS provider "Remote Share Provider", I follow the article https://learn.microsoft.com/en-us/sharepoint/administration/remote-share-provider, but it fails me when I register in Sharepoint on the message that I need the Enterprise edition of SQL. Seriously? I deployed RBS for SP2016 on SQL Standard edition, and it gets up and running. There are no articles on this yet, other than the few official ones that seem inaccurate or unclear to me. Does anyone have any practical experience with installing and getting this Remote Share Provider up and running to share with the community? Thanks in advance PavelWebDav on SharePoint Subscription Edition
Hi Community, I'm currently planning a migration from an old SharePoint 2016 On-Premises environment to M365, as well as moving some content to a new SharePoint Subscription Edition farm that will be operational for a few years. My question is: Does anyone have a confirmed, official source stating that WebDav is still supported as of now? Ideally, I'm looking for any official information regarding the future of its support. I understand that WebDav might not be the protocol of the future, but we still have some use cases that need to run for another year or so. Therefore, I want to ensure we can migrate these without concerns, or if we should start planning for alternatives. Thanks in advance for your help!
Configuring SharePoint SE to trust third party OIDC authentication.
I am following this article to configure SharePoint SE to trust Login.gov OIDC 1.0 authentication. https://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/set-up-oidc-auth-in-sharepoint-server-with-msaad Following Step 3 to configure using metadata endpoint failed with the error: New-SPTrustedIdentityTokenIssuer : The security token service metadata document could not be parsed. Can SPSE work with third-party Idp other than Microsoft Entra ID to use metadata endpoint? The public key of login.gov will be rotated annually, so configuring it manually by hard coding the public key is not a viable solution.
