Identityserver4: No claim types requested

[ravetroll]

I have just upgraded my Host from beta5 to RTM. I also moved my persistence from the TwentyTwenty EF to the IdentityServer one. This involved making the change from Scopes to ApiResources and IdentityResources. Its all gone smoothly and I have implemented the IResourceStore, IClientStore, IProfileService. I have set up my Identity Resources with the identity scope names (openid, profile) and I am able to log into my client using my Host, BUT ONLY if I add a claim to any one of my Identity Resources. If there is no claim in any Identity Resource then I get the error 'No claim types requested' which is thrown from the constructor of ProfileDataRequestContext. Why is it a problem if I don't have any Identity Resource claims. If I add any random value as a Identity Resource Claim, the authentication works perfectly and I get my identity and access tokens and my claims like sub and email and the like. Is there something I have failed to do?

[brockallen]

Can you show the identity resources config? Why are you modeling an identity resource without a user claim?

[ravetroll]

IdentityResources

Id  Description DisplayName Emphasize   Enabled Name    Required    ShowInDiscoveryDocument
1   openid  openid  0   1   openid  0   1
2   profile profile 0   1   profile 0   1
3   offline_access  offline_access  0   1   offline_access  0   1
5   api api 0   1   api 0   0

IdentityClaims

Id  IdentityResourceId  Type
4   2   t

I have put the value t in as a claim against profile.

Have I done this configuration wrong?

[brockallen]

Yea, your profile identity resource should have several claim types defined: https://github.com/IdentityServer/IdentityServer4/blob/dev/src/IdentityServer4/Constants.cs#L136. Also, openid should have sub defined: https://github.com/IdentityServer/IdentityServer4/blob/dev/src/IdentityServer4/Constants.cs#L167

[ravetroll]

I thought that IdentityServer4 was picking those up out of its constants based on the name? I ddn't know I had to define them manually in the table. I didn't have to do this configuration in beta5 middleware (Scopes insteads of Resources) and it worked fine, pulling out the claims for profile and openid. Now I know, and hope this helps others too.

[brockallen]

If you're using the EF stores for the resources, then they all need to be defined in the DB (unless you're doing some custom code to merge some from DB and some from in-mem).

[andreslon]

That change was a crap, IScopeStore to IResourceStore ?? , Seriously??

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.