Making a EJB3 web service over accessible via HTTPS on JBoss

Solution Verified - Updated -

Issue

  • How can an EJB3 web service be marked so that it is only available via HTTPS and not HTTP? It already has
    @WebContext(authMethod = "BASIC", secureWSDLAccess = true)

  • If using @WebService(wsdlLocation="META-INF/wsdl/Example.wsdl") on the implementation class and packaging the imported schemas along with WSDL, it works. However, the schema locations are rewritten as http. Since only https access is allowed to external clients, the concern is that they may not be able to access these xsds. What is the workaround for this?

  • How to change the URL in the soap:address element in WSDL to use https even when using the AJP or HTTP connector? The JBoss instances are load-balanced, and the load balancer handles the SSL.

  • JBoss allows to change the location host and port in the auto generated WSDL file through the JBossws.sar deployer, however, JBoss does not allow for a way to indicate in the soap:address node so that the connection the client uses is HTTPS and not HTTP.

  • Webservice installed on Jboss EAP 6.2.4 is available over http 8080 port but when trying to access web service on https 8443 it is not accessible. Are any additional settings required from Jboss end?

  • How to access web services via SSL?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 4.x
    • 5.x
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.