Skip to content

Commit a70cc6c

Browse files
PSR-SMMPSR-SMM
committed
Added Version 9.3 in old structure, added description for custom branding.
1 parent cba02ce commit a70cc6c

File tree

315 files changed

+14891
-2
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

315 files changed

+14891
-2
lines changed

‎docs/passwordsecure/9.3/configuration/_category_.json‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
{
2+
"label": "Configuration",
3+
"position": 40,
4+
"collapsed": true,
5+
"collapsible": true,
6+
"link": {
7+
"type": "doc",
8+
"id": "configuration"
9+
}
10+
}

‎docs/passwordsecure/9.3/configuration/advancedview/_category_.json‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
{
2+
"label": "Advanced View",
3+
"position": 20,
4+
"collapsed": true,
5+
"collapsible": true
6+
}

‎docs/passwordsecure/9.3/configuration/advancedview/clientmodule/_category_.json‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
{
2+
"label": "Client Module",
3+
"position": 20,
4+
"collapsed": true,
5+
"collapsible": true,
6+
"link": {
7+
"type": "doc",
8+
"id": "client_module"
9+
}
10+
}

‎docs/passwordsecure/9.3/configuration/advancedview/clientmodule/applications/_category_.json‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
{
2+
"label": "Applications",
3+
"position": 80,
4+
"collapsed": true,
5+
"collapsible": true,
6+
"link": {
7+
"type": "doc",
8+
"id": "applications"
9+
}
10+
}

‎docs/passwordsecure/9.3/configuration/advancedview/clientmodule/applications/applications.md‎

Lines changed: 110 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,110 @@
1+
---
2+
title: "Applications"
3+
description: "Applications"
4+
sidebar_position: 80
5+
---
6+
7+
# Applications
8+
9+
## What are applications?
10+
11+
Applications can be used to configure automated logins to various systems. Especially when combined
12+
with various protective mechanisms, the company benefits in terms of security because complex
13+
passwords are automated and entered in the login masks in concealed form. Various types are
14+
available, such as Remote Desktop (**RDP**), Secure Shell (**SSH**), general applications (**SSO**)
15+
and web applications. The Single Sign On Engine offers countless configuration options to enable
16+
automatic logon to almost any kind of software.
17+
18+
![applications module](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/applications_1-en.webp)
19+
20+
- Automatic logins to websites are covered by the
21+
[Autofill Add-on](/docs/passwordsecure/9.2/configuration/autofilladdon/autofill_add-on.md).
22+
23+
## The four types of applications
24+
25+
Netwrix Password Secure varies between four different types of applications: RDP, SSH, SSO and web
26+
applications.
27+
28+
![new application](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/applications_2-en.webp)
29+
30+
In terms of how they are handled, **RDP and SSH** applications can be covered together. Both types
31+
of application can be (optionally) "embedded" in Netwrix Password Secure. The relevant session then
32+
opens in its own tab in the [Reading pane](/docs/passwordsecure/9.2/configuration/advancedview/operationandsetup/reading_pane.md).
33+
All other forms of automatic logins are summarized in the **SSO applications** and **web
34+
applications** categories. How exactly these logins are created and used is covered in the next
35+
section and in the web applications chapter. They include all forms of Windows login masks and also
36+
applications for websites. In contrast to RDP and SSH applications, they cannot be started embedded
37+
in Netwrix Password Secure but are instead opened as usual in their own window. These SSO
38+
applications need to be defined in advance. In Netwrix Password Secure, this is also described as
39+
[Learning the applications](/docs/passwordsecure/9.2/configuration/advancedview/clientmodule/applications/learningtheapplications/learning_the_applications.md). In contrast,
40+
RDP and SSH can be both completely defined and also started within Netwrix Password Secure.
41+
42+
## RDP and SSH
43+
44+
A new RDP/SSH application can be created via the ribbon or also the context menu that is accessed
45+
using the right mouse button. A corresponding form opens in each case where the variables for a
46+
connection can be defined.
47+
48+
![new application](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/applications_3-en.webp)
49+
50+
These variables also correspond precisely to those (using the example of RDP here) that can be
51+
configured when creating an RDP connection via “mstsc”. Whether the connections should be started in
52+
a tab, full screen mode or in a window can be defined in the field **"window mode"**.
53+
54+
## Working with RDP and SSH applications
55+
56+
If you have created e.g. an RDP connection, this can now also be directly started via the ribbon.
57+
The connection to the desired session can be established via the icon **Establish RDP connection**.
58+
59+
![estabish RDP](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/applications_4-en.webp)
60+
61+
Netwrix Password Secure now attempts to log in to the target system with the information available.
62+
Data that are not saved in the form will be directly requested when opening the session. It is thus
63+
also possible to only enter the IP address and/or the password after starting the Netwrix Password
64+
Secure application. If all data has been retrieved, the RDP session will open in a tab – if so
65+
defined (Window mode field in the application):
66+
67+
![RDP session](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/applications_5-en.webp)
68+
69+
## Logging in via SSH certificates
70+
71+
It is also possible to complete the authentication process using SSH certificates. For this purpose,
72+
the certificate is saved as a document in .ppk format. (It may be necessary to firstly approve this
73+
file ending in the settings). The document is then linked to the record via the footer. The record
74+
does not need to have a password. However, it is necessary for the record to be linked to a SSH
75+
application.
76+
77+
## Linking records and applications
78+
79+
The application defines the requirements for the desired connection and also optionally for the
80+
target system. By linking records with applications, the complete login process can be automated. If
81+
the record now also supplies the user name and password, all of the information required for the
82+
login is available. Applications and records are linked via the "Start" tab in the ribbon. If this
83+
link to a record is established, a 1-click login to the target system is possible.
84+
85+
![linking RDP](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/applications_6-en.webp)
86+
87+
The following example illustrates this process using an RDP connection:
88+
89+
![RDP Connection](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/applications_7-en.webp)
90+
91+
A record can also be linked to multiple target systems in this manner. The user name and record are
92+
supplied by the record, while all other information necessary for the login is supplied by the
93+
different applications. In the following example, a record (user name and password) is linked to
94+
multiple access points.
95+
96+
![multiple access points](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/applications_8-en.webp)
97+
98+
This is generally a very common scenario. Nevertheless, it should be noted that accessing multiple
99+
servers with one single password is questionable from a security standpoint. It is generally
100+
recommended that a unique password is issued for every server/access point.
101+
102+
NOTE: It is possible to leave the **IP address** field empty in the application. If an **IP
103+
address** field exists in the linked record then this address will be used. If there is also no IP
104+
address in the record, a popup window will appear in which the desired IP address can be entered
105+
manually.
106+
107+
Alternatively, it is possible to connect several records with one RDP connection. In this way, you
108+
can combine different users with an RDP connection and register them straightforward.
109+
110+
![connect RDP sessions](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/applications_9-en.webp)

