Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial configuration fails with KeyError on "accessToken" #882

Closed
Petapton opened this issue May 18, 2024 · 1 comment
Closed

Initial configuration fails with KeyError on "accessToken" #882

Petapton opened this issue May 18, 2024 · 1 comment

Comments

@Petapton
Copy link
Contributor

Petapton commented May 18, 2024

Describe the bug
The bring up phase fails with a KeyError. It looks for the "accessToken" attribute, but the returned object is
AP_IT_ESP{"session":REDACTED, returnCode":"NEED_AUTHORIZATION","token":REDACTED}

To Reproduce
Steps to reproduce the behavior:

  1. Just start a new instance and try to log in

Config file
Also happens on a new instance

Environment (please complete the following information):

  • OS: Ubuntu host running the official container image
  • e208 2022
  • v3.5.1
  • Log from http://server_address:port/log and browser console log
2024-05-18 13:19:29,117 :: INFO :: App version 3.5.1
2024-05-18 13:19:29,117 :: ERROR :: No config file
2024-05-18 13:19:29,118 :: WARNING :: Can't get language
2024-05-18 13:19:29,118 :: WARNING :: Can't get language
2024-05-18 13:19:29,429 :: INFO :: update_data
2024-05-18 13:19:29,452 :: INFO ::  * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
2024-05-18 13:19:30,469 :: INFO :: 172.17.0.1 - - [18/May/2024 13:19:30] "�[37mGET / HTTP/1.1�[0m" 200 -
2024-05-18 13:19:30,557 :: INFO :: 172.17.0.1 - - [18/May/2024 13:19:30] "�[37mGET /assets/99_custom_overides.css?m=1715881091.0 HTTP/1.1�[0m" 200 -
2024-05-18 13:19:30,558 :: INFO :: 172.17.0.1 - - [18/May/2024 13:19:30] "�[37mGET /assets/clientside.js?m=1715881091.0 HTTP/1.1�[0m" 200 -
2024-05-18 13:19:30,887 :: INFO :: 172.17.0.1 - - [18/May/2024 13:19:30] "�[37mGET /_dash-layout HTTP/1.1�[0m" 200 -
2024-05-18 13:19:30,887 :: INFO :: 172.17.0.1 - - [18/May/2024 13:19:30] "�[37mGET /_dash-dependencies HTTP/1.1�[0m" 200 -
2024-05-18 13:19:36,067 :: INFO :: 172.17.0.1 - - [18/May/2024 13:19:36] "�[37mPOST /_dash-update-component HTTP/1.1�[0m" 200 -
2024-05-18 13:19:36,068 :: INFO :: 172.17.0.1 - - [18/May/2024 13:19:36] "�[37mGET /_favicon.ico?v=2.17.0 HTTP/1.1�[0m" 200 -
2024-05-18 13:19:36,104 :: INFO :: 172.17.0.1 - - [18/May/2024 13:19:36] "�[37mGET /config_login HTTP/1.1�[0m" 200 -
2024-05-18 13:19:36,339 :: INFO :: 172.17.0.1 - - [18/May/2024 13:19:36] "�[37mGET /_dash-layout HTTP/1.1�[0m" 200 -
2024-05-18 13:19:36,340 :: INFO :: 172.17.0.1 - - [18/May/2024 13:19:36] "�[37mGET /_dash-dependencies HTTP/1.1�[0m" 200 -

Additional context
Looks like login APIs have changed.

@Petapton
Copy link
Contributor Author

Ok, I figured it out. No login API has changed.
It seems they made some modifications and needed privacy consents. The NEED_AUTHORIZATION means that apparently.
Solved by logging in the official app. There I was asked for privacy consents. Then logging back in PSACC was straightforward.
Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant