Hello everyone,

I am having exactly the same issue ( I think...) , cleared all the cookies, temporary internet files, everything..I even logged this user (going to referr to him from now on as USER A) on different machines and the error persisted. After googling for this issue I found this thread and checked for the USER A's amount of roles and in fact he did have 42 roles associated. Before starting removing roles I went to check if there was any other user with such amount of roles. The answer was yes. There was another user (From now on referred as USER B) with 65 roles associated, but odly enough, USER B doesnt have any issue logging in. Both USER A and USER B use Internet Explorer 7 (Tried to user IE6 with USER A also but error persists). Recapping:

USER A
# of roles: 42
Cookies, temporary internet files deleted, History deleted? Yes
Browsers tested: Internet Explorer 6, Internet Explorer 7
Can login? No. Invalid value for 'encryptedTicket' parameter exception occurs.

USER B
# of roles: 65
Cookies, temp internet files deleted, History deleted? Yes
Browsers tested: Internet Explorer 7
Can login? Yes.

USER A and USER B have the largest amount of roles associated. they are respectively number #2 and #1 on the TOP # of roles associated.

As a side note, wich may have some relevance, we upgraded recently from DotNetNuke v1.0.10 to v4.8.4. Before we entered production phase, we asked all users to clear their browsers cache and cookies because during test phase we were having issues regarding encryption and bad data errors if a user previously logged in on the old portal and then on the new one (Wich was promptly solved just by deleting cookies and logging back on the new portal). This USER A, although, was on Maternity Leave from company and returned today and didnt follow the procedure of clearing cookies and cache before accessing the new portal. Although we cleared all cookies and cache when the error was reported, is there any chance something is being left behind and avoiding the resolution of the problem?

This is the only user in the whole company (around 500 logins) having this issue!

Hello again,

Regarding my previous post, I tried to remove a couple roles to the User A and the problem was solved. Its still weird that another user with an higher amount of roles can login perfectly fine...oh well, time to check with people in charge if its possible to have a "role merge" or some other kind of refactoring aproach on the application.

Cheers!

It's not the number of roles, it is the length of the role names (all added together) that reach the limited size of the user cookie. If you have many DNN roles they should be as short as possible.

A simple fix might be to compress or zip up the string to use less space, then unzip it for use in the app. The most efficient refactoring would be to use bit fields (corresponding to roleIDs) which would limit the number of roles but be very efficient for role validation. For example, 16 bytes could store combinations of 128 different roles.

Without getting into security implications, you could add a checksum or hash sum byte to verify integrity.