‎docs/passwordsecure/9.3/configuration/advancedview/clientmodule/applications/configuration_of_saml.md‎

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
title: "Configuration of SAML"
3+
description: "Configuration of SAML"
4+
sidebar_position: 30
5+
---
6+
7+
# Configuration of SAML
8+
9+
## What is SAML?
10+
11+
The Security Assertion Markup Language (SAML) is an XML framework for exchanging authentication and
12+
authorization information. It provides functions to describe and transmit security-related
13+
information. This means that you can use one set of credentials to log in to many different
14+
websites. It is much easier to manage one login per user than separate logins for email, Customer
15+
Relationship Management (CRM) software, Active Directory, and more.
16+
17+
## Preconditions
18+
19+
In order for the users to be able to use SAML, "SMTP" must be set up and an e-mail address must be
20+
stored with the corresponding users. In addition, the Web Application is mandatory. Therefore, the
21+
Web Application must already be "set up or installed".
22+
23+
## Configuration
24+
25+
In order to create **SAML applications**, SAML must **first** be activated.
26+
27+
This is implemented in the settings of the database in the Server Manager:
28+
29+
![activate SAML](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/configuration_of_saml/configuration_of_saml_1-en.webp)
30+
31+
As soon as the check box is ticked, the next step is to enter the URL of the Web Application. The
32+
SAML configuration screen should then look like this:
33+
34+
![SAML configuration ](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/configuration_of_saml/configuration_of_saml_2-ewn.webp)
35+
36+
The screen is left open and the configuration is continued at the Advanced view. To do this, log on
37+
to the client as usual and switch to the **Applications** module. Select a **new SAML application**
38+
and fill it with the relevant data from the service provider.
39+
40+
NOTE: The data of the service provider, which are entered in the Advanced view, can be found at the
41+
respective provider. This differs from provider to provider.
42+
43+
![new SAML application](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/configuration_of_saml/configuration_of_saml_3-en.webp)
44+
45+
In addition, the data must be stored in the **Server Manager** at the service provider.
46+
47+
After the successful entry of all data, the last necessary step is the verification of the user.
48+
This is done by clicking on the tile. This gives the user an e-mail with which he can verify
49+
himself.
50+
51+
![SAML tile in LightClient](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/configuration_of_saml/configuration_of_saml_4-en.webp)
52+
53+
After verification, the **SAML application** can be started from the Basic view view.
54+
55+
**CAUTION:** As this is a passwordless authentication, it is not necessary to link the **SAML
56+
application** with a password.
57+
58+
NOTE: Setup and configuration instructions for
59+
[SAML Application for Dropbox](/docs/passwordsecure/9.2/configuration/advancedview/clientmodule/applications/exampleapplications/saml_application_for_dropbox.md) and
60+
[SAML application for Postman](/docs/passwordsecure/9.2/configuration/advancedview/clientmodule/applications/exampleapplications/saml_application_for_postman.md)can be
61+
found in the corresponding chapters.

