Quantcast
Channel: SharePoint 2013 - General Discussions and Questions forum
Viewing all articles
Browse latest Browse all 26374

NotSupportedException: Do not know how to create outbound claims for app only identity

$
0
0

It's a SharePoint 2013 environment that we have been deploying custom solutions to.  The custom solutions are nothing out of the ordinary (custom content types, event receivers, SPD workflows, branding).  It has been running fine but we started to get the following errors nonstop if we start a SP 2013 workflow on the site collection (even a simple Log 'hello world' to the workflow history 2013 WF would get the log excited.  I mean, these 3 entries repeat themselves more than ten times every second.  The log file size goes through the roof of course.  In the meanwhile, the w3wp.exe for the web app that hosts the site and the w3wp.exe for the SecurityTokenService got very busy.

03/05/2013 22:16:01.79     w3wp.exe (0x1324)                           0x09B0    SharePoint Foundation             Application Authentication        aiv3l    High        Token request correlation id: '69b9f705-2e5d-347d-e50f-169ad59ad1af'.   
03/05/2013 22:16:01.81     w3wp.exe (0x1324)                           0x09B0    SharePoint Foundation            Application Authentication        agmxm    Exception     System.NotSupportedException: Do not know how to create outbound claims for app only identity     at Microsoft.SharePoint.IdentityModel.SPIdentityContext.<GetOutboundS2SClaims>d__6.MoveNext()     at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)     at Microsoft.SharePoint.IdentityModel.OAuth2.SPOAuth2SecurityTokenManager.IssueBearerTokenString(SPServiceContext serviceContext, SPSecurityTokenServiceConnectionInformation stsInfo, OAuth2EndpointIdentity endpointIdentity, SPOAuth2SecurityTokenType tokenType, IEnumerable`1 claims) StackTrace:  at onetnative.dll: (sig=6aba1f5f-ccc4-4590-af00-b8ffe7fe99a0|2|onetnative.pdb, offset=28BE6) at onetnative.dll: (offset=152A9)    
03/05/2013 22:16:01.81     w3wp.exe (0x1324)                           0x09B0    SharePoint Foundation            Unified Logging Service           c91s    Monitorable    Watson bucket parameters: Microsoft SharePoint Foundation 4, ULSException14, 269cd32d "sharepoint foundation", 0f001144 "15.0.4420.0", 1f65804a "microsoft.sharepoint", 0f001144 "15.0.4420.0", 506723c5 "sat sep 29 11:37:25 2012", 00017b0d "00017b0d", 0000004c "0000004c", 760a1423 "notsupportedexception", 0018c5cc "agmxm"    
03/05/2013 22:16:01.82     w3wp.exe (0x1324)                           0x1C30    SharePoint Foundation            Application Authentication        aiv3e    High        Self-issued token request for '00000005-0000-0000-c000-000000000000/usnbka245t:12290@f43119f3-adb7-4cd8-8e5a-4c08c305b230' succeeded.

After recycling the w3wp.exe, everything calms down.  I tried running 2013 workflow on another site collection in the same web app, they ran totally fine without any issues.  So the integration between the SP farm and Workflow Manager Host is fine.  It appears that the app identity in this very site collection is corrupted or something?  How do I delete/change/create a new app identity for the workflows in the site collection to use if that's the case?  The site collection has a lot of content that we need so I can't simply delete it and spin up a new one.

Any suggestions would be helpful. 


Viewing all articles
Browse latest Browse all 26374

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>