Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

Commit

Permalink
Updated docs
Browse files Browse the repository at this point in the history
  • Loading branch information
jorritfolmer committed Jun 22, 2018
1 parent 2772ba3 commit 4a99437
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -580,6 +580,17 @@ Structured parameters like admin, clustering, auth need to be specified in valid

One caveat: you cannot specify the admin hash in JSON due to the dollar signs in the SHA512 hash. Even though the PE docs mention you should escape $ to prevent variable interpolation, this doesn't seem to work for values in JSON.

| Status | Statement | Reason
|------|-----|-----
| **Works** | `{"pass": "changemeagain"}` | Valid JSON
| Doesn't work | `{'pass': 'changemeagain'}` | Invalid JSON
| Doesn't work | `{pass: "changemeagain"}` | Invalid JSON
| Doesn't work | `{pass= "changemeagain"}` | Invalid JSON
| Doesn't work | `{"hash": "$6$MR9IJetc"}` | Valid JSON but $ causes variable interpolation
| Doesn't work | `{"hash": "\$6\$MR9IJetc"}` | Valid JSON but escaped $ causes PE webgui to interfere

If for one reason or another the PE web gui says "Converted to string" while you're entering JSON, you should assume your structured parameter to not be interpreted incorrectly.

## Splunk with ADFS

### Setup
Expand Down

0 comments on commit 4a99437

Please sign in to comment.