3 Replies Latest reply on Jan 23, 2017 5:38 AM by Martin Choma

    Setting up SSL for Application: No SSL Context available from security realm

    Aaron Alex Newbie



      My application needs to communicate to a third party service via SSL. Trying to setup by following the steps highlighted in 2.2.5 on the article How To Configure Server Security - Red Hat Customer Portal


      Below is a screengrab of the console output. Would appreciate if anyone can shed some light on specifically resolving this.




      Server: JBoss EAP 7.0.


      Windows PowerShell

      Copyright (C) 2012 Microsoft Corporation. All rights reserved.



      PS C:\Users\Administrator> C:\Sandbox\EAP-7.0.0\bin\jboss-cli.bat

      You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands


      [disconnected /] connect

      [standalone@localhost:9980 /] /core-service=management/security-realm=HTTPSRealm/:add

      {"outcome" => "success"}

      [standalone@localhost:9980 /] /core-service=management/security-realm=HTTPSRealm/server-identity= \

      > ssl:add(keystore-path=C:\DW\EAI\sp.keystore, \

      > keystore-relative-to=jboss.server.config.dir, \

      > keystore-password=123456, alias=ssl)


          "outcome" => "success",

          "response-headers" => {

              "operation-requires-reload" => true,

              "process-state" => "reload-required"



      [standalone@localhost:9980 /] /subsystem=undertow/server=default-server/https-listener=https:add( \

      > socket-binding=https, security-realm=HTTPSRealm)


          "outcome" => "failed",

          "failure-description" => {"WFLYCTL0080: Failed services" => {"jboss.undertow.listener.https" => "org.jboss.msc.servi

      ce.StartException in service jboss.undertow.listener.https: Failed to start service

          Caused by: java.lang.IllegalStateException: WFLYUT0079: No SSL Context available from security realm. Either the rea

      lm is not configured for SSL, or the server has not been reloaded since the SSL config was added."}},

          "rolled-back" => true,

          "response-headers" => {"process-state" => "reload-required"}


      [standalone@localhost:9980 /]