I did some testing with dACLs and got it to work, I haven't tested exhaustively other than verifying that it functions. To answer your question it means that the method list needs to actually be named "default" for dACLs to function correctly without anything special from the RADIUS server. If you want to use a different method list name (For example "RADIUS-Author-mList") then the RADIUS server needs to tell the WLC to use that method list. The method list needs to exist in the WLC, but the WLC can't use it unless the RADIUS server says so. If you use a method list with a name other than "default" and the RADIUS server doesn't specify that method list, you'll get an error from the WLC. The error changes with software versions. In one version I saw something to the effect of "ACL Error", in another I saw a message that said the WLC wasn't able to communicate with ISE. But the actual problem was that the WLC didn't know which method list to use.
Your ISE access-accept authorization profile would look something like this one that I used for a CWA portal
I wasn't aware of the memory corruption issue. Since it isn't officially supported I chose not to use dACLs anyway.
