On-premise Active Directory (AD)
for Atlassian JIRA & Confluence Logins (ADFS)
secured with SecSign Two-Factor Authentication
Find out why our Two-Factor Authentication is the best, some key-facts for developers and why you should upgrade to SecSign for your business.
Learn more about the options of on-premise use and your own customized ID App in your corporate design.
Download the plugin as cloud version for a free and convenient protection.
Table of contents
Active Directory Federation Services are used for local user management (for example Active Directory or LDAP) in companies for the authentication of web services (for example JIRA or Confluence).
To use the SecSign ID with JIRA or Confluence a SAML Plugin is required. That way the user only has to provide the SecSign ID for the login. The authentication is redirected via the Active Directory, secured with the on-premise SecSign ID server. The authentication takes place on the local SecSign ID server.
That way all user can be managed and controlled local in the Active Directory. Also, web services (like JIRA or Confluence) do not receive any confidential company data.
Try the Login with the ADFS in our test environment.
1. Installation
Common steps for the integration with Atlassian JIRA and Confluence are explained here:
1On the Windows Server run the Server Manager, Add Roles and Features. Please check the following options additionally to those selected per default already:
- Server roles:
- Active Directory Domain Services
- Active Directory Federation Services
- Web Server (IIS)
- Features:
- .NET Framework 4.5 (4.6 on Windows Server 2016) Features
- ASP.NET 4.5
- .NET Framework 4.5 (4.6 on Windows Server 2016) Features
- Role services for Web Server (IIS)
- Application Development
- ASP.NET 4.5 (4.6 on Windows Server 2016)
- Application Development
2Promote the server to a domain controller if not done already.
3Install a recent Oracle Java run time enviroment from: https://java.com/
4Add the SecSign ID user attribute to the Active Directory: https://www.secsign.com/two-factor-authentication-in-active-directory/
5Import a certificate for HTTPS on the Windows Server.
- Copy your private key and https certificate bundled in a p12 file (pfx) to the server and double-click it.
- Select “Local Machine” as store location.
- Confirm the suggested options and confirm to install the certificate.
6Install the imported certificate for HTTPS at the Web Server (IIS).
- Click the Windows start menu and then click “Windows Administrative Tools”.
- Double-click the Internet Information Services (IIS) Manager.
- Right-click the web site in the list on the left side.
- Select Edit Bindings.
- Add “https” and select the TLS (SSL) certificate.
7Switch off ADFS AutoCertificateRollover in order to be able to set your token signing certificate by running this command in a PowerShell:
- set-adfsproperties -autocertificaterollover $false
8Set your token signing certificate in ADFS, so that ADFS will include it into the metadata required for the Jira setup later:
- Run the ServerManager.
- Select “AD FS Management” from the “Tools” menu.
- Unfold “Service”.
- Select “Certificates” in the tree.
- In the “Actions” pane click “Add Token-Signing Certificate…”
- Select the certificate which you have imported from the pfx file or p12 for HTTPS before.
- Under “Token-signing” there should be two certificates. Right-click your new certificate and select “Set as primary”.
If Windows 2016 is not able to read the metadata from Jira, then please use the PowerShell instead:
Add-AdfsRelyingPartyTrust -Name “Jira SecSign ID” -MetadataUrl
After loading the metadata from the Windows Server in Jira:
- Change the path in the IdP POST Binding URL from:
/adfs/ls/ to: /FederatedSecSignID/SecSignIDLogin.aspx - Change the IdP Entity ID from:
http:///adfs/services/trust to: https:// /FederatedSecSignID/SecSignIDLogin.aspx - Install the SAML SSO plug-in for Jira and configure it as described by its manufacturer
If Windows 2016 is not able to read the metadata from Confluence, then please use the PowerShell instead:
Add-AdfsRelyingPartyTrust -Name “Confluence SecSign ID” -MetadataUrl
After loading the metadata from the Windows Server in Confluence:
- Change the path in the IdP POST Binding URL from:
/adfs/ls/ to: /FederatedSecSignID/SecSignIDLogin.aspx - Change the IdP Entity ID from: http://
/adfs/services/trust to: https:// /FederatedSecSignID/SecSignIDLogin.aspx - Install the SAML SSO plug-in for Confluence and configure it as described by its manufacturer
2. Available APIS
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.
3. See for yourself
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.
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.
Why upgrade to SecSign?
On-premise or in the cloud
Choose between our SecSign ID Cloud or operate your own on-premise Two-Factor Authentication server.
Easy customization
Operate your own YourBrand ID app - Two-Factor Authentication customized to your needs.
Ready-to-use SDK
Integrate SecSign ID Two-Factor Authentication in existing apps with our ready-to-use SDK.
Easy user management
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.
Cover all logins
Integration in any login environment: web, local, VPN, remote desktop, mobile logins and many more.
Plugins for all your needs
No need for complex integration: we have plugins for almost all environments.
Contact Us
Sales
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.
Product Support
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