jira-server integration does not support authentication via 3rd party authenticcation services (e.g. okta, microsoft auth...)
Jira Server version 8.22 or higher supports OAuth2 for incoming connections. The flow allows third party applications to make requests to the Jira Server on the user's behalf. Previous versions of Jira Server allowed only OAuth1.0a flow.
OAuth2 is the industry-standard protocol. Here is an example of documentation for it.
- Open the applications menu
- Open the application links menu
- Сreate a new incoming application link with these parameters
- Here's the value for the Redirect URL field to copy and paste it:
https://jira-api.integrations.asana.plus/setup/callback/jira
- Hit the "Save" button.
- The resulting page should look
- Don't close the page yet.
- Open the main setup page on the link https://jira-api.integrations.asana.plus/setup is a separate browser tab.
- Log in as Asana user, press "Allow".
- Log in would involve Asana OAuth process and should look
- Select an Asana workspace from
- Fill all the fields in the form like , use the values generated by Jira Server previously and press "Connect".
- Note that the Jira Server should be accessible from the internet. So if it's accessible only from a corporate network or via VPN, the integration won't work for now.
- It will start the Jira Server OAuth2 flow, press "Allow" button
- If everything is ok, you would be redirected to a page where the oauth2 process will finish.
- As a result, the current access and refresh tokens will be stored by the integration.
- As a user, you should see the screen .
- You could delete the connection that is stored by the integration, press "Remove" button.
- You could select another Asana workspace and use the same application link credentials if the Jira Server stays the same.
- A typo in the Jira Server url.
- Non-existing will be detected as "Not accessible" on save.
- Existing dns name visible from browser to the user but not accessible from other internet addresses are not supported for now.
- A typo in the client id.
- A typo in the client secret
- A typo in the callback