Add Support to configure API key
Issue #8
resolved
We're currently running into an issue where the banner is no longer appearing. Looking at the JS console window a 401 error is appearing. It seems to be an authentication error and if we pass in API key than it should begin working again. I don't know if it was required before but this is something that I just noticed.
http://doers.statuspage.io/api/authentication/
XMLHttpRequest cannot load https://XXXXX.statuspage.io/api/v2/summary.json. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://exampe.com' is therefore not allowed access. The response had HTTP status code 401.
Comments (9)
-
repo owner
-
reporter
It was coming from our forge.lmig.com URL. I just replaced the real values with dummy ones. Also it was from jira and bitbucket. Basically any tool where the plugin was installed.
-
repo owner
Why do you need an API key?
-
reporter
I was reading the docs and it mentioned that in order to request data from the API it required a valid API key. So I assumed it was needed based on the 401 error.
-
repo owner
Tucker talked to support last week, this is a new requirement they added. I cut a 1.3 release to add settings for API key.
-
repo owner
-
repo owner
1.3 adds support for API keys for private pages.
-
repo owner
- changed status to resolved
fix released to market
-
reporter
That was pretty quick. Thank you for getting it out there.
- Log in to comment
Can't support use of API KEYs because SP.io header doesnt allow pre-flight cross-origin requests.
What page are you calling, and from what domain? (error says exampe.com) But nothing we use at work should need an API key.