Certificate error about identityserver2 HOT 6 CLOSED

Only users in the "IdentityServerUsers" role are able to request tokens. That might be error #1.

For the AntiCSRF error message - that is happening in your app - not IdSrv right?

from identityserver2.

I am also having the same problem, in regards to:

"A claim of type 'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier' or 'http://schemas.microsoft.com/accesscontrolservice/2010/07/claims/identityprovider'" ... I am beating my head . Any advice.

Thanks for all of your great work and tutorials. Once I get this stuff down, it will GREATLY help me on many projects where we have made custom solutions for this.

from identityserver2.

And I am asking the same question - where does this error occur? In IdSrv or in your application?

My assumption is that it is in your application - and the error message should be quite clear. You have to set a claim / claim pair that uniquely identifies the client for anti CSRF.

from identityserver2.

I'm sorry, I was being thick-headed. It was happening on my application and yes you were right , it was completely clear. 2 full-time jobs has my brain fizzling at some points in the day. Thanks for the kickstart, but this will not be the last you've heard from me! ;)

from identityserver2.

hi, i am also having same error. in orchard application.

public static MvcHtmlString AntiForgeryTokenOrchard(this HtmlHelper htmlHelper) {

        try {
            return htmlHelper.AntiForgeryToken(); // error

A claim of type 'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier' or

'http://schemas.microsoft.com/accesscontrolservice/2010/07/claims/identityprovider' was not present on the provided ClaimsIdentity. To enable anti-forgery token

support with claims-based authentication, please verify that the configured claims provider is providing both of these claims on the ClaimsIdentity instances it

generates. If the configured claims provider instead uses a different claim type as a unique identifier, it can be configured by setting the static property

AntiForgeryConfig.UniqueClaimTypeIdentifier.

please advice...

from identityserver2.

@sankarapandian18, here ya go: http://brockallen.com/2012/07/08/mvc-4-antiforgerytoken-and-claims/

from identityserver2.