![]() ![]() Updated to maintain consistent version numbering with Okta Confluence Authenticator version 2.0.5. Okta now includes the version number of the plugin when redirecting users to Okta for further authentication. Support for adding Remember me cookie during JIRA logins.įix for new sessions not being created for Jira and Confluence apps when an already logged in user reauthenticates with a new SAML assertion OpenSaml library version has been updated to 3.2.0Įnhanced SP-initiated SAML flow and support for spUsers and spGroups to handle JIRA only users This release contains a fix for opensaml initialization in OSGi environment. This release contains a bug fix for SAML SP-initiated flows, to ensure that all supported URLs redirect to Okta. This release contains security fixes for Headers injection and Log injection, updates the library version for the dependencies: This release supports JIRA 8.22.2 plus bug fixes. Jira Service Management (formerly JIRA Service Desk): 4.20.20, 5.4.4, 5.7.0 Tested with these on‑premises versions (may also work with other versions) Support for Jira On-Premises app version 7.x.x and later Deep-links for Service Desk won't work for regular users. Jira Service Desk is only tested for user agents (Tech support). There's a known limitation for Okta authenticator integration with Jira Service Desk: Okta authenticator can't be configured to authenticate Customer Portal URLs. On a case-by-case base, Okta may investigate issues with new and untested minor release versions of the Jira Cloud or on-premises app. Such support would require Okta to test its Jira/Confluence on-premises authenticators with all major and minor releases of the Jira/Confluence Cloud and on-premises apps. ![]() Okta doesn't support the combined deployment of the Jira/Confluence Cloud and Jira/Confluence on-premises apps. If you experience any difficulties, Okta recommends that you switch to a newer version of the on-premises app and download and install the latest Okta Jira Authenticator ( Settings > Downloads). Your End of Life version of the Jira/Confluence on-premises app will continue to work with deprecated versions of the Okta toolkits. ![]() To determine when Atlassian plans to discontinue support for a specific version of a Jira or Confluence on-premises app, see the Atlassian Support End Of Life Policy page. Okta discontinued support for the JIRA on-premises toolkit version 2.0.0 in October 2017. They ended support for Jira 7.0.x in October 2017. Likewise, Okta will deprecate Okta toolkit versions that only support deprecated Jira/Confluence on-premises versions.įor example, Atlassian released Jira 7.0 in October 2015. Okta Customer Support won't investigate issues related to the Jira/Confluence on-premises versions that are classified as End of Life by Atlassian. 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-premises app versions that are more than two years old. Version 6.x.x and earlier Toolkit Support Deprecation Policy For older API versions compatible with Structure 2.x, see Previous API Versions.Current Okta Jira JAR authenticators (toolkits) allow customers to integrate with supported iterations of these versions of the Jira On-Premises (server) application: Structure API version 16.0.0 is the first public API version for Structure 3.x. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |