Sign in
Microsoft.com
 
Forefront Edge Security TechCenter
 
 
 
Forefront Edge Security TechCenter > Forefront Edge Security Forums > Forefront Edge Security – IAG/UAG > Publishing Corporate Website
Ask a questionAsk a question
Search Forums:
 

AnswerPublishing Corporate Website

  • Tuesday, July 07, 2009 10:35 PMDennis [Celestix] Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    1
    Sign In to Vote

    Hello.

    I recently had an inquiry regarding using IAG to publish their corporate website for example http://contoso.com

    My clients concerns is that if they publish their website with IAG, the IAG URL Rewriting Hash will cause issues with internet search engines, web crawling, User Bookmarks and so forth…

    Is there any way I can get rid of the hash for just this type of publishing that my client requires?

     

    --Somewhat related for others FYI--

    If it contained a sub-domain name such as http://test.contoso.com  and we were publishing SharePoint 2007, I would be fine.   Why?  Because I will just advertise my SharePoint AAM –URL as my public URL instead of my trunk-URL.   The SharePoint AAM-URL can be accessed directly and doesn’t provide hashing.

    Thank you!
    Dennis

     

     

Answers

  • Wednesday, July 08, 2009 8:23 PMRan [MSFT] Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hi Dennis,

    a) as you mentioned yourself in your first post that started this thread, if the website in question is a SharePoint site, then IAG can leverage the AAM functionality built into SharePoint and therefore IAG wil not perform its own Host Address Translation (HAT)

    b) if the backend site is the only resource that you want to publish, or if you are OK with having a separate trunk for it, then you have the option to use a Basic trunk (through which all incoming HTTP requests are forwarded by IAG to only one single backend destination), and on such a trunk there is no HAT

    c) if you need to publish multiple backend resources, either web or non-web, and you want to allow access to all of them through one single IAG trunk, then you have to use an IAG Portal trunk, and, if the backend application we're talking about is not SharePoint, then HAT will take place and you cannot turn that off

    d) however, the HAT "hash" (or HAT signature, as we usually refer to it) does not change. It remains the same (one HAT signature for each different IAG application published through a Portal trunk), as long as you do not change the HAT Unique Identifier or the HAT Encryption Key (see IAG Configuration -> Admin menu -> Advanced Configuration)

    HTH,
    -Ran
     

All Replies

  • Wednesday, July 08, 2009 11:54 AMFaisal Hussain [MSFT] Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    could you explain the required scenario in bit more detail to understand the concerns ?

    thanks,
    Faisal :>
     
  • Wednesday, July 08, 2009 6:56 PMDennis [Celestix] Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Basically- 

    I want to use IAG to secure the public website such as:

    http://www.contoso.com

    IAG is requiring a sub-domain like http://www.iag.contoso.com


    and... if I can get the above working:  I'd like the hash to either be removed or atleast stay static.

    Thanks!
    Dennis
     
  • Wednesday, July 08, 2009 8:23 PMRan [MSFT] Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hi Dennis,

    a) as you mentioned yourself in your first post that started this thread, if the website in question is a SharePoint site, then IAG can leverage the AAM functionality built into SharePoint and therefore IAG wil not perform its own Host Address Translation (HAT)

    b) if the backend site is the only resource that you want to publish, or if you are OK with having a separate trunk for it, then you have the option to use a Basic trunk (through which all incoming HTTP requests are forwarded by IAG to only one single backend destination), and on such a trunk there is no HAT

    c) if you need to publish multiple backend resources, either web or non-web, and you want to allow access to all of them through one single IAG trunk, then you have to use an IAG Portal trunk, and, if the backend application we're talking about is not SharePoint, then HAT will take place and you cannot turn that off

    d) however, the HAT "hash" (or HAT signature, as we usually refer to it) does not change. It remains the same (one HAT signature for each different IAG application published through a Portal trunk), as long as you do not change the HAT Unique Identifier or the HAT Encryption Key (see IAG Configuration -> Admin menu -> Advanced Configuration)

    HTH,
    -Ran
     
  • Wednesday, July 08, 2009 9:30 PMDennis [Celestix] Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Ran-

    I am going to try option b and hope that is acceptable for our client.

    Thanks!

    Dennis
     
  • Wednesday, November 04, 2009 2:49 PMIAG Novice Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Ran, Are you saying in point a) that if I follow this process:

    http://technet.microsoft.com/en-us/library/dd278112.aspx

    then the IAG will not perform HAT and thus the URL will not contain any hashing?

    Thanks
     
  • Thursday, November 05, 2009 5:59 PMDennis [Celestix] Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    That's correct.   Option A would also be a valid solution to my original question.

    Thanks