locked
Internal sharepoint page accessed externally issue. RRS feed

  • Question

  • Hello,

    We have Sharepoint running our company intranet.

    Users are able to get to it when logged to the network (of course!) "Windows Integrated Authentication", and when outside the network thru Microsoft Forefront.

    Some of the links in the main page are to applications hosted inside only, we would like to hide these links to the users that are accessing the page when outside the network.
    The only thing I could think of is to create a second website (clone), remove the links and point MS Forefront to it, but then every change made to the main website will need to be replicated.

    Is there any other solution anybody is aware?

    Thanks,


    Alex

     

    Wednesday, May 11, 2011 11:31 AM

Answers

  • 1: This new page would be required to be published with another web app and virtual directory in ISS?

    2: Also, I would be able to remove specific content from this second site, let's say the ability for users that reach this second site to see a specific link or web part?


    1: As far as publishing is concern, let see one scenario. Your A and B sites are uptodate now. You do one change in site A's xyz.aspx page but not published yet. In this case your site B will not reflect new change since it is not published. When you publish from A site then B automaticaly show upated text. This means both A and B are synchornized because both the sites are using same content database.

    2: Let me confirm second point.


    w: http://www.worldofsharepoint.com | t: @sharesandip
    • Marked as answer by Peng Lei Wednesday, May 18, 2011 1:23 AM
    Thursday, May 12, 2011 12:25 PM

All replies

  • The only thing I could think of is to create a second website (clone), remove the links and point MS Forefront to it, but then every change made to the main website will need to be replicated.


    Extend new site from first in Central Admin --> Create or Extend Web Application, in this case your content database of both the sites are same so if you do any change in one site it get reflected in second site. Extending means creating new web application in ISS and new virtual directory.
    w: http://www.worldofsharepoint.com | t: @sharesandip
    Wednesday, May 11, 2011 1:17 PM
  • Thanks Sandip,

    So let's see if my understanding is completely correct:

    Let's assume my main site is http://mysite.com/Pages/Default.aspx

    I would extend the site above in Central Admin --> Create or Extend Web Application with an address like: http://mysite.com/ExternalPages/Default.aspx.

    This new page would be required to be published with another web app and virtual directory in ISS?

    Also, I would be able to remove specific content from this second site, let's say the ability for users that reach this second site to see a specific link or web part?

    Thanks again,

    Alex

    Thursday, May 12, 2011 12:02 PM
  • 1: This new page would be required to be published with another web app and virtual directory in ISS?

    2: Also, I would be able to remove specific content from this second site, let's say the ability for users that reach this second site to see a specific link or web part?


    1: As far as publishing is concern, let see one scenario. Your A and B sites are uptodate now. You do one change in site A's xyz.aspx page but not published yet. In this case your site B will not reflect new change since it is not published. When you publish from A site then B automaticaly show upated text. This means both A and B are synchornized because both the sites are using same content database.

    2: Let me confirm second point.


    w: http://www.worldofsharepoint.com | t: @sharesandip
    • Marked as answer by Peng Lei Wednesday, May 18, 2011 1:23 AM
    Thursday, May 12, 2011 12:25 PM