SecSignID Plugin Changelog for Atlassian

2018-04-06 5 minutes to read
Tutorial Index

2-Factor-Authentication with SecSignID for Atlassian Services

This changelog describes the latest improvements for the SecSignID 2-Factor-Authentication Plugins for Jira, Confluence, Crowd, Bitbucket and Bamboo

What’s new? Check out the newest features and updates of your SecSign ID integration with
Jira, Confluence, Crowd, Bamboo or Bitbucket


Jira

Jira Changelog

JIRA SecSignID PluginAtlassian Marketplace
JIRA - 3.0.42018-07-24

  • fixed problem with groupnames with special characters

JIRA - 3.0.32018-06-20

  • added option for JIRA servicedesk whether to use 2FA or not
  • bug fixes
  • code review
  • added changelog for SecSign ID addons

JIRA - 3.0.22018-06-14

  • added support for invitation signup
  • fixed signup redirect
  • fixed filter for navigation bar

JIRA - 3.0.12018-06-05

  • removed superfluous servlet filter to fix a bug when showing issues and displaying issues in Jira.

JIRA - 3.0.02018-06-01

  • Redesign of options and user mappings page
  • Fixed problems with captcha
  • Fixed problems with synchronizing with an Crowd instance
  • Fixed problems in local mappings users and SecSign ID

JIRA - 2.1.02018-04-04

  • updated login screen
  • new options to synchronize the ID mappings to Crowd


JIRA - 2.0.22018-01-30

  • Layout changes of options
  • Added description for IPv6 compatibility IPSafeZone

JIRA - 2.0.12018-01-11

  • Read the X-Forwaded-For header field for the check whether the caller is within the specified IP-range of the IPSafeZone.
  • Reading the remote address only will fail if a proxy or a reverse proxy exists between the JIRA system and the caller.

JIRA - 2.0.02017-12-11

  • Two-Step-Verification: the SecSignID add-on can now be used as a two-step-verification
  • IPSafeZone: the admin can specify ip-ranges to adjust who must login using two-factor-authentication or who is allowed to use username and password only
  • ID assignment: added the option that a user can assign a SecSign ID by himself when a SecSignID wasn’t assigned yet
  • added the option that the admin can specify whether it is allowed that a user changes his or her SecSignID
  • Minor bugfixes

JIRA - 1.1.22017-10-30

  • fixed bug in two step verification due to JIRA Api changes between version 6.x and 7.x

JIRA - 1.1.12017-10-27

  • Added option to run the SecSign ID add-on in a two-step authentication or verification mode.
    In the two-step-verfication mode the user will have to enter its credentials before he needs to accept the SecSign ID access pass on its smartphone.
     
    More information about the difference of two step verification and two factor authentication at secsign.com/two-factor-authentication-vs-two-step-verification

JIRA - 1.1.02017-09-12

  • Admin can disable password login system wide
  • Bug fixes handling usernames with uppercase characters
  • Bug fixes when Jira is using a Crowd directory
  • Checks whether a captcha shall be shown when using password login

JIRA - 1.0.92017-03-16

  • URL and user name bugfixes
  • added captchas for login forms

JIRA - 1.0.82017-01-16

  • added DataCenter compatibility
  • fixed bug at redirect after login for Jira server with no path in baseurl

JIRA - 1.0.72017-01-06

  • A bug fix which prevents redirecting to the dashboard when showing projects and project issues

JIRA - 1.0.62016-12-22

  • When a SecSignID logs in, the authentication is delegated to Atlassian Crowd to login the Crowd user

JIRA - 1.0.52016-10-13

  • Fixed bug when adding new users to Jira

JIRA - 1.0.42016-06-10

  • better filtering of the login servlet so the SecSign ID Addon cannot be bypassed
  • changed design of the SecSign ID Addon login page

JIRA - 1.0.32016-06-02

  • Added more pages e.g. MyJiraHome.jspa of the Jira system to the authentication filter to supply the login using SecSign ID

JIRA - 1.0.22016-05-12

  • Bug fixes when handling Jira user with upper and lowercase characters in name
  • Added more descriptions when handling password disabled accounts but no SecSign IDs have been assigned
  • Added more debug logging.

JIRA - 1.0.12016-01-07

  • initial release
  • two-factor authentication with Jira & SecSign ID
  • options to disable all password logins, manage IDs etc


Confluence

Confluence Changelog

CONFLUENCE SecSignID PluginAtlassian Marketplace
CONFLUENCE - 3.0.42018-07-24

  • fixed problem with groupnames with special characters

