Thanks for the pack. Great one. And works perfectly.
The only default ,for my usage, is that on each site collection where the feature is deployed, we can see all the users (I know that seeing the users doesn't mean the can access the site collection, that's not my purpose). I'd rather see only the users created for each site collection. I understood that through olnly one provider with one Appname (and one database but that's not the problem I think), this is the normal behaviour. But do you think it would be difficult to add a column in the database with the site collection URL, add the URL of the site collection when adding the user from the site collection and filter the users with this column when you display it on the FBA management user page ? Do you think there would be a simplier solution to do that (seeing only the site collection users) ? SharePoint is limited to 4 web app extensions (+ default zone) (I could define extensions with different providers) and I don't want create a lot of web applications either (IIS pool applications limit). I work in a really big firm and I could have many of this kind of applications.
Regards
The only default ,for my usage, is that on each site collection where the feature is deployed, we can see all the users (I know that seeing the users doesn't mean the can access the site collection, that's not my purpose). I'd rather see only the users created for each site collection. I understood that through olnly one provider with one Appname (and one database but that's not the problem I think), this is the normal behaviour. But do you think it would be difficult to add a column in the database with the site collection URL, add the URL of the site collection when adding the user from the site collection and filter the users with this column when you display it on the FBA management user page ? Do you think there would be a simplier solution to do that (seeing only the site collection users) ? SharePoint is limited to 4 web app extensions (+ default zone) (I could define extensions with different providers) and I don't want create a lot of web applications either (IIS pool applications limit). I work in a really big firm and I could have many of this kind of applications.
Regards