![]() ![]() ![]() It did turn out to be a regression that could be solved by manually modifying the domains.Īs we continued to monitor for these errors, we also saw reports of the share credentials toggle not working. It was a little tricky to troubleshoot as the errors were somewhat inconsistent, and the timing of them also coincided with a Jira incident. We looped in our on-call engineering team internally when the "Client must be authenticated to access this resource." errors started to come in. We take stability very seriously, so I do want to at least share some additional context. Thanks for the feedback and it definitely makes sense that this wasn't a stable solution. Hi You can add an auth login component! This will allow end users of the app to initiate the auth process as needed. In the meantime, you can uncheck this setting (and follow the steps outlined in #1) in order to use the resource. We are working on a bug fix for this & are targeting end of this week or early next week for a fix. ![]() Please ensure your resource domain is in this format:Īnd also ensure that your queries are in the same domain format:Ģ) In addition to the above issue, there is a regression where the wrong callback url is being used for resources that have "Share credentials between users" checked ON. We are working on a bug fix for this, as it is very tedious, but in the meantime, you will also need to manually change the domain syntax in each of your app queries to match the cloud id syntax in the resource setup. Unfortunately, I have some new information that changing the domain in the resource page, isn't currently updating existing queries' domains. For anyone that is using the "." syntax for the Jira domain, we ask that you switch to the /ex/jira/ format, as described above. Thanks for your patience! I have some updates from our internal on-call engineering team.ġ). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |