-
Bug
-
Resolution: Done
-
Blocker
-
8.0.0.GA-CR1, 8.0.0.GA-CR2
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
-
The http-authentication-factory mechanism configuration is not fully persisted when configuring a security domain with a certificate authentication cache type.
According to the installer sources and runtime information the following CLI operation is executed:
{ "operation" => "add", "address" => [ ("subsystem" => "elytron"), ("http-authentication-factory" => "testDomain-certHttpAuth") ], "http-server-mechanism-factory" => "global", "security-domain" => "testDomain", "mechanism-configuration" => [{ "mechanism-name" => "CLIENT_CERT", "mechanism-realm-configurations" => [{"realm-name" => "testDomain"}] }] }
Although the following is what is persisted into e.g.: standalone.xml:
<http-authentication-factory name="testDomain-certHttpAuth" security-domain="testDomain" http-server-mechanism-factory="global"/>
- clones
-
JBEAP-25548 The "(Users|Group) properties file" text box ("Security Domain Configuration" screen -> Cache type: Property File) is not validated against empty/blank string
- Closed
- is cloned by
-
JBEAP-25706 The "Security Domain/Cache type: Database" password encryption configuration is not persisted when selecting base64 encoding
- Closed
- relates to
-
WFLY-18800 Misleading example in "Configure Authentication with Certificates" section of Elytron security doc
- Closed
- split to
-
JBEAP-26161 [GUI Installer] Certificate security configuration creates unnecessary configuration
- Closed