<HTML><BODY><p>The url where IdP will redirect user is specified in <span style="color:#a31515;">AssertionConsumerServiceURL </span>attribute of <span style="color:#a31515;">samlp:AuthnRequest</span> that SP sends to IdP. So you should check how the request is being generated on SP side. Also you have to add corresponding AssertionConsumerService element with the same Location attribute to SP metadata.<br></p><blockquote style="border-left:1px solid #0857A6; margin:10px; padding:0 0 0 10px;">Понедельник, 21 декабря 2015, 18:29 UTC от "David E. Newswanger" <David_Newswanger@berea.edu>:<br><br><div id=""><div class="js-helper js-readmsg-msg"><div><div id="style_14507226120000000104_BODY"><div style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;"><p>I recently installed a new service provider. When people go to login via HTTPS, the identity provider authenticates them and then redirects them using HTTP to the home page and they get a security warning saying "The information you have entered on this
page will be sent over an insecure connection and could be read by a third party." How do I configure my SP or IdP to redirect authenticated users using HTTPS?<br></p></div></div></div></div></div></blockquote><p>
<br> <br>Robo Burned<br></p></BODY></HTML>