Hi,

there are few approaches that you can use but everything depends on the fact whether your Web part is stand alone or you have embedded it on User profile Web part. I'll give you few hints on what you can do and with what built-in MonoX classes.

In stand alone scenario you can use "SecurityUtility" class to get the user information. But here you need to keep in mind that built-in MonoX user profile page keeps the username in the Url (it is SEO optimized) so you need to get the username from the Url and to get the proper username you should use the "UrlParams.UserProfile.UserName" strongly-typed approach.


When you have a username then you can use "SecurityUtility" to get the user id, user roles, etc. You can also use the ASP.NET Membership provider for such operations (More about the Membership provider). With "SecurityUtility" you can get the profile user and current user and match them to see what permissions to apply.

In embedded to user profile scenario you need to use the "UserId" property of the user profile to check what is the profile user and you can use "SecurityUtility" to get the current user. The rest of the permission implementation is up to you.

I hope that this will point you in the right direction.

Regards.

Hi Shawn,
Visibility of the Web part is managed automatically. If the currently active user is a member of at least one role that is selected in the "View roles" checkbox list in the Web parts properties tab, the part is visible to him, otherwise it is not displayed.
You can programatically check the role membership:


As for the profile page, you would probably want to check if the currently active user is the owner of the profile. The standard technique is to pass the username in the URL. You can than retrieve the user name, find it's ID and compare that to the user ID or name of the currently active user:


There are various different strategies to achieve what you want. Let me know if this helps,

Denis

Ok.. Thanks for the help.. should help point me in the right direction.

I'm thinking.. I have a need for both ways..

I want in some scenarios to just place a control a user profile.. and have it know.. if the user is logged in is the assigned user or not... and display edit or view..

I also have a need to have a whole separate page to allow for simple task.. like uploading files could in theory work better as one page.. As I plan to have a pretty detailed system when it comes to folder hierarchy and support and I prob want a pretty detailed interface.. I also want to make sure I have code reuse.. as much of this code would be usable in several controls I plan to write..

Im more of less trying to figure out the best way to do my permission system..

I dont see me having to many permission needs at first.. so .. although the simple approach is a good starting block I do see a future need for a more detailed permissions system.. with rules.. etc.. So It may be a good idea for me to at least some sort of basic rule support to my initial code.

I am a little concerned too.. about having the webpart know it can only be placed on a user profile.. .. maybe something like you said..



Or is there a better way to do this ? or is this method ok.. ?

Hi,

you need to distinguish user profile module (the one that I have been talking about in previous post) and user profile page. You will not benefit much by placing your Web part on the user profile page because it will be threated like every other page so you will need to handle everything as you have mentioned above.

Maybe you are looking for something like this. You can extend the user profile Web part so you can lean on user profile data binding, and some of the permission rules are already implemented for you.


Let me know if this helps, Regards.