You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When running aem up with an authenticated site the auth flow never successfully completes if your default browser is safari. When clicking send on the prompt page, an error occurs which is only surfaced via the dev console.
To Reproduce
Steps to reproduce the behavior:
make safari your default browser (my setup: safari 18.3 on Mac OS 15.3.1)
run aem up for an authenticated site with no stored site token
login with the IdP
when you arrive at https://admin.hlx.page/auth/adobe/ack?code=... click send
note that nothing happens
open dev tools console and note the error
Expected behavior
The auth flow should complete successfully. If that isn't possible due to some safari specific restriction, the user should see a message with some info on what they can do to work around.
Screenshots
errors from console:
[Warning] [blocked] The page at https://admin.hlx.page/auth/adobe/ack?code=.... requested insecure content from http://localhost:3000/.aem/cli/login/ack. This content was blocked and must (ack, line 7)
[Error] Not allowed to request resource
(anonymous function) (ack:7)
sendPost (ack:6)
(anonymous function) (ack:23)
[Error] Fetch API cannot load http://localhost:3000/.aem/cli/login/ack due to access control checks.
(anonymous function) (ack:7)
sendPost (ack:6)
(anonymous function) (ack:23)
[Error] Unhandled Promise Rejection: TypeError: Load failed
(anonymous function) (ack:7)
It looks like Safari is the only browser that very strictly enforces not making http calls from a secure https connection, even on localhost.
The other browsers treat localhost like a secure https connection.
Will probably need to switch the response from Helix Admin to transfer information via a redirect to localhost (assuming that's supported by Safari, will need to check).
But that has different security disadvantages, unless we use something like PKCE, which requires more effort to implement.
Will need to check what we can do...
Description
When running
aem up
with an authenticated site the auth flow never successfully completes if your default browser is safari. When clicking send on the prompt page, an error occurs which is only surfaced via the dev console.To Reproduce
Steps to reproduce the behavior:
aem up
for an authenticated site with no stored site tokenhttps://admin.hlx.page/auth/adobe/ack?code=...
click sendExpected behavior
The auth flow should complete successfully. If that isn't possible due to some safari specific restriction, the user should see a message with some info on what they can do to work around.
Screenshots
errors from console:
Version:
The text was updated successfully, but these errors were encountered: