Bizagi authentication

<< Click to Display Table of Contents >>

Navigation:  Integration and authentication > Identity managers >

Bizagi authentication

Overview

Bizagi Cloud supports integration with Identity Management services such as Azure Active Directory (Azure AD), or connections with on-premises LDAPs via a VPN configuration.

However, you can also choose to rely on Bizagi' local authentication service which offers secure sign-in options as well as configuration parameters to enforce your corporate password and accounts policies.

 

What you need to do

In order to configure Bizagi authentication for use in Bizagi Cloud, follow these steps:

 

1. Configure the authentication type in Bizagi Studio.

2. Configure Bizagi authentication parameters.

 

Configuration procedure

By default, Bizagi Studio projects start off using Bizagi Authentication, so the first step is not necessary unless you have already changed settings to use a different type of authentication.

 

1. Configure the authentication type in Bizagi Studio.

To explicitly choose Bizagi authentication, follow these steps:

 

1.1 Open your Bizagi Studio project.

Open Bizagi Studio and load your project (development environment).

 

Cloud_OpenProj

 

1.2 Go to the security settings.

Click on the Expert view, and select the Security module.

 

Cloud_SecurityModule

 

Click on Authentication in the middle panel, and ensure that the drop-down list at the rightmost panel shows Bizagi Authentication:

 

Authentication_Bizagi

 

Click Update if you had a different choice before.

 

2. Configure Bizagi authentication parameters.

Once Bizagi Authentication is chosen, you will notice that sub-items for Authentication are displayed.

 

Configure these parameters to use account and password policies as needed. Some parameters apply to passwords, others to accounts and session management, and others apply to the overall admin procedures when managing accounts.

 

AuthOptions

 

We recommend reviewing default values and define explicitly enforce password change after first login, enforce use of capital letters in passwords, enforce use of small letters in passwords, enforce use of numbers in passwords, enforce use of special characters in passwords, idle sessions time-out, minimum length of passwords, and maximum number of failed login attempts.

 

To configure each of the parameters, click on that parameter and define a setting in the panel to its right.

Ensure you click Update if you change values.

 

Refer to the following table for a description of each of the different parameters:

 

OPTION

DESCRIPTION

Account lockout duration

Defines the number of minutes an account remains locked out due to reaching Maximum number of failed login attempts (and having set Enable account lockout for failed login attempts), before automatically being unlocked.

This duration must be greater or equal than Failed login attempts time-out.

E-mail for an account unlock request - Body

Defines the body of the mail to be sent to the administrator when a user requests the unlocking of an account  (i.e when using Enable account unlock request e-mails to admin and specifying E-mail of admin).

Use with E-mail for an account unlock request - Subject.

E-mail for an account unlock request - Subject

Defines the subject of the mail to be sent to the administrator when a user requests the unlocking of an account (i.e when using Enable account unlock request e-mails to admin and specifying E-mail of admin).

Use with E-mail for an account unlock request - Body.

E-mail for an active account - Body

Defines the body of the mail to be sent to a user when his/her account is created and set as active.

Use with E-mail for an active account - Subject.

E-mail for an active account - Subject        

Defines the subject of the mail to be sent to a user when his/her account is created and set as active.

Use with E-mail for an active account - Body.

E-mail for password reminder - Body

Defines the body of the mail to be sent when the user requests a password reminder.

Use with E-mail for password reminder - Subject.

E-mail for password reminder - Subject

Defines the subject of the mail to be sent when the user requests a password reminder.

Use with E-mail for password reminder - Body.

E-mail of admin

Defines the e-mail of the administrator of accounts in charge of receiving E-mail for an account unlock request (i.e when using Enable account unlock request e-mails to admin).

Enable account lockout for failed login attempts

Establishes if accounts should be locked out when a maximum number of failed login attempts is reached (to use with Maximum number of failed login attempts).

Enable account unlock request e-mails to admin

Establishes if e-mails are sent when a user requests an account unlock.

Use with E-mail for an account unlock request, and E-mail of admin.

Enable authentication logging in database

Establishes if an audit log is recorded with all authentication events. If enabled look for the table AUTHOLOG in the database.

Note: Using Quick login feature does not create records in the authentication log.

Enable multiple sessions per account

Establishes if more than one simultaneous session is allowed for a same account.

Enable quick login

Applies only to the Development and Test environments.

 

Establishes if login to the Work portal is done without inputting the passwords of accounts (a quick login through a drop-down list displaying valid login accounts).

The drop-down list will show the first 100 active users (from the 101th user, accounts need to be typed into a text field).

To use for unit tests or quick prototyping purposes (this setting is not valid for a production environment).

When using quick login, the work portal's authentication log query feature will not record login events.

Enable use of a secret question

Establishes if a secret question and answer can be filled out by users, in order to have the possibility of avoiding an account lockout when the password is forgotten.

Enable password change after the first login

Establishes if a user must change the password after the first login.

Consider using this option or setting an explicit number of days for Password minimum age.

Enforce password history

Defines the number of unique passwords an account must have before reusing an older one.

Enforce use of capital letters in passwords

Establishes if passwords must contain at least one capital letter.

Enforce use of letters in passwords

Establishes if passwords must contain at least one letter.

Consider using Enforce use of capital letters in password and Enforce use of lowercase in password instead.

Enforce use of numbers in passwords

Establishes if passwords must contain at least one number.

Enforce use of small letters in passwords

Establishes if passwords must contain at least one small letter.

Enforce use of special characters in passwords

Establishes if passwords must contain at least one special character (i.e non alphanumeric characters).

Enforce validation of sequences in passwords

Establishes if passwords are not allowed to contain character sequences (e.g: abc or 12).

Failed login attempts time-out

Defines the number of minutes in which failed login attempts time-out.

The counter that stores this number of attempts is reset after this time frame, provided that the Maximum number of failed login attempts is not reached.

Idle account duration before lockout

Defines the maximum number of days before an unused account is locked out (unused accounts are those which have not had activity in that time frame).

Idle sessions time-out

 

 

Defines the time in minutes in which an idle session expires; in which case it would be required to authenticate again.

Maximum length of passwords

Defines the maximum number of characters for passwords (use zero if a maximum length is not desired).

Maximum number of failed login attempts

Defines a maximum number of login attempts before an account is locked out.

Applies when Enable account lockout for failed login attempts is active.

Minimum length of passwords

Defines the minimum number of characters for passwords.

Password maximum age

Defines the maximum number of days in which a password can be used, before it requires to be changed (i.e, the expiration time of passwords).

Password minimum age

Defines the minimum number of days in which a password must be used, before it is available for a change.

Consider using this option or setting an explicit number of days for Enable password change after the first login.

SLA for an account unlock request

Defines the expected service time (in hours) to process an account unlock request.

 

Next steps

At this point authentication has been set and you may proceed to create or import users into Bizagi.

Note that user management (i.e, creating, importing, editing) is not done through Bizagi Studio.

Through the Work portal you may manually create users for each environment.