The World Wide Web Consortium (W3C) recently conducted tests in August and September that impacted some agencies that use U.S. EPA’s Shared CROMERR Services (SCS). During these tests, the W3C redirected all internet traffic to its website to use the HTTPS protocol. While those tests have concluded for the time being, W3C indicates that it will eventually implement the change on a permanent basis. For additional information on the W3C’s recent testing, you may read entries in their blog here and here.
How does this impact users of SCS?
Some partner agencies experienced difficulties connecting to SCS during the W3C’s recent testing. This is because the Web Service Descriptor Language (WSDL) files for SCS include references to resources that are hosted on the W3C website. These references use the HTTP protocol instead of HTTPS. As a result, connectivity to SCS was interrupted for some agencies when the W3C redirected traffic to use HTTPS.
How will this issue be remedied?
U.S. EPA has revised the SCS WSDL files to use the HTTPS protocol. Testing indicates that this change resolves the connectivity issues with SCS. The updated WSDL files are available now in the SCS DEVELOPMENT and TEST environments (please see the URLs below). EPA plans to also deploy the changes to the SCS PRODUCTION environment on the evening of October 21, 2022.
- https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/IdentityProofingService2?wsdl
- https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/MessagingService?wsdl
- https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/SignatureAndCorService2?wsdl
- https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/SignatureService2?wsdl
- https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/IdentityProofingService?wsdl (limited support/deprecated)
- https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/SignatureAndCorService?wsdl (limited support/deprecated)
- https://encromerrdev.epacdxnode.net/shared-cromerr-ws/services/SignatureService?wsdl (limited support/deprecated)
- https://encromerrtest.epacdxnode.net/shared-cromerr-ws/services/IdentityProofingService2?wsdl
- https://encromerrtest.epacdxnode.net/shared-cromerr-ws/services/MessagingService?wsdl
- https://encromerrtest.epacdxnode.net/shared-cromerr-ws/services/SignatureAndCorService2?wsdl
- https://encromerrtest.epacdxnode.net/shared-cromerr-ws/services/SignatureService2?wsdl
- https://encromerrtest.epacdxnode.net/shared-cromerr-ws/services/IdentityProofingService?wsdl (limited support/deprecated)
- https://encromerrtest.epacdxnode.net/shared-cromerr-ws/services/SignatureAndCorService?wsdl (limited support/deprecated)
- https://encromerrtest.epacdxnode.net/shared-cromerr-ws/services/SignatureService?wsdl (limited support/deprecated)
What do I need to do?
U.S. EPA recommends that all agencies using Shared CROMERR Services test their use of the WSDLs and report any issues to either the Node Help Desk or Shared CROMERR Help Desk:
Exchange Network Help Desk
[email protected]
888-890-1995 ext 2
Shared CROMERR Help Desk:
[email protected]
888-890-1995 ext 2
Does this issue impact any other services or the Exchange Network?
At this time, there is no indication that other services or the Exchange Network will be impacted. EPA and its partners will continue to monitor and test for possible impacts. If your agency experiences any issues or has questions, please contact the Exchange Network Help Desk to report the problem.
Exchange Network Help Desk
[email protected]
888-890-1995 ext 2