CONFLUENCE - 3.0.32018-07-11

  • Fixed interface problem with newer versions

CONFLUENCE - 3.0.22018-06-20

  • fixed bugs in navigation bar
  • fixed bugs when acces usergroups
  • fixed wrong configure urls in menu and atlassian-plugin.xml
  • fixed bugs in layout of ip range/safezone view
  • added changelog for SecSign ID addons

CONFLUENCE - 3.0.12018-06-14

  • Fixed filter for navigation bar

CONFLUENCE - 3.0.02018-06-01

  • Redesign of options and user mappings page
  • Fixed problems with captcha
  • Fixed problems with synchronizing with an Crowd instance
  • Fixed problems in local mappings users and SecSign ID

CONFLUENCE - 2.1.02018-04-04

  • updated login screen
  • new options to synchronize the ID mappings to Crowd

CONFLUENCE - 2.0.02018-01-30

  • added IPSafeZone to setup IP ranges to specify where to user username and password and when to use the strong 2FA
  • added a dialog to allow a user to self-assign a SecSignID when two-step verification is setup
  • layout changes in options
  • fixed messages and urls in descriptions

CONFLUENCE - 1.1.22017-12-21

  • bug fix when running Confluence behind a reverse proxy e.g. Apache

CONFLUENCE - 1.1.12017-10-23

CONFLUENCE - 1.1.02017-09-12

  • Support for Atlassian Crowd
  • Admin can disable passord login system wide
  • Fixed visibility issues in user profiles

CONFLUENCE - 1.0.32017-03-16

  • bugfixes for password deactivation option and captchas

CONFLUENCE - 1.0.22017-01-16

  • added DataCenter compatibility
  • bug fix when connecting to Crowd to authenticate a user

CONFLUENCE - 1.0.12016-12-22

  • When a SecSignID logs in, the authentication is delegated to Atlassian Crowd to login the Crowd user

CONFLUENCE - 1.0.02016-11-25

  • initial release
  • Two-factor authentication (2FA) with Confluence & SecSign ID
  • Options to disable all password logins, manage IDs etc.


Crowd

Crowd Changelog

CROWD SecSignID PluginAtlassian Marketplace
CROWD - 3.0.32018-07-24

  • fixed problem with groupnames with special characters

CROWD - 3.0.22018-06-21

  • fixed navigation bar menu issues
  • fixed layout issues for iprange/safezone view
  • fixed action urls when saving user / SecSign ID mappings
  • added changelog for SecSign ID addons

CROWD - 3.0.12018-06-14

  • fixed filter for navigation bar

CROWD - 3.0.02018-06-01

  • Redesign of options and user mappings page
  • Fixed problems when synchronizing user and options from JIRA and Confluence
  • Fixed problems when synchronizing with Bitbucket and Bamboo

CROWD - 2.1.02018-04-04

  • updated login screen
  • Atlassian is working on a bug fix for Crowd versions 3.1.1 and 3.1.2. If you are using these versions you might experience issues with the SecSign ID Crowd plugin. We are expecting Atlassian to resolve this issue with the next update


CROWD - 1.0.22017-10-11

  • corrected configure url
  • corrected some scope options during build process to get a smaller add-on jar

CROWD - 1.0.12017-10-11

  • initial release
  • Added datacenter compatibility
  • Fixed some text messages and description texts


Bamboo

Bamboo Changelog

BAMBOO SecSignID PluginAtlassian Marketplace
BAMBOO - 3.0.32018-07-24

  • fixed problem with groupnames with special characters

BAMBOO - 3.0.22018-06-20

  • fixed navigation bar menu issues
  • fixed layout issues for iprange/safezone view
  • fixed action urls when saving user / SecSign ID mappings
  • added changelog for SecSign ID addons

BAMBOO - 3.0.12018-06-14

  • fixed filter for navigation bar
  • fixed layout problem
  • fixed twostep/twofa change disabled buttons
  • fixed addpi /deleteip get of parameters

BAMBOO - 3.0.02018-06-01

  • Redesign of options and user mappings page
  • Fixed problems with captcha
  • Fixed problems with synchronizing with an Crowd instance
  • Fixed problems in local mappings users and SecSign ID

BAMBOO - 2.0.02018-04-04

  • updated login screen
  • new options to synchronize the ID mappings to Crowd


BAMBOO - 1.0.22018-02-22

  • initial release
  • two-factor authentication with Bamboo & SecSign ID
  • options to disable all password logins, manage IDs etc.

[/changelog]


Bitbucket

Bitbucket Changelog

