Hi,
After following the dcm4chee-arc 5.x tutorial, i ended up with 2 wildflys:
- one carrying dcm4chee-archive with ports:
<socket-binding name="http" port="${jboss.http.port:8080}"/>
<socket-binding name="https" port="${jboss.https.port:8443}"/>
<socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
<socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
- and one carrying keycloak app with ports:
<socket-binding name="http" port="${jboss.http.port:8880}"/>
<socket-binding name="https" port="${jboss.https.port:8843}"/>
<socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9980}"/>
<socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9983}"/>
When I access
http://localhost:9983 the wildfly page appears and when I press the login to administration console no user password is required and I am automatically logged as an anonymous user. Could this be a potential risk? How could I secure the wildfly access of the keycloak-side?
Kind regards.