can't log into sso with developer subscription

[swheettaos]

I have tried with 2 different accounts .. both have the free developer subscription.. neither work..

in the bottom righthand corner I get two messages .. first is:

"Configuring redhat registry"

(which seems fine)

the second is:

"Activating Red Hat subscription"
APIError: Bad Request

I've gone as far as completely removing it from my MacOS system and completely reinstalling it. Nothing changes.

I was told this should work with my Free Redhat developer subscription.

[dgolovin]

Thank you for reporting it. I've seen this error through telemetry, but nobody reported it till now.
If you have Red Hat Registry configured successfully, that means you successfully logged into Red Hat SSO.

Would you add some more info:

1. OS?
2. Podman Desktop Version?
3. How old the accounts you're using? (sometimes older accounts have complications, because some features are not enabled by default)
4. Proxy configuration if any.
5. Can you provide a log from troubleshooting page?

[swheettaos]

OS? MacOS 15.3
Podman Desktop Version? Version 1.15.0 (1.15.0)
How old the accounts you're using? (sometimes older accounts have complications, because some features are not enabled by default): One is a few year old the other is less than 6 months
Proxy configuration if any.: no proxy
Can you provide a log from troubleshooting page? ok .. I grabbed this part of the log .. which I think is what you are looking for

main-[kind] kind extension is active
main-[kind] kind extension is active
main-[kind] kind extension is active
main-Activating extension (podman-desktop.kind) ended in 547 milliseconds
main-Activating extension (podman-desktop.kube-context) with max activation time of 20 seconds
main-[kube-context] starting extension kube-context
main-Activating extension (podman-desktop.kube-context) ended in 24 milliseconds
main-Activating extension (podman-desktop.kubectl-cli) with max activation time of 20 seconds
main-Activating extension (podman-desktop.kubectl-cli) ended in 154 milliseconds
main-Activating extension (podman-desktop.lima) with max activation time of 20 seconds
main-[lima] Could not find socket at /Users/stephenwheet/.lima/podman/sock/podman.sock
main-Activating extension (podman-desktop.lima) ended in 2 milliseconds
main-Activating extension (podman-desktop.podman) with max activation time of 20 seconds
main-[kind] kind extension is active
main-[podman] Error while pinging docker as podman Error: connect ENOENT /var/run/docker.sock
main-Activating extension (podman-desktop.podman) ended in 72 milliseconds
main-Activating extension (podman-desktop.registries) with max activation time of 20 seconds
main-Activating extension (podman-desktop.registries) ended in 1 milliseconds
main-[redhat-authentication] REDHAT_AUTH_URL: https://sso.redhat.com/auth/realms/redhat-external/
main-[redhat-authentication] KAS_API_URL: https://api.openshift.com
main-[redhat-authentication] CLIENT_ID: podman-desktop
main-Activating extension (redhat.redhat-authentication) with max activation time of 20 seconds
main-[redhat-authentication] starting redhat-authentication extension
main-Activating extension (redhat.redhat-authentication) ended in 4 milliseconds
main-PluginSystem: initialization done.
main-Autostarting podman-desktop.podman container engine
main-Skipping update for extension redhat.redhat-authentication because installed version 1.0.2 is greater or equal to latest available version 1.0.2
main-[kind] kind extension is active
main-Trying to watch routes on the kubernetes context named "default" but got a connection refused, retrying the connection in 2s. Error: HTTP-Code: 404 Message: Unknown API Status Code! Body: "404 page not found\n" Headers: {"audit-id":"12f251ba-7994-4b24-a538-1ed782b06b6f","cache-control":"no-cache, private","connection":"close","content-length":"19","content-type":"text/plain; charset=utf-8","date":"Tue, 31 Dec 2024 22:28:46 GMT","x-content-type-options":"nosniff","x-kubernetes-pf-flowschema-uid":"576ed936-c5c5-43e0-8482-01919cb40e47","x-kubernetes-pf-prioritylevel-uid":"b8d2e4f0-8d33-4e53-87fd-85e78ef6fc57"})
main-[podman] Error while pinging docker as podman Error: connect ENOENT /var/run/docker.sock
main-[podman] Podman extension: Autostarting machine podman-machine-default
main-Trying to watch routes on the kubernetes context named "default" but got a connection refused, retrying the connection in 2s. Error: HTTP-Code: 404 Message: Unknown API Status Code! Body: "404 page not found\n" Headers: {"audit-id":"f903da38-4221-4b69-bfa5-871eff225b73","cache-control":"no-cache, private","connection":"close","content-length":"19","content-type":"text/plain; charset=utf-8","date":"Tue, 31 Dec 2024 22:28:48 GMT","x-content-type-options":"nosniff","x-kubernetes-pf-flowschema-uid":"576ed936-c5c5-43e0-8482-01919cb40e47","x-kubernetes-pf-prioritylevel-uid":"b8d2e4f0-8d33-4e53-87fd-85e78ef6fc57"})
main-Engine does not have an API or a libpod API, returning empty array Podman
main-Trying to watch routes on the kubernetes context named "default" but got a connection refused, retrying the connection in 3s. Error: HTTP-Code: 404 Message: Unknown API Status Code! Body: "404 page not found\n" Headers: {"audit-id":"e14e78ed-9b0d-4ce1-aeab-fd7743e89db3","cache-control":"no-cache, private","connection":"close","content-length":"19","content-type":"text/plain; charset=utf-8","date":"Tue, 31 Dec 2024 22:28:50 GMT","x-content-type-options":"nosniff","x-kubernetes-pf-flowschema-uid":"576ed936-c5c5-43e0-8482-01919cb40e47","x-kubernetes-pf-prioritylevel-uid":"b8d2e4f0-8d33-4e53-87fd-85e78ef6fc57"})
main-Trying to watch routes on the kubernetes context named "default" but got a connection refused, retrying the connection in 3s. Error: HTTP-Code: 404 Message: Unknown API Status Code! Body: "404 page not found\n" Headers: {"audit-id":"12ede0ad-c6d4-4ebf-83c1-cce7eebc32d7","cache-control":"no-cache, private","connection":"close","content-length":"19","content-type":"text/plain; charset=utf-8","date":"Tue, 31 Dec 2024 22:28:53 GMT","x-content-type-options":"nosniff","x-kubernetes-pf-flowschema-uid":"576ed936-c5c5-43e0-8482-01919cb40e47","x-kubernetes-pf-prioritylevel-uid":"b8d2e4f0-8d33-4e53-87fd-85e78ef6fc57"})
main-[redhat-authentication] Received /signin
main-[redhat-authentication] https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/auth?client_id=podman-desktop&scope=openid%20id.username%20email%20api.console%20api.iam.registry_service_accounts&response_type=code&redirect_uri=http%3A%2F%2Flocalhost%3A49843%2Fsso-redhat-callback&resource=https%3A%2F%2Fapi.openshift.com&code_challenge=DyvwZzB5lhJs792q8i0xqqK4Q2qy4oTQA-IS89H9r_8&code_challenge_method=S256&nonce=5F4fVzZZLQBYcOm5FJurf3ugNYdgnBHMV_oinoPX6Ps
main-[redhat-authentication] Received /sso-redhat-callback
main-[redhat-authentication] Received /
main-[redhat-authentication] Received /auth.css
main-Trying to watch routes on the kubernetes context named "default" but got a connection refused, retrying the connection in 4s. Error: HTTP-Code: 404 Message: Unknown API Status Code! Body: "404 page not found\n" Headers: {"audit-id":"08cd66be-2287-4052-a88c-3d15c46b483f","cache-control":"no-cache, private","connection":"close","content-length":"19","content-type":"text/plain; charset=utf-8","date":"Tue, 31 Dec 2024 22:28:56 GMT","x-content-type-options":"nosniff","x-kubernetes-pf-flowschema-uid":"576ed936-c5c5-43e0-8482-01919cb40e47","x-kubernetes-pf-prioritylevel-uid":"b8d2e4f0-8d33-4e53-87fd-85e78ef6fc57"})
main-[redhat-authentication] Received /favicon.ico
main-url podman-desktop:// does not start with podman-desktop:extension/, skipping.
main-[kind] kind extension is active
main-Engine does not have an API or a libpod API, returning empty array Podman
main-Trying to watch routes on the kubernetes context named "default" but got a connection refused, retrying the connection in 5s. Error: HTTP-Code: 404 Message: Unknown API Status Code! Body: "404 page not found\n" Headers: {"audit-id":"3a2d9df2-128a-47e3-a473-7c9f4187ab15","cache-control":"no-cache, private","connection":"close","content-length":"19","content-type":"text/plain; charset=utf-8","date":"Tue, 31 Dec 2024 22:29:00 GMT","x-content-type-options":"nosniff","x-kubernetes-pf-flowschema-uid":"576ed936-c5c5-43e0-8482-01919cb40e47","x-kubernetes-pf-prioritylevel-uid":"b8d2e4f0-8d33-4e53-87fd-85e78ef6fc57"})
main-[podman] Can't get machine podman-machine-default resource usage error Error: no running provider for the matching container
main-Trying to watch routes on the kubernetes context named "default" but got a connection refused, retrying the connection in 6s. Error: HTTP-Code: 404 Message: Unknown API Status Code! Body: "404 page not found\n" Headers: {"audit-id":"9b445f26-4f08-4b33-ac69-4c5c387a22c7","cache-control":"no-cache, private","connection":"close","content-length":"19","content-type":"text/plain; charset=utf-8","date":"Tue, 31 Dec 2024 22:29:06 GMT","x-content-type-options":"nosniff","x-kubernetes-pf-flowschema-uid":"576ed936-c5c5-43e0-8482-01919cb40e47","x-kubernetes-pf-prioritylevel-uid":"b8d2e4f0-8d33-4e53-87fd-85e78ef6fc57"})
main-Trying to watch routes on the kubernetes context named "default" but got a connection refused, retrying the connection in 8s. Error: HTTP-Code: 404 Message: Unknown API Status Code! Body: "404 page not found\n" Headers: {"audit-id":"323f158b-33a7-40c6-acb7-be018b99da01","cache-control":"no-cache, private","connection":"close","content-length":"19","content-type":"text/plain; charset=utf-8","date":"Tue, 31 Dec 2024 22:29:12 GMT","x-content-type-options":"nosniff","x-kubernetes-pf-flowschema-uid":"576ed936-c5c5-43e0-8482-01919cb40e47","x-kubernetes-pf-prioritylevel-uid":"b8d2e4f0-8d33-4e53-87fd-85e78ef6fc57"})
main-[redhat-authentication] Executing: podman machine ssh podman-machine-default sudo subscription-manager unregister
main-[redhat-authentication] Subscription manager unregister failed. Command execution failed with exit code 1: Command execution failed with exit code 1 stdout: stderr: This system is currently not registered.
main-Error: Command execution failed with exit code 1
main-Trying to watch routes on the kubernetes context named "default" but got a connection refused, retrying the connection in 10s. Error: HTTP-Code: 404 Message: Unknown API Status Code! Body: "404 page not found\n" Headers: {"audit-id":"f3686ab9-2991-461f-9d69-21dbffb188f3","cache-control":"no-cache, private","connection":"close","content-length":"19","content-type":"text/plain; charset=utf-8","date":"Tue, 31 Dec 2024 22:29:20 GMT","x-content-type-options":"nosniff","x-kubernetes-pf-flowschema-uid":"576ed936-c5c5-43e0-8482-01919cb40e47","x-kubernetes-pf-prioritylevel-uid":"b8d2e4f0-8d33-4e53-87fd-85e78ef6fc57"})
main-Trying to watch routes on the kubernetes context named "default" but got a connection refused, retrying the connection in 12s. Error: HTTP-Code: 404 Message: Unknown API Status Code! Body: "404 page not found\n" Headers: {"audit-id":"630e0995-8e1a-4a82-a27e-1c7deb905fd2","cache-control":"no-cache, private","connection":"close","content-length":"19","content-type":"text/plain; charset=utf-8","date":"Tue, 31 Dec 2024 22:29:30 GMT","x-content-type-options":"nosniff","x-kubernetes-pf-flowschema-uid":"576ed936-c5c5-43e0-8482-01919cb40e47","x-kubernetes-pf-prioritylevel-uid":"b8d2e4f0-8d33-4e53-87fd-85e78ef6fc57"})
main-[redhat-authentication] Received /signin
main-[redhat-authentication] https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/auth?client_id=podman-desktop&scope=openid%20id.username%20email%20api.console%20api.iam.registry_service_accounts&response_type=code&redirect_uri=http%3A%2F%2Flocalhost%3A49940%2Fsso-redhat-callback&resource=https%3A%2F%2Fapi.openshift.com&code_challenge=7UN_ZUd7sYKZLBy9zBqDmwdVU9ZIFGWLLZvxX5j3Sao&code_challenge_method=S256&nonce=ehjNGRG1xzZvr_1Wf0iOYdKMaGhc5yqK34Wa864aMP0
main-[redhat-authentication] Received /sso-redhat-callback
main-[redhat-authentication] Received /
main-[redhat-authentication] Received /auth.css
main-[redhat-authentication] Received /favicon.ico
main-Trying to watch routes on the kubernetes context named "default" but got a connection refused, retrying the connection in 12s. Error: HTTP-Code: 404 Message: Unknown API Status Code! Body: "404 page not found\n" Headers: {"audit-id":"e8acf224-654f-4504-9949-9dfd66cff0c0","cache-control":"no-cache, private","connection":"close","content-length":"19","content-type":"text/plain; charset=utf-8","date":"Tue, 31 Dec 2024 22:29:42 GMT","x-content-type-options":"nosniff","x-kubernetes-pf-flowschema-uid":"576ed936-c5c5-43e0-8482-01919cb40e47","x-kubernetes-pf-prioritylevel-uid":"b8d2e4f0-8d33-4e53-87fd-85e78ef6fc57"})
main-[redhat-authentication] Executing: podman machine ssh podman-machine-default sudo subscription-manager
main-url podman-desktop:// does not start with podman-desktop:extension/, skipping.
main-[redhat-authentication] Executing: podman machine ssh podman-machine-default sudo subscription-manager status
main-[redhat-authentication] Subscription manager subscription activation check returned exit code: 1
main-[redhat-authentication] Executing: podman machine ssh podman-machine-default sudo mkdir -p /etc/rhsm/facts/ && printf '{\n "supported_architectures": "aarch64,x86_64" }\n' | sudo tee /etc/rhsm/facts/podman-desktop-redhat-account-ext.facts
main-[redhat-authentication] Executing: podman machine ssh podman-machine-default sudo subscription-manager unregister
main-[redhat-authentication] Subscription manager unregister failed. Command execution failed with exit code 1: Command execution failed with exit code 1 stdout: stderr: This system is currently not registered.
main-Error: Command execution failed with exit code 1

