This page shows all the applications within the organization whose access has been restricted for users. You can configure and add new applications as well.
When the administrator adds organizational site, a corresponding application ‘HawkkProtect Apps Portal’ is created using site details. Administrator can use this default application in the Firewall and DDoS policy. The administrator cannot delete or edit this application.
Further, the following details for all the applications is displayed.
Column Name | Description |
---|---|
Application Name | Name of the application. |
App Type | Type of application. |
IP Address / Domain Name | The web address/ domain name. |
Tags | The tags based on which access to the application is granted. |
Search | To search applications by their name. |
Add Filter | To add a filter. To know more, refer the Adding a filter to refine the view section on Visibility page. |
Export | To export the information displayed on this page in CSV file format. |
Add Application | To add an application. |
Note:
If a site is deleted, all the related applications on Application Catalog page become inactive. To make these applications active again, edit the applications and update the domain name. This is applicable only for auto-generated certificates.
Actions available with applications
When you hover over each application, the following options appear in the column next to Tags.
Action Icon | Action Label | Description |
---|---|---|
![]() |
Edit | To edit the application details. |
![]() |
Delete | To delete the application profile. |
![]() |
Side bar | To view the details of the application. |
- The applications can be sorted alphabetically by clicking the sorting symbol next to Application Name column.
- Bulk action: Select the checkboxes in front of the application names to perform bulk delete action on selected applications.
Note:
Only one tag is shown for each application. You can hover over the blue colored text next to the tag to view additional tags, if any.
When you click an application name, the following details are displayed in the right pane.
Name | Description |
---|---|
Application Name | Name of the application. |
Application Type | Type of application. |
IP Address / Domain Name | The web address/ Domain Name. |
App Type | Application type. |
External Domain Name | External domain name for the application. |
App Connector | The app connector that will be used to connect applications hosted on premises to site hosted on cloud environment. |
Tags | The tags applied to an application. |
Adding an application
To add a new application in the application catalog, follow these steps.
- Log on to the Seqrite HawkkProtect portal. Navigate to Application Catalog in the left navigation pane.
- On the Application Catalog page, Click Add Application. A new page appears.
- Enter the following information in the Application Information section.
- Enter the Application Name.
- Enter the Application Description.
- Upload the application logo.
- Enter the following details and select appropriate options (wherever applicable) in the Application Details section.
- Select one of the application types.
- Public Web Apps.
- Private Web Apps.
- Agent Based Apps.
- Enter the IP Address / Domain Name of the application.
- Select the appropriate protocol from the drop-down menu.
- The Port Value will be auto populated based on the selected protocol.
- Enter the relative URL path. For example: For the URL https://myapps.organization.com/careers/engineering, the relative URL path is /careers/engineering. The relative URL path must start with a forward slash ( / ).
- Enter the external domain name.
- Enter the tags applicable to the application.
- Enter the IP Address / Domain Name of the application.
- Select the appropriate protocol from the drop-down menu.
- The port value will be auto populated based on the selected protocol.
- If the selected protocol is either HTTP or HTTPS, enter the relative URL path. For example: for the URL https://myapps.organization.com/careers/engineering, the relative URL path is /careers/engineering. The relative URL path must start with a forward slash (/).
- If the selected protocol is Web RDP, select the RDP access type. If the selected RDP access type is ‘Limited Application Access’, enter the Remote Application Name, Remote Application Directory, and Remote Application Argument.
- Enter the external domain name.
- Select the appropriate App Connector Group.
- Enter the tags applicable to the application.
- The use of passphrases to generate private keys is not supported.
- At present, the only supported method for authentication to WebSSH applications is through private key files encrypted with RSA.
- Enter the IP Address / Domain Name of the application.
- Select the appropriate protocol from the drop-down menu.
- If the selected protocol is HTTPS, then the administrator should provide the Domain Name and not the IP address. The external domain name will be auto populated.
- Enter the external domain name.
- The port value will be auto populated based on the selected protocol.
- Select the appropriate App Connector from the drop-down.
- Enter the tags applicable to the application.
- Currently, to connect the SMB app in Windows OS, need to stop and disable server services and then need to reboot the device.
- The FTP protocol does not provide native support for using custom ports at present.
-
After this is done, click Add. The Applications page is displayed with the application details that you have configured.
Depending on the application type that you select, relevant parameters are displayed.
Public Web Apps
Enter the following information for the public web apps.
Private Web Apps
Enter the following information for the private web applications.
Providing support for importing a private key file while accessing webSSH applications
While configuring a WebSSH application the administrator can import the private key file as shown in the following image, so that the end user can access the application by entering the valid credentials.
Note:☛
Adding Agent Based Apps
Enter the following information for the agent-based applications.
Note:
For the Agent Based Apps the supported protocols are HTTP, HTTPS, RDP, SSH, Telnet, SMB, VNC, SFTP, FTP, and SCP.
Note: