Okta Confluence Authenticator Version History
Toolkit Support Deprecation Policy
In alignment with the Atlassian support End of Life policy, beginning July 15, 2017 Okta will discontinue toolkit support for all versions of the JIRA and Confluence on-premise appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in. versions that are more than two years old. When Atlassian discontinues support for a given version of the app, Okta Customer Support will no longer investigate issues related to the JIRA/Confluence on-premise versions that are classified as End of Life Status by Atlassian. Likewise, Okta will deprecate Okta toolkit versions that only support deprecated JIRA/Confluence on premise versions.
For example, since Atlassian released JIRA 7.0 in October 2015, they will end of life support for JIRA 7.0.x in October 2017. Accordingly, Okta will discontinue support for the JIRA on-premise toolkit version 2.0.0 in October 2017.
To determine when Atlassian plans to discontinue support for a specific version of a JIRA or Confluence on-premise app, see the Atlassian Support End Of Life Policy page.
Your End of Life version of the JIRA/Confluence on-premise app will continue to work with deprecated versions of the Okta toolkits. However, if you experience any difficulties, Okta strongly recommends that you (1) switch to a newer version of the on premise app, and (2) download and install the latest SAMLAn acronym for Security Assertion Markup Language, SAML is an XML-based standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP). The SAML standard addresses issues unique to the single sign-on (SSO) solution, and defines three roles: the end user, the IdP, and the SP. Here's how SAML works through Okta: SP-initiated flow: the end user requests (principally through a browser) a service from the SP. The SP requests and obtains an identity assertion from the IdP (in this case, Okta). On the basis of this assertion, the SP can decide whether or not to authorize or authenticate the service for the end user. IdP-initiated flow: with Okta as the IdP, an end user goes to the Okta browser and clicks on an app, sending a SAMLResponse to the configured SP. A session is established with the SP, and the end user is authenticated. toolkit and necessary toolkit from the Dashboard (Settings > Downloads).
Okta does not support the combined deployment of the JIRA/Confluence Cloud and JIRA/Confluence on-premise apps. Such support would require Okta to test its JIRA/Confluence on-prem authenticators with all major and minor releases of the JIRA/Confluence Cloud and on-premise apps. On a case-by-case base, Okta may investigate issues with new and untested minor release versions of the JIRA Cloud or on-premise app.
|Current GA Version||3.1.2|
|Current EA Version||N/A|
|Toolkit Version||Tested with these on‑premise Confluence Versions (may also work with other versions)||Description||Release|
|3.1.2||5.9.3, 6.0.1, 6.1.1, 6.2.2, 6.3.0, 6.3.2, 6.4.0, 6.4.2, 6.4.3, 6.14.0, 7.0.2, 7.0.4||This release contains a fix for OpenSaml initialization in OSGi environment and update to OpenSaml library version 3.2.0.||2019.12.0|
|3.0.6||5.9.3, 6.0.1, 6.1.1, 6.2.2, 6.3.0, 6.3.2, 6.4.0, 6.4.2, 6.4.3||
Support for adding Remember me cookie during JIRA logins.
Fix for new sessions not being created for Jira and Confluence apps when an already logged in user re-authenticates with a new SAML assertion.
SPAn acronym for service provider. Generally, an SP is a company, usually providing organizations with communications, storage, processing, and a host of other services. Within Okta, it is any website that accepts SAML responses as a way of signing in users, and has the ability to redirect a user to an IdP (e.g., Okta) to begin the authentication process.-initiated flows are disabled for Confluence users that are not present in Okta.
|3.0.5||5.9.3, 6.0.1, 6.1.1, 6.2.2, 6.3.2, 6.4.0, 6.4.2, 6.4.3||We now include the version number of the plugin when redirecting users to Okta for further authentication.||2017.45|
|2.0.5||5.9.1, 5.9.8, 5.9.3, 6.0.1, 6.1.1, 6.1.2||This version adds support for custom base URLs (for example, http://confluence.onprem.com/my-confluence).||2017.21|
|2.0.4||5.9.1, 5.9.8, 5.9.3, 6.0.1, 6.1.1||Provides improved security.||2017.19|
|2.0.3||6.0.1, 5.9.8, 5.9.1||Confirms support for on-prem version 6.0.1.||2016.49|
|2.0.3||5.9.8, 5.9.1||Updated to maintain consistent version numbering with Okta's JIRA On-Prem Authenticator version 2.0.3.||2016.45|
|1.0.13||5.9.8, 5.9.1||Confirms support for on-prem versions 5.9.1 and 5.9.8.||2016.17|