Blank page when login for OAuth 2.0 Authorization

Carlos A_ López Ortín April 21, 2022

Hello, experts:

I'm back to a webpage project I started about 6 months ago. In that web, I connect my Jira user using Jira API, and read my issues list, their details and even send comments and read the worklog.

Now, with the scopes change, I can't do it anymore. As far as I know, the only thing I must do is to change old scopes with newer ones. Ok, this was my scopes string:

public readonly static string client_scopes = "read:jira-work%20read:jira-user%20write:jira-work";

This is my new scopes string:

public readonly static string client_scopes = "read:issue:jira%20write:issue:jira%20read:attachment:jira%20write:attachment:jira%20read:comment:jira%20" +
"write:comment:jira%20read:comment.property:jira%20read:field:jira%20read:field.default-value:jira%20"+
"read:field.option:jira%20read:field-configuration:jira%20read:field.options:jira%20read:issue-link:jira%20" +
"write:issue-link:jira%20delete:issue-link:jira%20read:issue-link-type:jira%20read:priority:jira%20" +
"read:issue.property:jira%20read:issue.remote-link:jira%20write:issue.remote-link:jira%20" +
"read:resolution:jira%20read:issue-details:jira%20read:issue-type:jira%20read:issue.watcher:jira%20" +
"read:issue-worklog:jira%20read:issue-field-values:jira%20read:issue-status:jira%20read:issue.changelog:jira%20" +
"read:issue-event:jira%20read:user:jira%20read:user.columns:jira%20read:label:jira%20read:project:jira%20" +
"read:project-category:jira%20read:issue.time-tracking:jira%20read:user.property:jira%20read:status:jira%20" +
"read:role:jira";

 

At first, I had an error message, telling me that I have to change scopes on my console page. Ok, done (why the deprecated scopes are shown by default, and the newer and mandatory ones are hidden by default?).

Then, I tried again and I got a blank page. Yes, my page redirects to auth.atlassian.com/authorize, I can log in (if I wasn't), and I log in correctly (because other tabs open with my user on atlassian), but it tries to load https://api.atlassian.com/oauth2/authorize/consent page and... blank. No info. No error... well, kind of. Pressing F12 on Chrome, I get this errors:

TypeError: this.analytics.sendScreenEvent is not a function
at e.value (consent.bundle.js:119)
at t.value (consent.bundle.js:73)
at Ha (consent.bundle.js:89)
at Ua (consent.bundle.js:89)
at Cs (consent.bundle.js:89)
at kc (consent.bundle.js:89)
at wc (consent.bundle.js:89)
at fc (consent.bundle.js:89)
at consent.bundle.js:89
at t.unstable_runWithPriority (consent.bundle.js:97)
is @ consent.bundle.js:formatted:33621
n.callback @ consent.bundle.js:formatted:34071
gi @ consent.bundle.js:formatted:31730
ls @ consent.bundle.js:formatted:33718
Sc @ consent.bundle.js:formatted:34818
t.unstable_runWithPriority @ consent.bundle.js:formatted:36108
Yo @ consent.bundle.js:formatted:31472
Ec @ consent.bundle.js:formatted:34615
fc @ consent.bundle.js:formatted:34353
(anonymous) @ consent.bundle.js:formatted:31501
t.unstable_runWithPriority @ consent.bundle.js:formatted:36108
Yo @ consent.bundle.js:formatted:31472
Qo @ consent.bundle.js:formatted:31497
Ko @ consent.bundle.js:formatted:31489
sc @ consent.bundle.js:formatted:34141
$c @ consent.bundle.js:formatted:35476
tu @ consent.bundle.js:formatted:35529
t.render @ consent.bundle.js:formatted:35760
window.__INIT_CONSENT_SCREEN__ @ consent.bundle.js:formatted:22707
(anonymous) @ consent?state=******************************************************************************************************************************************************************************************************************************************
consent.bundle.js:formatted:45214 Uncaught TypeError: this.analytics.sendScreenEvent is not a function
at e.value (consent.bundle.js:119)
at t.value (consent.bundle.js:73)
at Ha (consent.bundle.js:89)
at Ua (consent.bundle.js:89)
at Cs (consent.bundle.js:89)
at kc (consent.bundle.js:89)
at wc (consent.bundle.js:89)
at fc (consent.bundle.js:89)
at consent.bundle.js:89
at t.unstable_runWithPriority (consent.bundle.js:97)

So... has someone any clue what's wrong?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events