Skip to content
3SL header
3SL_Logo_Medium

3SL Blog

From concept to creation

  • Home
  • Blog
  • News
  • Newsletters
  • Hints & Tips
  • Articles
  • FAQ

Tag: login

In computer security, logging in is the process by which an individual gains access to a computer system by identifying and authenticating themselves. The user credentials are typically some form of username and a matching password, and these credentials themselves are sometimes referred to as a login.

Posted on 18th November 2026

Two-Factor Authentication (2FA)

Two-factor authentication (2FA) is now supported in WorkBench, Web Access, Project Manager, Web Services Interface, the API and the Toolsuite applications. This adds a new layer of security.

Setting up 2FA

The setup of 2FA is simple:

  1. Configure the cradle.ini/.cradlerc file to work with your email server
  2. Ensure user profiles contain email addresses
  3. Configure the 2fa_config file

These are detailed below.

Configure the cradle.ini/.cradlerc Configuration File

To be able to receive 2FA codes, the Cradle server must be configured to work with your mail server:

cradle.ini File
Configuration File showing Mail Server Settings

User Profiles

2FA uses the email address associated with the user’s Cradle User Profile, so you need to ensure the user’s email address is configured correctly:

User Setup showing user
User Profile showing Email Address

 

2FA Configuration File

2FA is configured by the System Administrator using the 2fa_config file. This file is in CRADLEHOME\admin.

Setting USE_2FA to true, enables 2FA for the Cradle components.

2FA Configuration File Attributes

This file contains the following attributes:

  • USE_2FA – Flag which confirms if Cradle components will use 2FA. Default – false.
  • TIMEOUT – Contains the time in minutes for how long the Cradle components will remain active for the Cradle user to enter the 2FA code before being terminated. Default – 2.
  • PROJECT_SCOPE – Defines which Cradle projects require 2FA. If empty, 2FA is applied to all projects. If defined, this should be a comma separated list of project codes, e.g. DEMO,TEST.
  • ENABLE_CMDLINE_TOOLS – Controls whether Cradle command line utilities are permitted to run when 2FA is enabled. By default, command line tools are blocked under 2FA to prevent bypassing security. Default – false.
  • MANAGER_BYPASS – Determines whether the MANAGER account is exempt from 2FA checks. Due to its elevated privileges, it may be desirable to skip 2FA for this account, but for higher security it can also be included. Default – false.
  • EMAIL_FORMAT – Used to set the format of the email that is sent containing the 2FA code. The possible values are plain (plain email text only) or template (use the web_auth.eml template).
  • EMAIL_SUBJECT – Subject used in the 2FA email.
  • EMAIL_MESSAGE – Message used in the 2FA email.

Login using 2FA

When you attempt to login as a user with 2FA you are prompted to enter a 6 digit code.

The following example is in WorkBench:

Two Factor Authentication Dialog
WorkBench Two Factor Authentication Dialog

The following example is in Web Access:

Web Access Login showing 2FA
Web Access Login showing 2FA

Please note if you enter the code after the 2FA timeout setting, a Cradle Web Server 500 Error will be displayed.

The 2FA code is sent to the email address that is defined in the User Profile of the user you are logging in as. Once you have entered the correct code, click Continue to login.

TweetShareNewsletter
Posted on 30th May 201731st May 2017

LDAP Troubleshooting Checklist

LDAP Connection Problems/Unknown User Issues?

Work through the following checklist as setting up the ldap_config file to match your LDAP settings can be difficult:

  1. Enable the trace log by setting the LDAP_TRACE attribute to TRUE in the ldap_config file. The ldap_trace.log file is written to a file in the logs/user directory this can be used to diagnose your problem.

    Screenshot showing tracing enabled in the ldap_config file
    Enabling tracing in the ldap_config file
  2. If you are using Windows® Active Directory, run the Active Directory Users and Computers browser from the Windows Domain Controller and check what the DN (Distinguished Name) is for the domain. From this browser you can also find out where the users are stored.
  3. On other LDAP servers, use the setup tool for the LDAP server to find out the correct DN and user areas.
  4. Check the correct Protocol is being used.
  5. Check that the correct level in the LDAP directory structure is being used as the BIND_DN and also that the correct BIND_PASSWD is being used.
  6. If the LDAP server is running securely, is the ldap_config file setup correctly?
  7. To test that you are connecting to the LDAP server correctly without checking the user authentication, set AUTO_LDAP_LOGIN from TRUE to FALSE. This would help to show where the problem is, i.e. either an issue with the connection to the LDAP server or whether there is a problem searching the correct user location on the LDAP server.
  8. LDAP verification will not succeed if the user’s LDAP structure contains multiple UIDs, e.g. if you have UID=manager and UID=yourname.
  9. If you are failing to login and you receive an LDAP message confirming the password or username could be incorrect but the LDAP response message is blank then it is likely you have a case match issue with the entered username and the username returned from LDAP, and Cradle is rejecting the entered username. To resolve this issue you can set the UID_IGNORE_CASE to true.

For further information on LDAP see our previous blog entry or for more on Cradle integration with LDAP please refer to our online help.

TweetShareNewsletter
Posted on 18th May 201716th October 2019

LDAP Authentication Within Cradle

Cradle provides the ability to use LDAP for user login (Lightweight Directory Access Protocol)

This feature provides the ability for Cradle to authenticate a user against an LDAP server instead of passwords held in Cradle user accounts within a Cradle project database.

  • Used to look up user login information from a server
  • Avoids the need for user to enter username and password entry when launching the tools
  • LDAP is an optional part of Cradle that you can enable or not (disabled by default)
  • Supported by all Cradle tools
