Obsolete JNDI setting should return Error and stop service

Description

Following config is obsolete.

  • Ensure the service fails to start if any of these are specified.

  • Ensure the release notes indicate that changes are required to current deployments.

Environment

None

Activity

Show:
Patrick Huang
November 29, 2016, 1:38 AM
Edited

To test it in dev environment:

  • $docker exec -it zanata bash #(this will connect to running zanata docker container)

  • $wildfly/bin/jboss-cli.sh

    1. inside container, launch jboss cli to add JNDI bindings

  • type following inside jboss cli console. Last command will restart the server

    • connect

    • /subsystem=naming/binding=java\:global\/zanata\/security\/auth-policy-names\/internal:add(value="zanata.internal",binding-type=simple)

  • reload

Assignee

Patrick Huang

Reporter

Ding-Yi Chen

Labels

Tested Version/s

None

Sprint

None

Fix versions

Affects versions

Priority

Highest
Configure