-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
Steps to reproduce:
- Change default realm name to a different one
- Update endpoint to point to a correct name
- Create a user
- Attempt to execute a request
$ curl --digest -u admin:admin http://localhost:11222/rest/v2/caches -i HTTP/1.1 401 Unauthorized WWW-Authenticate: Digest realm="custom", nonce="AAAAAQAAAi7ZDm0qIzaxrckAqj2qsx/2cSdHHjoNwP6z35mQlMx3/HgBDf0=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth content-length: 0 HTTP/1.1 401 Unauthorized WWW-Authenticate: Digest realm="custom", nonce="AAAAAgAAAi7aSR14m/6hpbcuO9egiD5nilFacTDsghv4Q9xGKyqgLfJz9PY=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth content-length: 0
- is cloned by
-
ISPN-16339 Document how the realm name affects user properties encryption
- Resolved