BITBUCKET SecSignID PluginAtlassian Marketplace
BITBUCKET - 3.0.32018-07-24

  • fixed problem with groupnames with special characters

BITBUCKET - 3.0.22018-06-20

  • fixed navigation bar menu issues
  • fixed layout issues for iprange/safezone view
  • fixed action urls when saving user / SecSign ID mappings
  • added changelog for SecSign ID addons

BITBUCKET - 3.0.12018-06-14

  • fixed filter for navigation bar

BITBUCKET - 3.0.02018-06-01

  • Redesign of options and user mappings page
  • Fixed problems with captcha
  • Fixed problems with synchronizing with an Crowd instance
  • Fixed problems in local mappings users and SecSign ID

BITBUCKET - 2.0.02018-04-04

  • updated login screen
  • new options to synchronize the ID mappings to Crowd


BITBUCKET - 1.0.02018-02-22

  • initial release
  • two-factor authentication with Bamboo & SecSign ID
  • options to disable all password logins, manage IDs etc.

No Patch Work Solutions:
Two-Factor Authentiacation for all your Atlassian services.

Atlassian

Logo
Secure your Confluence system with SecSign Two-Factor Authentication.
Logo
Secure your Jira system with SecSign Two-Factor Authentication.
Logo
Secure your Crowd system with SecSign Two-Factor Authentication.
Logo
Secure your Bitbucket system with SecSign Two-Factor Authentication.
Logo
Secure your Bamboo system with SecSign Two-Factor Authentication.
Logo
Secure 2FA for Identity Federation with Active Directory.
Logo
All Atlassian Plugins can be secured with our SecSign-SAML-Plugin.
Logo
Secure all interfaces between your Atlassian system and external apps with our OAuth Plugin.
Logo
Secure your REST interfaces with SecSign Two-Factor Authentication.

Why SecSignID?

Die 2FA von SecSign ist die stärkste Zwei-Faktor-Authentifizierung auf dem Markt! Profitieren Sie von unbegrenzten Möglichkeiten der Integration. Für so gut wie jedes Login bietet SecSign eine Absicherung. Auch für komnplizierte Nutzermanagement-Situationen, wie beispielse Nutzer in und außerhalb eines AD hat SecSign unkomplizierte Lösungen parat.

Logo

Inhouse- oder Cloudlösung

Zwei-Faktor-Authentifizierung in der Cloud, oder volle Kontrolle und individuelle Anpasungen durch eine Inhouse Lösung.
Logo

Sichere Authentifizierung

Passwörter sind nicht sicher. Sichern Sie Ihre Logins und somit Ihre Unternehmensdaten mit unserer echten Zwei-Faktor-Authentifizierung ab.
Logo

Schützen Sie ALLE Logins

Integration in sämtliche Loginumgebungen; Web, Lokal, VPN, Remote Desktop, Mobile Logins und Plugins für nahezu alle Umgebungen.
Logo

Einfache Integration

Unsere Plugins lassen sich leicht in Ihre Systeme integrieren und ohne großen Aufwand auch für eine große Nutzerzahl aktivieren.
Logo

Unkompliziertes Nutzermanagement

Schützen Sie Ihr Active/Directory/LDAP mit der Zwei-Faktor-Authentifizierung und erstellen Sie dadruch Ihr individuelles Identitäts- und Zugangsmanagement mit zahlreichen Sicherheitseinstellungen.
Logo

App Integration

Mit unserer Anwendungsfertigen SDK können Sie ganz einfach die Zwei-Faktor-Authentifizierung in bestehende Apps integrieren. Alternativ erstellen wir eine App mit Ihrem Unternehmens Look-and-Feel.

Your own ID-Server

On premise installations of SecSign ID offer the flexibility to connect with your preferred servers, services, and devices. And you can customize the SecSign ID with your own organization’s branding.

Learn More
On Premise 2FA ID

Latest Blog Posts, Updates & Features

Atlassian JIRA and Confluence Two-Step Authentication and IP-SafeZone

With SecSign ID you can protect all your logins with a secure Two-Factor Authentication based on a challenge response. The authentication offers the highest protection for the company data while being incredibly simple to us ...

Mehr Lesen

SSO Setup with Crowd

Content Pre-requirements Setup and configuration of the components as a server application Configuration of Crowd for the centrally organized user management Configure application (for example JIRA) to be used wit ...

Mehr Lesen

What is possible with Crowd?

The SecSign ID Crowd Plugin can be integrated in just a few steps. For more information about the plugin and the integration please refer to the following pages. Do you have any questions? Don't hesitate to contact us. ...

Mehr Lesen