Resolving HTTPS MEX Endpoint Problem
I am sure there is something I am missing out here but I have no idea what.
In my STS Config, I have this:
<services>
<service name="Softwaremaker.Security.SecurityTokenService.SecurityTokenService" behaviorConfiguration="stsBehavior">
<endpoint contract="Softwaremaker.Security.SecurityTokenService.IWSTrust" binding="wsHttpBinding" bindingConfiguration="stsInfoCardBinding"
address="" />
<endpoint contract="IMetadataExchange" binding="mexHttpBinding" address="mex" />
</service>
My service metadata is set as follows:
<serviceMetadata httpsGetEnabled="True" httpsGetUrl="mex"/>
Once I point the Relying Party to the above STS:
<issuer address="http://swmvm2k3/DotNetProj/RSTSService/Service.svc">
</issuer>
<issuerMetadata address="https://swmvm2k3/DotNetProj/RSTSService/Service.svc/mex" />
and then point a svcutil to do retrieve the aggregated metadata from RP and STS, it throws me an error:
Attempting to download metadata from 'http://swmvm2k3:8000/SimpleSecurityService
' using WS-Metadata Exchange or DISCO.
Error: Obtaining metadata from issuer 'https://swmvm2k3/DotNetProj/RSTSService/S
ervice.svc/mex' failed with error 'System.InvalidOperationException: Metadata co
ntains a reference that cannot be resolved: 'https://swmvm2k3/DotNetProj/RSTSSer
vice/Service.svc/mex'. > System.ServiceModel.EndpointNotFoundException: There
was no endpoint listening athttps://swmvm2k3/DotNetProj/RSTSService/Service.sv
c/mex that could accept the message. This is often caused by an incorrect addres
s or SOAP action. See InnerException, if present, for more details. > System.
Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpCha
nnelRequest.WaitForReply(TimeSpan timeout)
End of inner exception stack trace
I have all my SSL certs and sites set up properly. I can browse to:https://swmvm2k3/DotNetProj/RSTSService/service.svc/mex and see the mex in the browser BUT somehow the endpoint/s:Action doesnt correspond.
The funny part is that when I change the issuerMetadata to:http://swmvm2k3/DotNetProj/RSTSService/Service.svc/mex (without the HTTPS endpoint), it resolves and works fine.
Therefore, I can safely say that the code is setup fine. What am I missing in the config setup ?
Thanks.
