-
Bug
-
Resolution: Duplicate
-
Major
-
3.0.0.Beta13
-
None
- I am able to set both key-store and public-key attributes. However based on model they should be alternatives and thus only one of them should be allowed.
- Althought, key-store and certificate are configured as requires in model, validation does not work.
Seems it is caused by WFCORE-2317.
"public-key" => { "type" => STRING, "description" => "A public key in PEM Format. During validation, if a public key is provided, signature will be verified based on the key you provided here.", "expressions-allowed" => true, "required" => false, "nillable" => true, "alternatives" => [ "key-store", "certificate" ], "min-length" => 1L, "max-length" => 2147483647L }, "key-store" => { "type" => STRING, "description" => "A key store from where the certificate with a public key should be loaded from.", "expressions-allowed" => false, "required" => false, "nillable" => true, "alternatives" => ["public-key"], "requires" => ["certificate"], "capability-reference" => "org.wildfly.security.key-store", "min-length" => 1L, "max-length" => 2147483647L }, "certificate" => { "type" => STRING, "description" => "The name of the certificate with a public key to load from the key store.", "expressions-allowed" => true, "required" => false, "nillable" => true, "alternatives" => ["public-key"], "requires" => ["key-store"], "min-length" => 1L, "max-length" => 2147483647L }
- clones
-
JBEAP-10379 Elytron token-realm attributes validations
- Closed
- duplicates
-
WFCORE-2317 Nested attributes are not validated
- Resolved