Fixed Jira 9 compatibility

Fixed Jira 9 compatibility

The previous version 4.0.0 caused a problem in instances using a MySQL database, resulting the list of OpenID providers not to be shown.

OpenID/ OAuth Authentication is now officially compatible with Data Center.

Please note that we removed OpenID 1.0 support as part of the changes for the data center approval. Read more about it here: https://wiki.resolution.de/doc/openid-oauth-authentication/4.0.0/release-notes

The previous version 4.0.0 caused a problem in instances using a MySQL database, resulting the list of OpenID providers not to be shown.OpenID/ OAuth Authentication is now officially compatible with Jira Data Center.Please note that we removed OpenID 1.0 support as part of the changes for the data center approval. Read more about it here: https://wiki.resolution.de/doc/openid-oauth-authentication/4.0.0/release-notes

Adjusted to changes for GitHub's API.

User creation is now only controlled by the setting in the app. Previously, user creation was blocked if "External User Management" was enabled in Jira.

Fixed Google failing randomly with IllegalArgumentException: XXXX.XXXX.XXXX not a valid Token

This version supports Jira 8.0.0 and above

No migration is needed, Google provider now uses Google Sign In API instead of Google+ API which is discontinued and scheduled to termination in March.

The plugin will now add user to all default applications.

3.2.0 were released without proxy support due to a bug in OLTU library, this release provides a fix.

This release fixes following bugs:

• don't require JWT token from custom providers
• when configuring a custom provider show that /.well-known/openid-configuration will be requested
• don't crash when a username is already taken
• fixed ClassCastException when handling JWT's Claim sets
• OpenID buttons missing from a login form that included an error (dashboard only)

This version brings:

• It is now posible to edit names of all providers
• You can set a scope for a custom provider
• Buttons will be visible even if you're logged in (reverted previous change)
• Custom provider doesn't fail if there is no user info endpoint available for a custom provider (as it's optional)

It will show login buttons on mobile login page as well.

• Fixed Facebook integration
• Will not try to endlessly bind to dashboard
• Will terminate immediately if a user is already signed in

Plugin will now issue a remember me cookie when user is authenticated.

Updated GitHub authentication to support new API changes.Fixed HTTP/404 with OpenID 1 authentication.

Better redirection handling to support reverse proxies.

You can select a prompt type (select account, consent screen or nothing).

Fixed parsing response from user info URL.

Added Jira 7.2 compatibility.

Better redirection handling to support reverse proxies.

Did you know that there's OpenID Authentication for Confluence too?

Fixed GitHub provider to work for users without a public email.

Did you know that there's OpenID Authentication for Confluence too?

Made the plugin work with Azure.

Fixed race condition for Login gadget extension.

Fixed bug that didn't allow to edit some of the properties.

When running on Jira 6.4.9 or newer plugin will extend Login dashboard item directly. No need to use OpenID gadget.

Added VK provider.

Changed UI to list all the providers.

Fixed dashboard widget.

Improved error reporting when Google+ API is disabled.

Fixed HTTP/405 Method not allowed when creating or saving a provider.

Added Facebook, Github and LinkedIn to supported authentication providers.

Bug fix: Login will redirect you to the page you were trying to access (instead of the dashboard).

Made the plugin work with Jira 6.1.

It's now possible to limit logins to selected Google Apps domains.

Other bug fixes.

Users accessing Jira using address different than configured base URL will now be correctly handled and logged in.

Changed format to OBR to fix initialization problems.

• You can now configure your own OpenID providers
• You can disable built-in providers (so you can force users to use only yours)
• Improved user interface to support more than two OpenID providers
• Fixed bugs causing user not to be logged in after the account was created

Initial release.