Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I'm a Sharepoint development beginner and I would like to develop a custom application on top of Sharepoint Foundation 2010. I decided to write few visual web parts for simple logic and Silverlight web parts for complex application logic.

My application will use it's own data in a separate DB. The only connection between my DB and Sharepoint DB will be users. Users will authenticate against Sharepoint and access my application from there.

Within my application (and DB) all these users will be hierarchically related (I don't know if this is trivially possible in Active Directory so I could avoid one part of user administration?) and they will also define certain rights within my application.

Problem?

If I do write web parts (of whatever kind), how do I ensure that these same web parts are not used in other Sharepoint sites as well? It would most probably break the application and it could of course make it possible to replicate the same application but using different users...

I thought of writing application pages (my application would be in _layouts folder as I understand it), which would make it possible to not reuse my application, but users and rights are assigned on site level... So I can't win this way either...

What would you suggest?

share|improve this question
add comment

2 Answers

SharePoint does not provide authentication. User accounts in SharePoint are authenticated by Active Directory or ASP.Net Membership providers.

Why are you using SharePoint for the application if you will not be using any of the SharePoint functionality?

Perhaps you should simply write the application in ASP.Net and use the Page Viewer Web Part to display your application on a SharePoint web part page.

share|improve this answer
    
Users will authenticate against Sharepoint. They will be authorised based on settings in Sharepoint. I'm developing an app on Sharepoint because the clients wants it to be integrated with Sharepoint. So users won't authenticate twice and for very strict security measures (client certificates) I won't have to deal with authentication whatsoever. –  Robert Koritnik Jun 30 '10 at 13:17
    
Page viewer web part is not an option since it uses IFRAME which means that users authenticated in Sharepoint won't be authenticated in my application. I won't have any security info from SP. I will use user data from Sharepoint. –  Robert Koritnik Jun 30 '10 at 13:19
    
An IFrame doesn't negate authentication, they just need to be able to authenticate to both systems. If both are setup properly with Windows Auth, a domain user will not be prompted for either site. –  Mike Oryszak Jul 27 '10 at 13:03
add comment

You may want to look at Robin Meure's Feature Blocker. I am not sure if it has been updated for SharePoint 2010 though.

There are a number of alternative approaches you can take. For full control you may want to check the URL of the Site Collection the Web part is running on and see if it matches a list of 'allowed sites'.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.