Screenshot of login dialog using LDAP
Login dialog showing LDAP being used

Cradle supports two methods of LDAP authentication:

The first for systems where the username can be inferred from network username and the second for systems where the username can not be inferred from the network username.

Force Network Login Name

The first method assumes that Cradle username is to be inferred from the current network username (Force Network LoginName). A user authenticates against LDAP when they login to the network by supplying a network username and a network password.

This method is to allow a user to login to a Cradle project without specifying a username or password. In this situation, the users are already authenticated to their desktop or Citrix environment and we do not require them to login again with a username and password to gain access to Cradle. So, provided that a user has logged-in to their desktop or Citrix environment and they have a User Profile in a Cradle project, the users will be able to login to Cradle without supplying a username or password.

Username/Password validated via LDAP server

The second method allows users to enter username and password to be validated via LDAP server. A user authenticates against LDAP when they login to the Cradle tools, by supplying a username and password.

LDAP control with ldap_config

Contained within the ldap_config file is an attribute called AUTO_LDAP_LOGIN

If AUTO_LDAP_LOGIN is TRUE then Force Network Login Name method is used (login with current network username)
If AUTO_LDAP_LOGIN is FALSE then Username/Password validated via LDAP server is is used (allows users to enter LDAP username and password)

For more information on how to setup Cradle to intergrate/interact with your LDAP server please refer to the online help section.

 

TweetShareNewsletter
Posted on 27th February 201710th March 2017

Desktop Login Shortcut

Want to Login More Quickly ?

If you are operating in a secure environment and have multiple projects, you may want to launch WorkBench faster from a Windows Desktop shortcut.

Configure the shortcut for an individual Cradle user with  “-login USERNAME,PASSWORD,PROJ-CODE ” for Cradle’s WorkBench.

Ediiting shortcut properties for login

For an even faster connection, you could also specify -cds thus alleviating WorkBench from searching for a server. (Without this parameter WorkBench will broadcast and await a response from an available CDS before connecting)

Configure with “-cds HOSTNAME/IP-ADDRESS” and give the host or IP address of the server running the CDS (Cradle Database Server).

https://www.threesl.com:2958/blog/wp-content/uploads/2017/02/shortcuts.mp4

If you are running from Linux, you can also use these parameters.  When launching WorkBench from the command line use c_work and the -login and -cds parameters.

TweetShareNewsletter
Posted on 19th February 201722nd October 2018

Login Messages and User Acknowledgement

You can add your own messages into the Cradle Login dialog to communicate important information to your Cradle users.

You can also add a checkbox to the Login dialog that users must select before they can login. This includes users who use Single-Sign-On (SSO) to login to Cradle.

This checkbox can be used to, for example, ensure that users have acknowledged that they understand their security and confidentiality obligations every time that they login to Cradle.

Login Messages
Article Updated 22/10/2018 – Made image slightly bigger
TweetShareNewsletter
Posted on 12th August 20168th October 2018

User-Defined Login Messages

Do you have something important that your users need to know? Rather than having to send an email, you can display messages on the Cradle login screen for all of your Cradle users to see. These are called “Login Messages”, and can communicate any number of things, for example:

  • A reminder of a confidentiality agreement that may be implicit in your use of Cradle
  • The dates and times for any planned server reboots, for example after installing updates to the operating system
  • Announcements of internal training courses
  • A daily joke(!)
How to setup a user login message
Login Message

Setup

The message is written in UTF-8 and so can be in any language. The login message appears on the right hand side of the login dialog. You can optionally include a checkbox that users must select to confirm that they have read the message. A user cannot login until this checkbox has been selected. Users must select the checkbox every time that they login. See this blog post for more information.

The login message is stored in the file: login_message in the admin directory of the Cradle installation on your Cradle server:

Linux: $CRADLEHOME/admin/login_message
Windows: %CRADLEHOME%\admin\login_message

This file contains notes which explain how to enter a message into the file, also includes examples. Any login_message files in an end users Cradle installation are ignored because the message is controlled on the server and displayed to all client machines.

More information about login messages in the Cradle help.

 

TweetShareNewsletter
November 2026
MTWTFSS
 1
2345678
9101112131415
16171819202122
23242526272829
30 
« Oct    

Archive

Search

Categories

Tags

user requirements compliance and traceability change control forms training deals sidebar login lifecycle distributor testing Web Publisher process flow diagram (PFD) Citrix dates/times start page office tools language frames Cradle-7.4 general interest Cradle product versions discussions Project Manager queries modelling Risks social media c_io Model Based Systems Engineering (MBSE) anti-virus Cradle database Cradle licences Document Publisher Cradle-7.3 baselines Cradle-7.2 Systems Engineering (SE) source documents requirements management diagrams skills PDUID errors history project management Toolsuite alerts formal documents reports cross references / links iso9001 new features / release white papers Cyber Essentials publish document management definitions Web Access metrics linux Cradle-7.1 newsletter projects SysML Cradle-7.6 settings/configuration/prefs/customise WorkBench administration Document Loader G-Cloud hierarchy diagrams (HID) Cradle support categories dashboards Cradle-7.7 Cradle installation INCOSE Risk Management SaaS information capture import/export hierarchies Cradle modules Risk items 3SL graphs output/printing database configuration management images workflow user interface (UI) commands project schema Windows views users

Copyright

Copyright© 1987 - Structured Software Systems Ltd. All rights reserved. Cradle® is a registered trademark of 3SL in the UK and other countries.
Blog – Privacy Proudly powered by WordPress