locked
Probelm with E-mail Notification Feature of Issue Tracking List RRS feed

  • Question

  • When creating a list in MOSS 2007 using the "Issue Tracking" template, there is a feature which sends an automatic email out when the issue is assigned/reassigned.  On most of our sites, this functionality works fine. 

    We have one web application which uses both NTLM and FBA authentication (uses one content db but has two URLs: http://clients.company.com for NTLM and https://client.company.com for FBA).  There is an Issue Tracking list on this particular site and the issue can potentially be assigned to internal users (NTLM) or external users (FBA).  We have found that when an issue is assigned to an external user, the hyperlinks in the automatic email refer to http://clients.company.com instead of the https://client.company.com that the external users need to be using.

    Is there any way to configure the feature so that the links in the automatic email are relative to the URL the user should be using?

    There must be a way, because if an external user manually sets up an alert on any list/library, the alert email does correctly reference the external URL to the site.  Any ideas?

    Wednesday, December 8, 2010 12:32 AM

Answers

  • Your last paragraph explains exactly what you are encountering and why it works the way it works for you.

    1.  When a user adds an Alert via https, the alert works just fine and the user gets the alert.  The same applies to a user adding an alert via http.

    2.  When you assign a task to an external https user, they get the link with an http url value.  This is expected behavior.

    3.  If you were to assign a task to an internal http user, they would get the link with a http url value which would work just fine.  In the same way, if you were logged in as an external https user and assigned a task to another external https user, they should also get the link with a https url and it should work just fine for them too.

    The disconnect is that the processing of the task assignment, uses whatever server url YOU are connected under and NOT the url and/or protocol of the assignee.  Therefor, an internal user cannot assign a task to an external user and an external user cannot assign a task to an internal user.

    The can be overcome with something like ISA Server to do proxy switching i.e. when an internal user tries to hit the site via https, it will switch them over to the http version.  In the same way, when an external user tries to hit the site via http, it will switch them over to the https version.

    With that in place, you can cross assign tasks and event though the link is incorrect (http instead of https) the proxy switch would fix it and the end user would be none the wiser.  It should be seamless to the end user.

     


    I trust that answers your question...

    Thanks
    C

    http://www.cjvandyk.com/blog
    • Marked as answer by Emir Liu Thursday, December 16, 2010 2:59 AM
    Wednesday, December 8, 2010 9:48 PM
    Answerer

All replies

  • Your last paragraph explains exactly what you are encountering and why it works the way it works for you.

    1.  When a user adds an Alert via https, the alert works just fine and the user gets the alert.  The same applies to a user adding an alert via http.

    2.  When you assign a task to an external https user, they get the link with an http url value.  This is expected behavior.

    3.  If you were to assign a task to an internal http user, they would get the link with a http url value which would work just fine.  In the same way, if you were logged in as an external https user and assigned a task to another external https user, they should also get the link with a https url and it should work just fine for them too.

    The disconnect is that the processing of the task assignment, uses whatever server url YOU are connected under and NOT the url and/or protocol of the assignee.  Therefor, an internal user cannot assign a task to an external user and an external user cannot assign a task to an internal user.

    The can be overcome with something like ISA Server to do proxy switching i.e. when an internal user tries to hit the site via https, it will switch them over to the http version.  In the same way, when an external user tries to hit the site via http, it will switch them over to the https version.

    With that in place, you can cross assign tasks and event though the link is incorrect (http instead of https) the proxy switch would fix it and the end user would be none the wiser.  It should be seamless to the end user.

     


    I trust that answers your question...

    Thanks
    C

    http://www.cjvandyk.com/blog
    • Marked as answer by Emir Liu Thursday, December 16, 2010 2:59 AM
    Wednesday, December 8, 2010 9:48 PM
    Answerer
  • Thank you for the detailed response.  Can you provide a link to something which explains proxy switching within SharePoint?  I'm not very familiar with it. 
    Thursday, December 9, 2010 3:53 AM