-
Bug
-
Resolution: Won't Do
-
Minor
-
7.0.z.GA
-
None
What problem/issue/behavior are you having trouble with? What do you expect to see?
It is possible to define the following without JBoss complaining:
<subsystem xmlns="urn:jboss:domain:security:3.0">
<security-domain name="mydomain" cache-type="Hugo">
[...]
Expected behavior is that JBoss complains about invalid value "Hugo" (e.g. throws an Exception, refuses to start,..)
According to the CLI, there are two valid options: default and infinispan
}
-----------------------
[standalone@localhost:9990 /] /subsystem=security/security-domain=other:read-resource-description
.. .. ..
.. .. ..
"attributes" => {"cache-type" => {
"type" => STRING,
"description" => "Adds a cache to speed up authentication checks. Allowed values are 'default' to use simple map as the cache and 'infinispan' to use an Infinispan cache.",
"expressions-allowed" => true,
"required" => false,
"nillable" => true,
"min-length" => 1L,
"max-length" => 2147483647L,
"allowed" => [
"default",
"infinispan"
],
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
}},
-----------------------
- clones
-
JBEAP-11955 [GSS](7.1.0) cache-type attribute of security-domain element accepts invalid values
- Closed
- is cloned by
-
JBEAP-12104 [GSS](6.4.x) cache-type attribute of security-domain element accepts invalid values
- Closed
- is incorporated by
-
JBEAP-13430 (7.0.z) Upgrade WildFly Core from 2.1.19 to 2.1.20
- Closed
- is related to
-
JBEAP-12842 (7.0.x) Adding a testcase in EAT for JBEAP-12052.
- Resolved