SecSignID Plugin: Crowd

2017-09-15 14 minutes to read

2-Factor-Authentication with SecSignID for Crowd

This tutorial describes how to set up the SecSignID-Plugin for your Confluence-System to login increase security.


Overview & Quickstart

Use SecSign ID Crowd Two-Factor Authentication to login to all your Atlassian applications with an easy and highly secure user login using iOS or Android mobile devices as well as for desktop use. This tutorial describes the integration of the SecSign ID Crowd Plugin. An overview on the Crowd functions and protection with the SecSign ID Two-Factor Authentication is available on the Crowd Overview page.


SecSign ID is a plugin for real two-factor authentication (2FA). 2FA adds another layer of security to your website by using a second token. In this case the physical token is your smartphone.

For more information about the Crowd setup with SecSign please refer to our Crowd overview and our Atlassian overview for SecSign ID.

Questions? Feel free to get in touch with us if you need help setting up your SecSign ID plugin or to request a plugin for a not yet supported environment.

Pre-requirements for Two-Factor Authentication with Crowd

In order to use two-factor authentication with Crowd and the connected Atlassian services, you need to install the SecSign ID plugin for Crowd and all connected services that need to be secured with 2FA.
1. Install the SecSign ID 2FA plugin for each service that is connected with Crowd
2. Install the SecSign ID 2FA Plugin for Crowd
3. Use 2FA with Crowd for all connected services



The communication of Crowd, JIRA, the Active Directory and the SecSign ID server is displayed in the following UML diagram.

A link to the Active Directory is not necessary for the setup. The IDs can be directly managed in the the respective Atlassian services without linking the Active Directory.
By linking your Active Directory there is no need to separately manage your users in all individual services. Each change to a user profile in the Active Directory is automatically applied to all services the user is assigned to.



1Install the Plugins

Install the SecSign ID Crowd Plugin and the SecSign ID plugins for all connected Atlassian services that need to be secured with 2FA. A roadmap is available here.

Information about the setup of a complete SSO for Atlassian services with Crowd can be found on our blog. This will give you detailed information about the initial Crowd Setup if you have not been using Crowd yet.

2User Enrollment

Comprehensive security doesn’t need to be complicated. Your users can be secured with 2FA by tomorrow. You have the choice between convenient ready-to-use options or customized solutions for your specific setup.
Our solutions are build for frictionless rollout and management, user self-control and convenience. Reliable protection in just a few simple steps.
More information about the SecSign ID Rollout Options are available here.

If your users are managed with an Active Directory setup you have two options to activate the two-factor authentication for them.

Activate the two-factor authentication without schema extension

Activate the two-factor authentication with schema extension


The Crowd Plugin can be installed in a few simple steps.

  1. Shut down the Crowd-Server
  2. Navigate to the home-folder of the Crowd installation
  3. Versions older 3.0 : Copy the .jar file of the plugin in the plugin folder
    Versionen newer than 3.0 : Copy the .jar file of the plugin in the shared\plugins folder

  4. Launch the Crowd installation

A detailed description on how to activate the Crowd SSO in Jira, Confluence and other applications, please refer to this tutorial.


The option “SecSign ID” is available in the top menu after installing the SecSign ID Plugin. This option gives access to the configuration of the plugin and assignment of the SecSign ID to the users in the directory.

Plugin Settings

On-premise ID Server

The Service Name should describe your Crowd system. It is displayed to the user during the authentication procedure. The URL of the ID-server is „“ by default. This option gives the possibility to employ your on-premise Crowd system like the on-premise ID-server. With the on-premise ID server you have complete control over accessibility, settings and user data.
More information about our on-premise setup is available on our website.

Local Mappings and LDAP settings

The option Local Mappings gives access to editing SecSign IDs via Crowd. IDs can be edited locally and read by connected applications.

Additionally the option LDAP-Import allows to import SecSign IDs from an added LDAP-Directory. For more information on SecSign IDs in LDAP-Directories see the Tutorial.
Activating this option imports mappings from LDAP-Directories and merges them with existing local mappings.

The LDAP-attribute determines the attribute which is searched for in the directories. This can be edited to fit your settings. The default-value is secsignid, which is the attribute-name mentioned in the tutorials.

The option Write to LDAP allows to write changes in mappings from Crowd to the LDAP directory. Use this option with care, because it can delete mappings that are necessary for use in Windows or other important applications.

Also be aware that you already added the secsignid-attribute to the directory as mentioned in the tutorial.

Custom Login Layout

The option Custom Login Layout allows you to change the background of the login screen to fit your Crowd appearance.

The corresponding Login Background Color determines the Hex color code that is used as the background color for the login screen.

User settings

You can assign each user one or more IDs that can used for authentication and login with Crowd and, if the plugins are installed, JIRA and Confluence. If you want to assign several IDs to one user simply separate the IDs with a comma. One example of using several IDs for one user is for example company JIRA accounts where several employees use one account with their individual IDs.

Please be aware that activating LDAP-Import without Write to LDAP will result in not deletable SecSign IDs. Even if you clear the input for one user. The imported SecSign IDs will persist and are usable nonetheless.
To delete those IDs please delete them in the LDAP-directory or enable write access to the LDAP by the Write to LDAP option.
If you want to disable the login for a user with an ID in the LDAP directory, just deactivate that account in Crowd or revoke permissions for the application that should not be accessible

An overview of the individual users and their SecSign IDs is sorted into directories within Crowd. Additionally, SecSign IDs can be assigned to the user in the Crowd profile view. In the Crowd user directory all users are listed sorted by directories. This view provides account information for every user and profile information. It also gives information about the assigned SecSign IDs and the option to edit them.

Login procedure

Login procedure

After installing the SecSign ID plugin the SecSign ID login window appears when opening Crowd instead of the user name and password login window. After the user initiates the login an access pass is displayed. This access pass is part of the two-factor authentication procedure that the user needs to verify in the SecSign ID app. The user compares the symbol displayed at the Crowd login with the symbol displayed in his app and selects the identical one. The user is then automatically forwarded to Crowd and successfully logged in.

You can try the login procedure for free on our website. Download the SecSign ID app from iTunes or Google Play and generate a SecSign ID. You can then use this ID to log into

An administrator can assign a Crowd user to an ID.

User Setup

Setup new user in Crowd

When setting up new users by an administrator the box SecSign ID is displayed. The administrator can assign a SecSign ID to a new user and also define wether the user is still allowed to only use a password for authentication. Since Crowd only knows two status (successful and failed) the user gets the message “user name and password incorrect” if the password option is disabled.



If you are experiencing issues with the plugin or if you lost your SecSign ID you can manually remove the plugin. Please shut down the Crowd Server and navigate to the home directory of the Crowd Installation.
Delete the .jar file and restart the server.

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


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


Inhouse- oder Cloudlösung

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

Sichere Authentifizierung

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

Schützen Sie ALLE Logins

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

Einfache Integration

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

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.

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

Options for secure SSO for Atlassian products

Options for securing Atlassian SSO Your users and passwords and services are all over the place? You want to simplify your security and authentication setup but you don’t know where to start? Move beyond your authentication ...

Mehr Lesen

Multi-Factor Authentication powered IdM/IAM

Multi-Factor Authentication powered IdM/IAM with SecSign ID Your users and passwords and services are all over the place? You want to simplify your security and authentication setup but you don’t know where to start? Move bey ...

Mehr Lesen

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