---
title: Configuring Okta in 4biz
slug: helium-en/configuring-okta-in-4biz
description: Learn how to configure Okta authentication in your 4biz instance with this comprehensive document. Follow the step-by-step guide on creating an Okta account, setting up a 4biz application, assigning users, and syncing data. Also, find out how to configure
createdAt: 2021-10-20T19:32:13.000Z
---

This authentication method allows you to use the **Okta&#x20;**&#x66;eatures to authenticate users of your organization in a <font color="#ff6900">**4biz**</font> instance. This document explains the steps in configuring this method. To learn more about Okta, visit <font color="#2166ae"><u>**okta.com**</u></font><u>****</u>

## Before getting started

- [x] The configuration of this solution is a multi-phase process;
- [x] The first step is the creation of an Okta account.

## Procedure

******<font color="#2166ae"><u>***1st Step***</u>***\:*** </font>*Create an Okta account:*

1. Access the site:  [https://www.okta.com](https://www.okta.com);
2. Click on "**Try Okta**" and then on "**Sign up toda**y";
3. Enter the essential data (e-mail, name, and last name);

::Image[]{src="https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/4MF7O3HUBYXtB-mXhvQR__image.png" size="58" width="420" height="448" position="center" showCaption="false"}

4\. Click on "**Get Started**" to complete the operation. Then check the registered e-mail (which will send an access link), access the account with the temporary password sent, and change it for greater data security;

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/xylDfx623JhqAWXJnhChu_image.png)

******<font color="#2166ae"><u>***2nd Step***</u>***\:*** </font>*Created&#x20;*<font color="#ff6900">***4biz*** </font>*application within Okta:*

1. After completing the previous step, connect to Okta with your newly created account;
2. Click on the "**Applications**" tab and then on "**Add Application**";

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/9Sl5bzSsf-p7rnssaX6TH_image.png)

3\. Click on "**Create New App**";

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/FmhHSwc1n9S43xyRume71_image.png)

4\. Select the option "**SAML 2.0**" and then click on "**Create**";

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/sHhej3YI8K3V-48YZHimt_image.png)

5\. In the field "**App Name**", add the name of the application and soon after, it is necessary to click on "**Next**";

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/K_jUcc6ohS418NsOD2spP_image.png)

6\. Configure the application path and then click on "**Next**";

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/sZ67YIS88sjkp33RhnsAn_image.png)

:::hint{type="warning"}
⚠ <u>**Attention**</u>**!**

In the "**Single sign on URL**" and "**Audience URI (SP Entity ID)**" fields, the URL addresses on which the <font color="#ff6900">**4biz** </font>Application will be executed should be included.
:::

7\. Select the options "**I'm an Okta customer adding an internal app**" and "**This is an internal app that we have created**". Then, click on "**Finish**".

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/jsTY43gBsEBfRCl-GJDwD_image.png)

******<font color="#2166ae"><u>***3rd Step***</u>***\:*** </font>*Assign users to Okta's&#x20;*<font color="#ff6900">***4biz***</font>*&#x20;application:*

1. After completing the previous step, click on the "`Applications > Applications`" tab, then on "**Assign Applications**" and choose the filter called "**People**";

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/p0I0HM2idxECuwxQQLSHA_image.png)

2\. Then you can choose the user who will be allowed to access the application that is being created. Click on "**Assign**" and then, to finish, click on "**Done**";

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/XPMp_S_pW-pSVnfniZOEJ_image.png)

******<font color="#2166ae"><u>***4th Step***</u>***\:***</font>*&#x20;Include required information in the&#x20;*<font color="#ff6900">***4biz***</font>*&#x20;configured on Okta:*

1. You will need to configure some data in the WildFly directory. Access the directory, open the "<font color="#2166ae">**/standalone/configuration**</font>" folder and change the file "**4biz.cfg**".

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/Nz47rEtqHbeJlrYDy7xFd_image.png)

2\. Accessed the file, you need to include this information in the file "**4biz.cfg**":

a) In the line, **SAML2\_HOST and SAML2\_PORT**, include the address and port of the <font color="#ff6900">**4biz**</font> application;

