-
Bug
-
Resolution: Done
-
Major
-
7.1.0.ER2
-
None
The hash-from attribute has a wrong decription in elytron subsystem. It wrongly suggests it's rather about function/algorithm name than a hash value.
[standalone@embedded /] /subsystem=elytron/ldap-realm=*:read-resource-description() ... "hash-from" => { "type" => STRING, "description" => "The name of the LDAP attribute of OTP hash function.", "expressions-allowed" => true, "required" => true, "nillable" => false, "min-length" => 1L, "max-length" => 2147483647L }, ...
The attribute should not talk about the hash function, but rather hash (or hash value).
Updated
The description has to also mention the value of the LDAP attribute is Base64 encoded.
- is cloned by
-
WFCORE-3066 Elytron subsystem - wrong description of ldap-realm.otp-credential-mapper.hash-from attribute
- Resolved
- is incorporated by
-
JBEAP-11931 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta30
- Closed
- relates to
-
JBEAP-12140 Elytron - OTP seed attribute in ldap-realm is Base64 encoded
- Closed