Authorization flow / Failed to fetch objects: undefined / proxy

[ThierryIT]

Describe the bug When created a provider proxy, it is not possible for me to have the explicit authorization flow, instead, I do have a Failed to fetch objects: undefined

To Reproduce Steps to reproduce the behavior:

1. Go to 'new provider'
2. Click on 'authorization flow'
3. Scroll down to 'Failed to fetch objects: undefined '
4. See error

Expected behavior explicit authorization flow

Screenshots If applicable, add screenshots to help explain your problem.

Logs Output of docker-compose logs or kubectl logs respectively

Version and Deployment (please complete the following information):

• authentik version: [2024.4.1]
• Deployment: [docker / fresh install / VM proxmox]

Additional context Add any other context about the problem here.

[ThierryIT]

When in Dashboard/Overview I do have:

• Outpost status: Failed to fetch data.
• Workers: Failed to fetch data.
• Systems status: Failed to fetch data.

few logs:

`INF auth_via=session domain_url=authentik.domain.tld event=/api/v3/crypto/certificatekeypairs/?has_key=true&include_details=false&ordering=name host=authentik.domain.tld logger=authentik.asgi method=GET pid=54 remote=ip_number request_id=7035982d0ff944c08cd93a09a5fe7dc0 runtime=193 schema_name=public scheme=https status=200 timestamp=2024-05-05T15:26:40.040677 user=login_name user_agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 INF auth_via=unauthenticated domain_url=0.0.0.0 event=/-/health/live/ host=0.0.0.0:9000 logger=authentik.asgi method=HEAD pid=54 remote=127.0.0.1 request_id=f331d5e945c64188bb83fd8471a76b7a runtime=43 schema_name=public scheme=http status=204 timestamp=2024-05-05T15:26:40.738155 user= user_agent=goauthentik.io/healthcheck INF domain_url=null event=/ws/client/ logger=authentik.asgi pid=53 remote=172.69.151.58 schema_name=public scheme=ws timestamp=2024-05-05T15:26:41.267880 user_agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 warning error=context canceled event=failed to proxy to backend logger=authentik.router timestamp=2024-05-05T15:26:41Z warning error=context canceled event=failed to proxy to backend logger=authentik.router timestamp=2024-05-05T15:26:41Z INF auth_via=session domain_url=authentik.domain.tld event=/api/v3/flows/instances/?designation=authorization&ordering=slug host=authentik.domain.tld logger=authentik.asgi method=GET pid=53 remote=ip_number request_id=1f5c4ea0fa5642209bae733ad5079eb9 runtime=3333 schema_name=public scheme=https status=200 timestamp=2024-05-05T15:26:43.054396 user=login_name user_agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 INF auth_via=session domain_url=authentik.domain.tld event=/api/v3/flows/instances/?designation=authentication&ordering=slug host=authentik.domain.tld logger=authentik.asgi method=GET pid=53 remote=ip_number request_id=4b01830ab9534739825a8c9a2ca969aa runtime=3487 schema_name=public scheme=https status=200 timestamp=2024-05-05T15:26:43.328836 user=login_name user_agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 INF domain_url=null event=/ws/client/ logger=authentik.asgi pid=53 remote=172.69.151.212 schema_name=public scheme=ws timestamp=2024-05-05T15:26:44.624331 user_agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36

  `

[ThierryIT]

[ThierryIT]

So I have done some tests on different version:

2024.4 -> flow pb 2024.4.0 -> flow pb 2024.2.0 -> Authentification flow: loading .... (nothing else) -> Authorization flow: same 2023.10.7 -> working

[authentik-automation[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.