I forgot to submit env info:

Win7

SQL

Version: 2-3-6-5

In previous post I wrote it may be not a bug, but it looks like it is, since the expected steps were performed and then it does not behave as expected (should include all defined roles).

Thanks,

Maciek

Thank you.

Indeed, when I add a new to role to a user who has not logged on at all yet, it works - the new roles are visible in IsInRole.

But once I log on as a certain user, it looks like the list of roles is remembered in its initial state and adding new roles is not reflected in IsInRole.

I log out using the code from Client Application Services walkthrough:

ClientFormsAuthenticationMembershipProvider authProvider =
                (ClientFormsAuthenticationMembershipProvider)
                System.Web.Security.Membership.Provider;
                authProvider.Logout();

and after that

Thread.CurrentPrincipal.Identity.IsAuthenticated correctly returns false.

But when I log on again, the newly added roles are not visible.

Is the list of roles cached somewhere?

Greetings,

Maciek

Yes, it's not a matter of standard or non-standard roles, but caching roles during the first logon.

Both, adding and removing roles later does not affect the return from IsInRole.

So it looks that the roles are cached somewhere (even though ClientFormsAuthenticationMembershipProvider.Logout() is succesfully called)?

Thanks for your help,

Maciek