[dgolovin]

@swheettaos thank you for update.

It seems 'APIError: Bad Request` was a temp error, could be because some of the API urls weren't accessible at the time.

I can see you tried to login once. It seems to be done right after podman desktop started and it seems podman was not auto started yet, so subscription activation failed. Then on the second attempt it seems went couple steps further but failed to create facts file.

main-[redhat-authentication] Executing: podman machine ssh podman-machine-default sudo mkdir -p /etc/rhsm/facts/ && printf '{\n "supported_architectures": "aarch64,x86_64" }\n' | sudo tee /etc/rhsm/facts/podman-desktop-redhat-account-ext.facts

It should report exit code in this case, but it did not. I'll check it and report back if there is something required to be fixed.

What is your podman version? You can check it by running podman version in terminal.

[swheettaos]

OS? MacOS 15.3
Podman Desktop Version? Version 1.15.0 (1.15.0)

[swheettaos]

I tried it several times alway gets the error and it doesn't show me as logged in as far as I can tell

[dgolovin]

Podman Desktop Version? Version 1.15.0 (1.15.0)

what is podman version?

[swheettaos]

DOH!! sorry man .. ya it's v5.3.1

[dgolovin]

@swheettaos

Did you select virtualization provider GPU Enabled (LibKrun) when creating Podman VM?

