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.

To use the SecSign ID Crowd Plugin to securely manage the Atlassian logins, the respective SecSign ID Atlassian Plugins need to be installed first. If your setup for example includes Crowd, JIRA and Confluence and you want to add secure two-factor authentication to the management features of Crowd, you need to install the SecSign ID Crowd, JIRA and Confluence plugin.
An overview of the Atlassian plugins offered by SecSign are available here.
Information about the setup of a complete SSO for Atlassian services with Crowd can be found on our blog.

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.
ENROLLMENT OPTIONSThe Crowd Plugin can be installed in a few simple steps.

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.

There are only three options for settings for the plugin: The Service Name and URL of the ID-Server as well as the option Synchronizeable IDs. The Service Name should describe your JIRA system. It is displayed to the user during the authentication procedure.

The URL of the ID-server is „https://httpapi.secsign.com“ by default. This option gives the possibility to employ your on-premise JIRA 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.
The option synchronizeable IDs gives access to editing SecSign IDs via Crowd. IDs can only be read and not edited if this option is deactivated. To edit IDs via Crowd please activate this function.
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.

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.

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 portal.secsign.com.
An administrator can assign a Crowd user to an ID.
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.
We provide an ever growing list of APIs and plugins to easily integrate the SecSign ID Two-Factor Authentication in any project. An overview is available at Plugin and APIs.
We do not only offer APIs in different programming languages but also plugins for CMS, Server and VPN environments, oAuth2 and many more. These plugins use our APIs and offer additional functionalities, for example user management, easy and native installation, logging or integration in firewalls or Active Directory.
The JIRA plugin for example uses the JAVA-API. The PHP-Api and JS-API is used by WordPress, Joomla, Drupal, Typo3 and many more. The ASP.net/C#-API is used for the Windows and Cisco VPN and the C-API is used for protecting Unix SSH services. The Objective-C API is used by our AppleTV and iPhone/iPad apps.

You can experience the SecSign ID two-factor authentication and the two-factor login by simply integrating the plugin into your website or test environment. Or you can try out the login process on our website without having to register first. You already have a SecSign ID or you want one? Login now and use the portal or use our hassle free registration.
See for yourself how fast and convenient the login process using challenge-response authentication with 2048-bit key pairs is. There is no need for passwords, and no passwords or other confidential information are ever transmitted. It is easy to integrate and simple to use.
For more information about the patented SafeKey procedure and it's unique security can be found here.
If you are missing an API for the programming language you are working with, feel free to contact us and we’ll find a solution with you. If you need help with the integration into an existing system or you can’t find the plugin for your content management system you are working with, don’t hesitate to contact our support team.
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.


Choose between our SecSign ID Cloud or operate your own on-premise Two-Factor Authentication server.

Operate your own YourBrand ID app - Two-Factor Authentication customized to your needs.
Integrate SecSign ID Two-Factor Authentication in existing apps with our ready-to-use SDK.
Use the Two-Factor Authentication Server to secure your company Active Directory/LDAP. Your own Identity and Access Management System, for example for mandatory updates and additional security features.

Integration in any login environment: web, local, VPN, remote desktop, mobile logins and many more.

No need for complex integration: we have plugins for almost all environments.
Want to learn more about SecSign’s innovative and highly secure
solutions for protecting your user accounts and sensitive data?
Use our contact form to submit your information, and a SecSign sales representative will contact you within one business day.
If you need assistance with an existing SecSign account or product
installation, please see the FAQs for more information on the most common questions. You don’t find the solution to your problem? Don’t hesitate to contact the
Product Support
I am Interested in