locked
CRM 2011 IFD RRS feed

  • Question

  • Greetings,

    I was wondering if someone can figure out what I'm doing wrong in order to configure Forefront TMG 2010 server to publish our CRM 2011 server to the Internet.

    Environment setup:

    CRM Server:    Host Name: crm5-svr   IP: 10.40.50.10

    IIS setup:

    Domain Name: mydomain.Internal

    Default site is assigned to ADFS on port 444

    Second site is assigned to CRM on port 443

    Internal to our LAN everything is working as expected users can go to:

    https://crm5.mydomain.com

    http://crm5-svr:5555

     

    Internally all the following DNS are pointing to our CRM/ADFS server ( 10.40.50.10)

    Externally all the Following DNS are pointing to only one public address

    Crm5.mydomain.com

    Dev.mydomain.com

    Auth.mydomain.com

    Sts.mydomain.com

    Adfs.mydomain.com

    Intcrm.mydomai.com

     

    Forefront TMG 2010 with SP2

    Listener name: CRM-Listener1

                 Connections: Http (port 80) and Https (port 443) Enabled ,

                                            Redirect all traffic from HTTP to HTTPS

                Client Authentication method: No Authentication

                Certificates: Assign a certificate for each IP address- the public IP and related wildcard cert purchased from Digicert.

     

     

                                                                                                                                       

    TMG Rule 1.

    Rule name: CRM-Org

    From: Anywhere

    To:       crm5.mydomain.com

    Computer name or IP address: 10.40.50.10

    Forward all original host headers …                    Checked          

    Request appear to come from original client       Selected

    Listener: CRM-Listener1

     Public Name: crm5.mydomain.com

    Path: /*

    Authentication Delegation: No delegation, but client may authenticate directly

    Bridging: Redirect requests to SSL port                         443

     

    TMG Rule2

    Rule Name: CRM-Sts

    From: Anywhere

    To:       sts.mydomain.com

    Computer name or IP address: 10.40.50.10

    Forward all original host headers …                    Checked          

    Request appear to come from original client       Selected

    Listener: CRM-Listener1

     Public Name: sts.mydomain.com

    Path: /*

    Authentication Delegation: No delegation, but client may authenticate directly

    Bridging: Redirect requests to SSL port                         444   

     

    TMG Rule3

    Rule Name: CRM-Auth

    From: Anywhere

    To:       auth.mydomain.com

    Computer name or IP address: 10.40.50.10

    Forward all original host headers …                    Checked          

    Request appear to come from original client       Selected

    Listener: CRM-Listener1

     Public Name: auth.mydomain.com

    Path: /*

    Authentication Delegation: No delegation, but client may authenticate directly

    Bridging: Redirect requests to SSL port                         444    

     

    TMG Rule4

    Rule Name: CRM-Dev

    From: Anywhere

    To:       Dev.mydomain.com

    Computer name or IP address: 10.40.50.10

    Forward all original host headers …                    Checked          

    Request appear to come from original client       Selected

    Listener: CRM-Listener1

     Public Name:            Dev.mydomain.com

    Path: /*

    Authentication Delegation: No delegation, but client may authenticate directly

    Bridging: Redirect requests to SSL port                         444    

     

    TMG Rule5:

    Rule Name: CRM-ADFS

    From: Anywhere

    To:       ADFS.mydomain.com

    Computer name or IP address: 10.40.50.10

    Forward all original host headers …                    Checked          

    Request appear to come from original client       Selected

    Listener: CRM-Listener1

     Public Name:      ADFS.mydomain.com

    Path: /*

    Authentication Delegation: No delegation, but client may authenticate directly

    Bridging: Redirect requests to SSL port                         444    

     

     

    Appreciate any help very much, and please do let me know if you should have any further questions or comments.

    Thanks for looking at this case,

    Ed.

    Monday, February 6, 2012 3:09 AM

All replies

  • Hi Ed,

                    It would be easier to help you if you also share what errors are you getting, one thing I can tell you that might be causing issues is the redirect all traffic from http to https, and I have noticed that with that setting the AD FS not always work specially when connecting the outlook client. Based on the port numbers I guess you have ADFS and CRM installed on the same server, on that case you must be binding the http port to 81 on the ADFS website.

     

     


    Regards,
    Damian Sinay
    Monday, February 6, 2012 6:16 AM
  • Hi,

    I can see few mistakes in this configuration.

    1. How did you configure ADFS URL?

     using Sts.mydomain.com or Adfs.mydomain.com

    2. You have the above added two host names. You need to provide the only one ADFS host name which you have configured.

    3. Is CRM5 organization?

    4. You dont need to add Internal CRM host in TMG, because you will not use the Internal CRM URL externally.

    5. On which port you have configured ADFS? if it is 444 then you just need to add one listener for ADFS on 444 port. 

    6. Bridging for Auth and Dev should be 443 not 444.

    Go through the configuration in TMG again and test it.

    http://www.dynamicsexchange.com/Blogs/user.aspx?Tableid=285

     

    Regards, 


    Khaja Mohiddin|||||http://www.dynamicsexchange.com/
    Monday, February 6, 2012 11:38 AM
  • Daminan/Khaja,

    Thank you so very much for taking your time and trying help; i have done all the changes that you guys recomended with no luck yet. I am posing the updated configuration below again. Please give a look and let me know if you see anything that I can change to make the IFD working from out side of our institution.

    1. How did you configure ADFS URL? Sts.mydomain.com

    2. You have the above added two host names. I removed the extra rule

    3. Is CRM5 organization? yes Org name is CRM5 and the host server name is vCRM5-SVR

    4. You dont need to add Internal CRM host in TMG, because you will not use the Internal CRM URL externally. Dont understand what you mean; should I remove the part that sys To: under rules

    5. On which port you have configured ADFS? 444 I have added additional Listener  

    6. Bridging for Auth and Dev should be 443 not 444.

    I have diabled the redirecting from http to https and removed an extra TMG rule. Also, I'm including the errors and a few snapshots below:

     

    Environment setup:

    CRM Server:    Host Name: crm5-svr   IP: 10.40.50.10                 CRM Org Name; CRM5

    IIS setup:

    AD Domain Name: mydomain.Internal

    Default site is assigned to ADFS on port 444

    Second site is assigned to CRM on port 443

    Internal to our LAN everything is working as expected users can go to:

    https://crm5.mydomain.com

    http://crm5-svr:5555

    Internally all the following DNS are point to our CRM/ADFS server ( 10.40.50.10)

    Externally all the Following DNS are pointing to only one public address

    Crm5.mydomain.com

    Dev.mydomain.com

    Auth.mydomain.com

    Sts.mydomain.com

    Adfs.mydomain.com

    Intcrm.mydomai.com

    Forefront TMG 2010 with SP2

    Listener name: CRM-Listener1

                Connections: Https (port 443) Enabled ,

                                           

                Client Authentication method: No Authentication

                Certificates: Assign a certificate for each IP address- the public IP and related wildcard cert purchased from Digicert.

    Listener name: CRM-Listener2

                Connections: Https (port 444) Enabled

                Client Authentication method: No Authentication

                Certificates: Assign a certificate for each IP address- the public IP and related wildcard cert purchased from Digicert.

                                                                                                                                       

    TMG Rule 1. Rule name: CRM Org

    From: Anywhere

    To:       crm5.mydomain.com

    Computer name or IP address: 10.40.50.10

    Forward all original host headers …                    Checked          

    Request appear to come from original client       Selected

    Listener: CRM-Listener1

    Public Name: crm5.mydomain.com

    Path: /*

    Authentication Delegation: No delegation, but client may authenticate directly

    Bridging: Redirect requests to SSL port                         443

    TMG Rule2: CRM-Sts

    From: Anywhere

    To:       sts.mydomain.com

    Computer name or IP address: 10.40.50.10

    Forward all original host headers …                    Checked          

    Request appear to come from original client       Selected

    Listener: CRM-Listener2

    Public Name: sts.mydomain.com

    Path: /*

    Authentication Delegation: No delegation, but client may authenticate directly

    Bridging: Redirect requests to SSL port                         443

    TMG Rule3: CRM-Auth

    From: Anywhere

    To:       auth.mydomain.com

    Computer name or IP address: 10.40.50.10

    Forward all original host headers …                    Checked          

    Request appear to come from original client       Selected

    Listener: CRM-Listener2

    Public Name: auth.mydomain.com

    Path: /*

    Authentication Delegation: No delegation, but client may authenticate directly

    Bridging: Redirect requests to SSL port                         443

    TMG Rule4: CRM-Dev

    From: Anywhere

    To:       Dev.mydomain.com

    Computer name or IP address: 10.40.50.10

    Forward all original host headers …                    Checked          

    Request appear to come from original client       Selected

    Listener: CRM-Listener2

    Public Name:  Dev.mydomain.com

    Path: /*

    Authentication Delegation: No delegation, but client may authenticate directly

    Bridging: Redirect requests to SSL port                         443

      I get this when i try to brows to the website:

    https://sts.mydomain.com:444/adfs/ls/?wa=wsignin1.0&wtrealm=https%3a%2f%2fcrm5.mydomain.com%2f&wctx=rm%3d1%26id%3d0024bed6-02ac-4a48-81b2-c21d2c7b4da9%26ru%3dhttps%253a%252f%252fcrm5.mydomain.com%252fdefault.aspx&wct=2012-02-07T03%3a58%3a10Z&wauth=urn%3aoasis%3anames%3atc%3aSAML%3a1.0%3aam%3apassword

    Technical Information (for support personnel)

    • Error Code: 500 Internal Server Error. The request was rejected by the HTTP filter. Contact the server administrator. (12217)

    On the TMG side:

     

    Allowed Connection

    2/6/2012 11:49:50 PM

    Log type: Web Proxy (Reverse)

    Status: 302 Moved Temporarily

    Rule: CRM IFD

    Source: External (99.69.199.220:52070)

    Destination: Local Host (adfs.mydomain.com 10.31.2.79:443)

    Request: GET http://crm5.mydomain.com/

    Filter information: Req ID: 0b48841f

    Protocol: https

    User: anonymous

    <wrap type="none"></wrap><anchorlock></anchorlock><//span>

    Denied Connection

    FW-SVR 2/6/2012 11:49:50 PM

    <id id="L_LogPane_LogType"></id>

    Log type: </id><//id><id id="L_LogPane_WebProxyForward"></id>Web Proxy (Reverse)

    </id><//id>
    <id id="L_LogPane_Status"></id>

    Status: </id><//id>12217 The request was rejected by the HTTP filter. Contact your Forefront TMG administrator.

    <id id="L_LogPane_Rule"></id>

    Rule: </id><//id>CRM Sts

    <id id="L_LogPane_Source"></id>

    Source: </id><//id>External (99.69.199.220:52071)

    <id id="L_LogPane_Destination"></id>

    Destination: </id><//id>Local Host (96.61.198.67:443)

    <id id="L_LogPane_Request"></id>

    Request: </id><//id>GET http://sts.mydomain.com/adfs/ls/?wa=wsignin1.0&wtrealm=https%3a%2f%2fcrm5. mydomain.com %2f&wctx=rm%3d1%26id%3daea16088-e556-4b64-a24b-fafba13947f0%26ru%3dhttps%253a%252f%252fcrm5. mydomain.com %252fdefault.aspx&wct=2012-02-07T04%3a50%3a39Z&wauth=urn%3aoasis%3anames%3atc%3aSAML%3a1.0%3aam%3apassword

    <id id="L_LogPane_FilterInfo"></id>

    Filter information: </id><//id>Req ID: 0b488422; Blocked by the HTTP Security filter: URL normalization was not complete after one pass

    <id id="L_LogPane_Protocol"></id>

    Protocol: </id><//id>https

    <id id="L_LogPane_User"></id>

    User: </id><//id>anonymous

    <wrap type="none"></wrap><anchorlock></anchorlock>


    • Edited by Essi22 Tuesday, February 7, 2012 5:00 AM
    Tuesday, February 7, 2012 4:58 AM
  • Hi,

    1. Externally all the Following DNS are pointing to only one public address

    Crm5.mydomain.com

    Dev.mydomain.com

    Auth.mydomain.com

    Sts.mydomain.com

    Adfs.mydomain.com(Why this host is point to your static IP? you have confgured ADFS using sts.mydoamin.com, so you can delete this.)

    Intcrm.mydomai.com(This can be used only internally,, so this also you can delete.)

    ****Delete the aobve two rules from TMG also.****

    2. Internal to our LAN everything is working as expected users can go to:

    https://crm5.mydomain.com

    http://crm5-svr:5555(Once you configure IFD there should not be more than one port for Microsoft Dynamics CRM, so you can delete this. For internal access use internal.mydomain.com not the external url and the http://crm5-svr:5555)

    3. 

    Allowed Connection

    2/6/2012 11:49:50 PM

    Log type: Web Proxy (Reverse)

    Status: 302 Moved Temporarily

    Rule: CRM IFD

    Source: External (99.69.199.220:52070)

    Destination: Local Host (adfs.mydomain.com 10.31.2.79:443)(Why you are using ADFS.mydomain.com, you have configured using sts.mydomain.com)

    Request: GET http://crm5.mydomain.com/

    Filter information: Req ID: 0b48841f

    Protocol: https

    User: anonymous

    <wrap type="none"></wrap><anchorlock></anchorlock><//span>

    You need to delete the above rule from TMG.

    Regards,


    Khaja Mohiddin  ||  http://www.dynamicsexchange.com/


    Wednesday, February 8, 2012 10:18 AM
  • Khaja,

    Thanks so much, I got everything working now.

    Best to you,

    Ed

    Monday, February 13, 2012 1:56 PM
  • Hi Ed,

    Can you please mark as the above solution as answer if my suggestions are helpful for you.

    Regards,


    Khaja Mohiddin|||||http://www.dynamicsexchange.com/

    • Proposed as answer by Khaja Mohiddin Wednesday, January 2, 2013 7:48 PM
    Monday, February 13, 2012 2:32 PM