Introductory ramble
Client Application Services (CAS) is the Microsoft solution for ASP.NET and WCF identity management. The default store is XML but nearly everyone reconfigures it to use ASPNETDB on MSSQL.
There is support for per-user information in the shape of the .NET Profile. Within this, the application developer can define an hierarchy of groups and properties.
What there does not appear to be is support for per-role profile information.
Why would you want to do this? My company, for example, has a lot of GPS tracking units leased to companies that fit them to vehicles in their fleets. Each customer has its own database, for administrative reasons (we can do backups on a per customer basis) and some metadata in a common database allows my code to determine which backing store (server and database) to use for data coming in from a given device.
At the moment I have hacked this onto the end of the aspnet_Roles table, but this seems inappropriate, and unlike user profiles this extra data cannot be managed with the IIS7 Manager application.
The question
Is there a supported, endorsed, Microsoft-sanctified way to handle role-based profile data?
Other thoughts
It strikes me that I could create multiple web applications all pointing at the same file-system location. I might then use per-application settings for this purpose. But they'd all have to be on different URLs, which would cause upheaval elsewhere.