Self hosted (datacenter)
I tried to connect my outlook calendar to Jira Assistant extension. After checking on the check box and clicking on the link "Click here to sign in with your Microsoft account". I am getting the following website. I think that the there is issue with the redirect URL "https://jiraassistant.com/oauth/outlook"
PS: There is an open issue with Google calendar integration (https://github.com/shridhar-tl/jira-assistant/issues/155) (Mostly unrelated).
It looks like the request is going to the Microsoft Online Server properly
It returns the access token to the specified URL, which is permanently moved (301).
And then finally, it is not able to find the new location webpage, because of which we are getting page not found (404)
As I stated earlier, it looks like a redirect URL issue. I cannot find the location of the webpages hosted on the website and this redirect URL location in the repository.
Hi @irahhari , This issue has been resolved and is published to Web version. It would take up to a weeks time for publishing the changes to extension users. You can once use the web version to integrate with calendar and then continue to use extension.
Using web version is simple and do not store any data outside of your browser cache similar to that of your extension.
You can know more about web version from the following url: https://app.jiraassistant.com/?authType=1
Closing this ticket considering this issue is resolved. Please feel free to reopen it or create a new ticket in case of any other issues.
Thanks, @shridhar-tl. It is working now. I am able to integrate using the web version and use the extension later.
Just a few updates on the extension version. Now, suppose I try to integrate using the extension version. In that case, I am getting this "AADSTS50011: The redirect URI 'https://www.jiraassistant.com/oauth/outlook' specified in the request does not match the redirect URIs configured for the application 'a8efd8fc-0657-490e-a622-7b2aaa4f4f46'. Make sure the redirect URI sent in the request matches one added to your application in the Azure portal. Navigate to https://aka.ms/redirectUriMismatchError to learn more about how to fix this."
This looks like in the app you have registered with Microsoft, the redirect URL specified and the redirect URL sent with the request are different. You had mentioned that it would take weeks to fix in the extension version, which I understand, as Microsoft has to update it.
But how is it working for the web version? If the web version is also sending requests under the same application ID, then it would take weeks to fix the issue in the web version also. If the web version has a different application ID, wouldn't that also take weeks to update from Microsoft?
@irahhari - I know it doesn't work on extension currently and the exact error as well. If you just thought of giving an update, thank you for that. But just in case if there are some mis understanding, let me try to clarify that:
Currently the fix is only available in Web version. Though for extension, source code is same, for me to publish the change, it would take a week or 10 days. This is due to the fact that web store has to review the code before publish.
Hence extension still do not have latest code. So directly integrating on extension will not work until your extension gets updated to v2.56 which may take time depending on browsers.
As I had to publish the changes for individual browsers and each webstore takes its own time for review process, I cannot immediately push the changes. I had to do a round of testing with each browser and then manually publish it for each web store and then their review takes time.
As I cannot cover testing all the cases each time I publish and due to these process related delays, I request extension users to have the extension installed (as it would add more features like using browser session for authentication and backup just in case if web version breaks) and use web version to have latest changes.
So users come across issues and reports them before it gets published to extension so that I can fix it quickly and users also have a stable extension version as backup. The more users use web version, the extension becomes more stable.
You can learn more about web version here: https://jiraassistant.com/why-web-version/
Thank you @shridhar-tl, for the detailed explanation and clearing the confusion.
@irahhari - Already v2.56 published for Chrome, Firefox and Opera. Edge is still under review and it would be published by next week. If you want to update to latest version of extension, you can do so by going to "chrome://extension", enable dev mode from top right corner and then click on update button from top left corner. That would get your extension updated to latest available version.