‎docs/passwordsecure/9.3/configuration/advancedview/clientmodule/applications/exampleapplications/_category_.json‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
{
2+
"label": "Example Applications",
3+
"position": 40,
4+
"collapsed": true,
5+
"collapsible": true,
6+
"link": {
7+
"type": "doc",
8+
"id": "example_applications"
9+
}
10+
}

‎docs/passwordsecure/9.3/configuration/advancedview/clientmodule/applications/exampleapplications/example_applications.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: "Example Applications"
3+
description: "Example Applications"
4+
sidebar_position: 40
5+
---
6+
7+
# Example Applications
8+
9+
In this section you'll find examples for applications.
10+
11+
- [SAP GUI logon - SSO Application](/docs/passwordsecure/9.2/configuration/advancedview/clientmodule/applications/exampleapplications/sap_gui_logon_-_sso_application.md)
12+
- [SAML Application for Dropbox](/docs/passwordsecure/9.2/configuration/advancedview/clientmodule/applications/exampleapplications/saml_application_for_dropbox.md)
13+
- [SAML application for Postman](/docs/passwordsecure/9.2/configuration/advancedview/clientmodule/applications/exampleapplications/saml_application_for_postman.md)

‎docs/passwordsecure/9.3/configuration/advancedview/clientmodule/applications/exampleapplications/saml_application_for_dropbox.md‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
title: "SAML Application for Dropbox"
3+
description: "SAML Application for Dropbox"
4+
sidebar_position: 20
5+
---
6+
7+
# SAML Application for Dropbox
8+
9+
## SAML Configuration Example for Dropbox
10+
11+
This chapter explains how to configure the SAML application for **Dropbox**. It is assumed that
12+
[Configuration of SAML](/docs/passwordsecure/9.2/configuration/advancedview/clientmodule/applications/configuration_of_saml.md) has already been
13+
activated in the Server Manager.
14+
15+
- Log in as administrator at the **Dropbox**
16+
- Open the Admin Console
17+
18+
![Admin Console](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/examples/saml_examples/saml_dropbox_1-en.webp)s
19+
20+
- Open Settings
21+
22+
![settings dropbox](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/examples/saml_examples/saml_dropbox_2-en.webp)
23+
24+
- Single Sign On
25+
26+
![SSO dropbox](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/examples/saml_examples/saml_dropbox_3-en.webp)
27+
28+
- This is where the data SSO URL and the certificate from the Server Manager must be deposited.
29+
30+
![database settings](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/examples/saml_examples/saml_dropbox_4-en.webp)
31+
32+
- In the Advanced view, a new SAML application must be created in the Applications module.
33+
- Then the target page (login URL) and the XML file must be stored in the application.
34+
35+
![login with SAML](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/examples/saml_examples/saml_dropbox_5-en.webp)
36+
37+
The XML file must look like [this](https://cdn.manula.com/user/3511/docs/dropbox.xml).
38+
39+
- The application can now be executed via the Basic view.

‎docs/passwordsecure/9.3/configuration/advancedview/clientmodule/applications/exampleapplications/saml_application_for_postman.md‎

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
title: "SAML application for Postman"
3+
description: "SAML application for Postman"
4+
sidebar_position: 30
5+
---
6+
7+
# SAML application for Postman
8+
9+
## SAML configuration example for Postman
10+
11+
This chapter explains how to configure the SAML application for **Postman**. It is assumed that
12+
[Configuration of SAML](/docs/passwordsecure/9.2/configuration/advancedview/clientmodule/applications/configuration_of_saml.md) has already been
13+
activated in the Server Manager.
14+
15+
- First, you register with Postman.
16+
- After logging in, click on the avatar and select "**Settings**".
17+
18+
![settings postman](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/examples/saml_examples/saml_postman_1-en.webp)
19+
20+
- Then click on **Authentication**. Select a new method in the upper right corner.
21+
22+
![option authentication postman](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/examples/saml_examples/saml_postman_2-en.webp)
23+
24+
- Here the Authentication Type must be defined with **SAML 2.0** and any useful Authentication Name.
25+
26+
![add authentication method](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/examples/saml_examples/saml_postman_3-en.webp)
27+
28+
Then you come to the actual configuration.
29+
30+
- Store Provider Details
31+
- **Identity Provider Details** The data from the Server Manager is uploaded as XML or stored
32+
manually.
33+
34+
![postman identity provider details](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/examples/saml_examples/saml_postman_4-en.webp)
35+
36+
- **Service Provider Details** The service provider details are now copied to the application in the
37+
Netwrix Password Secure Client.
38+
39+
![postman service provider details](/images/passwordsecure/9.2/configuration/advanced_view/clientmodule/applications/examples/saml_examples/saml_postman_5-en.webp)
40+
41+
NOTE: Please note that a **Relay State** is required. This value can be created in the **Configure
42+
Identity Provider Details View**.

0 commit comments

Comments
 (0)