[swheettaos]

I don’t remember. Should I have? I can redo the vm if need be. Is it default?

[dgolovin]

It is not default, but it is the only way I can replicate the issue.

[swheettaos]

I’ll rebuild and try. Can we not use the gpu feature? Stephen

…

________________________________ From: Denis Golovin ***@***.***> Sent: Monday, January 13, 2025 6:16:48 PM To: redhat-developer/podman-desktop-redhat-account-ext ***@***.***> Cc: swheettaos ***@***.***>; Mention ***@***.***> Subject: Re: [redhat-developer/podman-desktop-redhat-account-ext] can't log into sso with developer subscription (Issue #506) It is not default, but it is the only way I can replicate the issue. — Reply to this email directly, view it on GitHub<#506 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM3C4EPZPGDAXH66TMCAPDL2KRXRBAVCNFSM6AAAAABUZBXBLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBYGY4DGNRYGM>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[dgolovin]

Default value for Provider type when you creating new machine is 'Apple Hypervisor' and when I use default SSO Login works.

[dgolovin]

But the errors in the log are different for me. But I am on macOS 15.2. You seems to be using macOS 15.3 Beta stream. Is that correct?

[swheettaos]

Ya. Had to switch to beta to fix a display port issue causing lockup on my Mac. Which it did. Stephen

…

________________________________ From: Denis Golovin ***@***.***> Sent: Monday, January 13, 2025 6:30:27 PM To: redhat-developer/podman-desktop-redhat-account-ext ***@***.***> Cc: swheettaos ***@***.***>; Mention ***@***.***> Subject: Re: [redhat-developer/podman-desktop-redhat-account-ext] can't log into sso with developer subscription (Issue #506) But the errors in the log are different for me. But I am on macOS 15.2. You seems to be using macOS 15.3 Beta stream. Is that correct? — Reply to this email directly, view it on GitHub<#506 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM3C4EIEQTCJ6HVXBI3HZ7D2KRZEHAVCNFSM6AAAAABUZBXBLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBYG4ZTMOBYGE>. You are receiving this because you were mentioned.Message ID: ***@***.***>