b) In the line, **SAML2\_METADATA**, include the SAML metadata of the Okta. This data can be obtained by following the instructions below:&#x20;

- Access the <font color="#ff6900">**4biz**</font> application in Okta, click the "`Applications > Applications`" tab, and then on "**Sign On**". When you click on the "**Identity Provider metadata**" option, a new tab will be available to the metadata, copy the URL of the browser and insert in the property SAML2\_METADATA;&#x20;

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/uoC4A2Up0LWw8b7vaKizH_image.png)

c) In the line, **OKTA\_URL**, include the main URL in the Okta account.&#x20;

d) In the line, **OKTA\_TOKEN**, include the token to access through API. To get this token, follow these steps:

- Access the <font color="#ff6900">**4biz**</font> application in Okta, select the "`Security > API`" menu, and then click on "**Create Token**". Name the token and click on "**Create Token**". It will be presented the token value to be copied on the line quoted above.

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/1OExMeStU7qxhct6uA8hd_image.png)

e) In the line, ***OKTA\_DOMAIN\_ALIAS***, include the domain of users coming from Okta.&#x20;

******<font color="#2166ae"><u>***5th Step***</u>***\:***</font>*&#x20;Synchronize Okta user on&#x20;*<font color="#ff6900">**4biz**</font>*:*

1. Within <font color="#ff6900">**4biz**</font>, access the "**Okta Config**" menu and register a new configuration by clicking on "**New**";

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/UDy2pnAh62ceYDYWDpEF2_image.png)

2\. Complete the fields with the necessary information:

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/6qP95Jeprnk-c6VHxqWWF_image.png)

- <u>**Description**</u>**:** introduce a definition of this new setting Okta;
- <u>**Alias**</u>**:** include the user domain that will be saved to the database. Example: okta\\[administrador@4biz.com](mailto\:administrador@4biz.com);
- <u>**URL domain**</u>**:&#x20;**&#x73;hould include the same value (URL) that was entered in the line *OKTA\_URL* in the "**4biz.cfg**" file;
- <u>**Token API**</u>**:** include the same value of the token inserted in the line *OKTA\_TOKEN* in the file "**4biz.cfg**";
- <u>**Group**</u>**:** insert the ID of the group in which the synchronized and registered user will belong in <font color="#ff6900">**4biz**</font>;
- <u>**Access Profile**</u>**:** insert the profile ID in which the synchronized and registered user will belong in <font color="#ff6900">**4biz**</font>;
- <u>**Application ID**</u>**:** include the application ID. This information can be retrieved from the Okta URL, as shown below:

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/fqWUTlG4UX9fheLjLORnr_image.png)

3\. Click on "**Save**" and then on "**Synchronize users**" to perform the operation.

******<font color="#2166ae"><u>***6th Step***</u>***\:***</font>*&#x20;Configure the Logout:*

1. Since Okta does not have a logout screen, in **parameter 377** of <font color="#ff6900">**4biz**</font>, we can insert some page address to redirect the user to the end of the session;
2. Set up the logout link also at the address (`Admin > Settings > Customization > Sign-Out-Page`), then check the option "**Use the custom sign-out page**". Therefore, enter the URL ([https://localhost:8443/4biz/saml/logout](https://localhost:8443/4biz/saml/logout)) with the appropriate adaptations (host and port), according to the image below:

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/Vz0dZcbHxCGhpTmWFkbSh_image.png)

:::hint{type="info"}
🖊 <u>**Note**</u>**:&#x20;**&#x57;hen **logging out** in <font color="#ff6900">**4biz**</font>, do not **log out** from the Okta, since users may have other applications in the Okta session. In contrast, if you do Okta **logout**, the user session in <font color="#ff6900">**4biz**</font> will be removed.
:::

## What to do next

Once the Okta integration with <font color="#ff6900">**4biz** </font>is complete, some <font color="#ff6900">**4biz** </font>parameters can be configured to better customize this integration. They are:

- The **parameter 445** (Name of the Administrator group in Okta) allows you to choose the administrator group in the Okta solution. If the user belongs to this chosen group, he/she will have the access profile defined as administrator. If this is not the case, your access profile will be the default profile defined by **parameter 39**.

