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

First developer login with GitHub leads to 403 Forbidden #1066

Open
3 tasks done
rustyjux opened this issue Jun 11, 2024 · 0 comments
Open
3 tasks done

First developer login with GitHub leads to 403 Forbidden #1066

rustyjux opened this issue Jun 11, 2024 · 0 comments
Labels
bug Something isn't working jira

Comments

@rustyjux
Copy link
Contributor

API Services Portal Issue

The first time (only?) a user logs in with a GitHub account, they are directed to:
image

Console shows:

Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-iSYegxzDyHTUnoy2QuvcGAH0Tb/CyB9ZY22CqSvyhAs='), or a nonce ('nonce-...') is required to enable inline execution.

There is an easy workaround from the 403 Forbidden page when using GitHub developer login:

  • On the 403 page, click Go back
  • Proceed to try and login again (Login > Developer > Login with GitHub)

This should lead to successful login with the GitHub account. Similarly, subsequent attempts to login with the GitHub account seem to avoid the 403 error.

ENV

  • DEV
  • TEST
  • PROD
@rustyjux rustyjux added bug Something isn't working jira labels Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working jira
Projects
None yet
Development

No branches or pull requests

1 participant