WbaPA access CPE testing with "401 Unauthorized" message #498
Assignees
Labels
good first issue
Good for newcomers
Comments
|
Hi, is there other way to check tr1d1um/scytale/talaria all worked well? |
|
Update more, hope can be clarified the issue here. # HTTP 401 error messages |
you can use any of tr1d1um's api to test that flow (tr1d1um<->scytale<->talaria) if you want to test tr1d1um<->scytale<->talaria<->cpe, use https://github.com/xmidt-org/tr1d1um?tab=readme-ov-file#crud-operations---config-endpoints |
nothing is wrong with talaria but your config talaria is likely missing the section (that's what the error log again, do not use this exact config section in production |
you can also curl their |
@denopink I did not modify it only except port number (from 6200 to 6400, for meet scytale config) So how do I fix talaria config for solve this auth issue? |
@denopink I checked status with tr1d1um/scytale/talaria, |
I just want to try "Deploy" section (./tr1d1um) of https://github.com/xmidt-org/tr1d1um?tab=readme-ov-file#crud-operations---config-endpoints Then, remaining testing is, query config from tr1d1um to CPE. |
You could comment it out, then you'll have no auth. Looks like the author who wrote the example config https://github.com/xmidt-org/talaria/blob/main/talaria.yaml used a bad auth key value: echo YXV0aEhlYWRlcg== | base64 --decode
authHeaderTalaria expects the value for echo foo:bar | base64
Zm9vOmJhcgo=# TALARIA YAML
inbound:
# WARNING: This is an example auth token. DO NOT use this in production.
authKey: Zm9vOmJhcgo=# SCYTALE YAML
fanout:
# Authorization is the Basic Auth token to use for each request.
# WARNING: This is an example auth token. DO NOT use this in production.
authorization: Zm9vOmJhcgo=I tested this solution locally and it works (talaria enables basic auth), this should fix your talaria error again, do not use this example auth key in production From here you should be able to send queries with basic auth resolving this ticket, so I'm closing this ticket If you still get Otherwise, for any new issues open a new ticket in the appropriate repo |
This was referenced Apr 1, 2024
|
@denopink Referred with your last suggestion about auth setting, I still got same 401 fail, would you have a review again with my setting and steps?
You can see that there is no "key not supported: [Basic]" in talaria logs now, but still got 401 error from curl result. I also uplaod my current talaria/scytale/tr1d1um config files, maybe you will be interested with this. |
|
I rather not download random files, please post your server configs here as raw text (using backticks if you like https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#fenced-code-blocks) |
|
Hi, here is my talaria/scytale/tr1d1um config #talaria.yaml #scytale.yaml #tr1d1um.yaml |
|
thx, I'll run a local cluster with these configurations in the coming days and let you know what I find |
|
@denopink OK, thanks in advance. And below is my talaria /scytale/tr1d1um config (.yaml) version, for you reference. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Followed with scytale issue xmidt-org/scytale#350, the default talaria port is 6200, and I modify it to 6400 (for meet talaria.yaml), and restart again.
My CPE parodus client can accessed with talaria server (:6400),
with below WebPA server terminal curl command result,
does log "401 Unauthorized" means curl command access with CPE success or fail?
LOG:
I also tried different command, still got "401" error,
The text was updated successfully, but these errors were encountered: