All m-->s transport binding scenario fails with : The remote certificate is invalid according to the validation procedure

Scenario
========
Scenario_1_IssuedTokenOverTransport_UsernameOverTransport-m2s
Scenario_7_IssuedTokenOverTransport_UsernameOverTransport-m2s

Setup
=====
metro 2.0.1
glassfish v3

Comment
========
This is little old issue probably, cert config in mmc is not correct need to
look into the configuration.

Error Log
========
LOG for Scenario_1_IssuedTokenOverTransport_UsernameOverTransport
Response recieved by the MS client from the Sun service endpoint
Getting test parameters
FederatedService_Endpoint_Address =
[https://ejp5359-vm1.india.sun.com:443/Security_Federation_FederatedService_Indigo/Symmetric.svc/Scenario_1_IssuedTokenOverTransport_UsernameOverTransport](https://ejp5359-vm1.india.sun.com:443/Security_Federation_FederatedService_Indigo/Symmetric.svc/Scenario_1_IssuedTokenOverTransport_UsernameOverTransport)
SecurityTokenService_Endpoint_Address = [https://129.158.229.79:8181/jaxws-s1-sts/sts](https://129.158.229.79:8181/jaxws-s1-sts/sts)
System.ServiceModel.Security.SecurityNegotiationException: Could not establish
trust relationship for the SSL/TLS secure channel with authority
'129.158.229.79:8181'. ---> System.Net.WebException: The underlying connection
was closed: Could not establish trust relationship for the SSL/TLS secure
channel. ---> System.Security.Authentication.AuthenticationException: The remote
certificate is invalid according to the validation procedure.
at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken
message, AsyncProtocolRequest asyncRequest, Exception exception)
at
System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken
message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count,
AsyncProtocolRequest asyncRequest)
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[2.0]

Source: [https://github.com/javaee/metro-wsit/issues/1384](https://github.com/javaee/metro-wsit/issues/1384)
Author: glassfishrobot

Start with the Scenario_1_IssuedTokenOverTransport_UsernameOverTransport-m2s and Scenario_7_IssuedTokenOverTransport_UsernameOverTransport-m2s configurations and reproduce the SSL/TLS failure against the listed SecurityTokenService endpoint. Review the Metro 2.0.1 and GlassFish v3 certificate setup; done means both scenarios establish the secure channel without the remote-certificate validation error.

Written by the indexing model from the issue text.