4.0 Internet Facing Deployment Signin.aspx page targets wrong url (no

I've set up an IFD and everything is working fine, except that
"targeturl" parameter is missing the port number for the CRM website.
When you open the CRM server external url in IE (https://
<organizationname>.<subdomain>.<domain>.com:5555/), you're redirected
to this url:

https://<organizationname>.<subdomain>.<domain>.com:5555/signin.aspx?targeturl=https%3a%2f%2f<organizationname>.<subdomain>.<domain>.com%2fdefault.aspx

However, the correct url should be:

https://<organizationname>.<subdomain>.<domain>.com:5555/signin.aspx?targeturl=https%3a%2f%2f<organizationname>.<subdomain>.<domain>.com%3a5555%2fdefault.aspx

Notice that the correct url has "%3a5555" which is the port number.

So after the user logs in, they are directed to
https://<organizationname>.<subdomain>.<domain>.com:443 and not
https://<organizationname>.<subdomain>.<domain>.com:5555 like they
should be, and they get a 404, since the CRM server does not expose
port 443 (another server routes all 5555 traffic to port 443 of the
CRM server.)

HOWEVER: if instead of using the url: "https://
<organizationname>.<subdomain>.<domain>.com:5555/" the user instead
uses "https://<organizationname>.<subdomain>.<domain>.com:5555/
signin.aspx" then the user does not get the "?targeturl" appended to
the address, port 5555 sticks to the url, and everything works fine.

Anyone know how to fix this? How does the "targeturl" parameter get
set? I'd like to avoid putting a forwarding page on port 443 of the
exposed server to the appropriate signin page.

Thanks,
Phil

AdamEdmonds
Wed Jun 25 14:33:00 CDT 2008

Phil,
Have you had anyluck with this? I think I'm having a similar problem.

Thanks,
Adam

"Phil - DynamicsCrmBlog.com" wrote:

> I've set up an IFD and everything is working fine, except that
> "targeturl" parameter is missing the port number for the CRM website.
> When you open the CRM server external url in IE (https://
> <organizationname>.<subdomain>.<domain>.com:5555/), you're redirected
> to this url:
>
> https://<organizationname>.<subdomain>.<domain>.com:5555/signin.aspx?targeturl=https%3a%2f%2f<organizationname>.<subdomain>.<domain>.com%2fdefault.aspx
>
> However, the correct url should be:
>
> https://<organizationname>.<subdomain>.<domain>.com:5555/signin.aspx?targeturl=https%3a%2f%2f<organizationname>.<subdomain>.<domain>.com%3a5555%2fdefault.aspx
>
> Notice that the correct url has "%3a5555" which is the port number.
>
> So after the user logs in, they are directed to
> https://<organizationname>.<subdomain>.<domain>.com:443 and not
> https://<organizationname>.<subdomain>.<domain>.com:5555 like they
> should be, and they get a 404, since the CRM server does not expose
> port 443 (another server routes all 5555 traffic to port 443 of the
> CRM server.)
>
> HOWEVER: if instead of using the url: "https://
> <organizationname>.<subdomain>.<domain>.com:5555/" the user instead
> uses "https://<organizationname>.<subdomain>.<domain>.com:5555/
> signin.aspx" then the user does not get the "?targeturl" appended to
> the address, port 5555 sticks to the url, and everything works fine.
>
> Anyone know how to fix this? How does the "targeturl" parameter get
> set? I'd like to avoid putting a forwarding page on port 443 of the
> exposed server to the appropriate signin page.
>
> Thanks,
> Phil
>

Robert
Sat Jul 19 08:37:00 CDT 2008

Had a similar problem I just could not use SSL port 5555 had a tech from MS
for ISA and CRM 4 worked 6 hours we gave up went back to SSL 443 everything
is workign great including the email router. If anyone know anything about
SSL 5555 and using ISA to make this work I would be glad to receive the
advice and try.

"AdamEdmonds" wrote:

> Phil,
> Have you had anyluck with this? I think I'm having a similar problem.
>
> Thanks,
> Adam
>
> "Phil - DynamicsCrmBlog.com" wrote:
>
> > I've set up an IFD and everything is working fine, except that
> > "targeturl" parameter is missing the port number for the CRM website.
> > When you open the CRM server external url in IE (https://
> > <organizationname>.<subdomain>.<domain>.com:5555/), you're redirected
> > to this url:
> >
> > https://<organizationname>.<subdomain>.<domain>.com:5555/signin.aspx?targeturl=https%3a%2f%2f<organizationname>.<subdomain>.<domain>.com%2fdefault.aspx
> >
> > However, the correct url should be:
> >
> > https://<organizationname>.<subdomain>.<domain>.com:5555/signin.aspx?targeturl=https%3a%2f%2f<organizationname>.<subdomain>.<domain>.com%3a5555%2fdefault.aspx
> >
> > Notice that the correct url has "%3a5555" which is the port number.
> >
> > So after the user logs in, they are directed to
> > https://<organizationname>.<subdomain>.<domain>.com:443 and not
> > https://<organizationname>.<subdomain>.<domain>.com:5555 like they
> > should be, and they get a 404, since the CRM server does not expose
> > port 443 (another server routes all 5555 traffic to port 443 of the
> > CRM server.)
> >
> > HOWEVER: if instead of using the url: "https://
> > <organizationname>.<subdomain>.<domain>.com:5555/" the user instead
> > uses "https://<organizationname>.<subdomain>.<domain>.com:5555/
> > signin.aspx" then the user does not get the "?targeturl" appended to
> > the address, port 5555 sticks to the url, and everything works fine.
> >
> > Anyone know how to fix this? How does the "targeturl" parameter get
> > set? I'd like to avoid putting a forwarding page on port 443 of the
> > exposed server to the appropriate signin page.
> >
> > Thanks,
> > Phil
> >