IRIS General description - Versionsgeschichte

Sbaumbach: /* Challenges */

2023-12-07T07:59:35Z

Challenges

Sbaumbach: /* Challenges */

2023-12-07T07:59:17Z

Challenges

Sbaumbach am 16. Februar 2023 um 15:35 Uhr

2023-02-16T15:35:19Z

Lbanik: /* Challenges */

2023-02-16T15:03:18Z

Challenges

Lbanik: /* IRIS in the cloud environment */

2023-02-16T15:02:18Z

IRIS in the cloud environment

Lbanik am 16. Februar 2023 um 15:00 Uhr

2023-02-16T15:00:33Z

Lbanik am 16. Februar 2023 um 14:59 Uhr

2023-02-16T14:59:23Z

Lbanik: bilder auf eng

2023-02-16T14:40:04Z

bilder auf eng

Lbanik am 16. Februar 2023 um 14:23 Uhr

2023-02-16T14:23:37Z

Lbanik am 16. Februar 2023 um 14:18 Uhr

2023-02-16T14:18:56Z

@@ Zeile 77: / Zeile 77: @@
 We would like to point out at this point that the introduction of a security-relevant application such as IRIS can also bring with it various challenges and the security of the overall system must also be regularly checked from all sides.
-We have described further details on the requirements for an installation on our [[Index.php?title=IRIS System requirements|IRIS system requirements]] page.
+We have described further details on the requirements for an installation on our [[IRIS System requirements|IRIS system requirements]] page.
 In addition, however, these security requirements also make ERP system connectivity more complex. Additional challenges arise for the ERP system, which must also implement these requirements at least as a client of the shipping system.

@@ Zeile 77: / Zeile 77: @@
 We would like to point out at this point that the introduction of a security-relevant application such as IRIS can also bring with it various challenges and the security of the overall system must also be regularly checked from all sides.
-We have described further details on the requirements for an installation on our [[IRIS system requirements]] page.
+We have described further details on the requirements for an installation on our [[Index.php?title=IRIS System requirements|IRIS system requirements]] page.
 In addition, however, these security requirements also make ERP system connectivity more complex. Additional challenges arise for the ERP system, which must also implement these requirements at least as a client of the shipping system.
@@ Zeile 85: / Zeile 85: @@
 * Only possible with our latest [https://interface.heidler-strichcode.de/ REST interface]
 * Requests only via an HTTPS connection
-* Authentifizierung mit [https://en.wikipedia.org/wiki/OAuth OAuth2] (nur über die "Authorization Code" Methode)
+* Authentication using [[wikipedia:OAuth|OAuth2]] (Authorization Code / Client Credentials)

← Nächstältere Version		Version vom 16. Februar 2023, 15:35 Uhr
Zeile 1:		Zeile 1:
	[[de:IRIS Allgemeine Beschreibung]]		[[de:IRIS Allgemeine Beschreibung]]
		+	[[IRIS cloud system\|IRIS]] enables you to securely publish functions of the HVS32 dispatch system into the public internet (cloud capability).

	== Issues with cloud systems ==		== Issues with cloud systems ==

@@ Zeile 76: / Zeile 76: @@
 We would like to point out at this point that the introduction of a security-relevant application such as IRIS can also bring with it various challenges and the security of the overall system must also be regularly checked from all sides.
-We have described further details on the requirements for an installation on our [[IRIS Systemvoraussetzungen]] page.
+We have described further details on the requirements for an installation on our [[IRIS system requirements]] page.
 In addition, however, these security requirements also make ERP system connectivity more complex. Additional challenges arise for the ERP system, which must also implement these requirements at least as a client of the shipping system.

← Nächstältere Version		Version vom 16. Februar 2023, 15:02 Uhr
Zeile 59:		Zeile 59:
	Authenticated: Each user is given a personal account in the IRIS system with which to log in.		Authenticated: Each user is given a personal account in the IRIS system with which to log in.

−	Authorized: Authorizations for functions in the dispatch system can be assigned for each user, according to the [https://en.wikipedia.org/wiki/Role-based_access_control]	+	Authorized: Authorizations for functions in the dispatch system can be assigned for each user, according to the [https://en.wikipedia.org/wiki/Role-based_access_control RBAC system]

@@ Zeile 29: / Zeile 29: @@
 |-
 |'''+''' Only minor change effort for existing systems
-|'''+''' Also accessible from [https://de.wikipedia.org/wiki/Software_as_a_Service SaaS] ERP systems
+|'''+''' Also accessible from [https://en.wikipedia.org/wiki/Software_as_a_Service SaaS] ERP systems
 |-
 |'''-''' Only possible with self-hosted (installed) ERP system
-[https://de.wikipedia.org/wiki/Software_as_a_Service SaaS] based ERP systems are not possible.
+[https://en.wikipedia.org/wiki/Software_as_a_Service SaaS] based ERP systems are not possible.
 |'''+''' Developed according to the latest safety standards
 |-
@@ Zeile 59: / Zeile 59: @@
 Authenticated: Each user is given a personal account in the IRIS system with which to log in.
-Authorized: Authorizations for functions in the dispatch system can be assigned for each user, according to the [https://de.wikipedia.org/wiki/Role_Based_Access_Control RBAC-System]
+Authorized: Authorizations for functions in the dispatch system can be assigned for each user, according to the [https://en.wikipedia.org/wiki/Role-based_access_control]
@@ Zeile 81: / Zeile 81: @@
 Bitte planen Sie deshalb auch ein Gespräch mit Ihrem ERP-System-Hersteller, um diese Anforderungen zu besprechen. Hierzu zählen u.a.:
-* Only possible with our latest [https://interface.heidler-strichcode.de/ REST-Schnittstelle]
+* Only possible with our latest [https://interface.heidler-strichcode.de/ REST interface]
 * Requests only via an HTTPS connection
-* Authentifizierung mit [https://de.wikipedia.org/wiki/OAuth OAuth2] (nur über die "Authorization Code" Methode)
+* Authentifizierung mit [https://en.wikipedia.org/wiki/OAuth OAuth2] (nur über die "Authorization Code" Methode)

@@ Zeile 3: / Zeile 3: @@
 == Issues with cloud systems ==
 In principle, the HVS32 can be operated in cloud environments without hesitation, provided that the connection from the upstream system (ERP or WMS, hereinafter referred to as just ERP for simplicity) to the HVS32 is in a shared, secure, internal network.
+[[Datei:IRIS internal network.png|alternativtext=|zentriert|rahmenlos|717x717px]]
-[[Datei:IRIS internes Netzwerk.png|zentriert|rahmenlos|717x717px]]Problems arise, however, when a connection is to take place across networks:
+Problems arise, however, when a connection is to take place across networks:
-[[Datei:IRIS Problem Netzwerkübergreifend.png|zentriert|rahmenlos|702x702px]]
+[[Datei:IRIS Problem across networks.png|alternativtext=|zentriert|rahmenlos|702x702px]]
 Then this connection between two networks must be secured.
@@ Zeile 53: / Zeile 52: @@
 == IRIS in the cloud environment ==
 If you decided to use IRIS, the IRIS system would integrate with your internal corporate or cloud network as follows:
-[[Datei:IRIS im Netzwerk.png|zentriert|rahmenlos|694x694px]]
+[[Datei:IRIS in the network.png|alternativtext=|zentriert|rahmenlos|694x694px]]
 All requests to IRIS are encrypted, authenticated, and authorized.

← Nächstältere Version		Version vom 16. Februar 2023, 14:18 Uhr
Zeile 8:		Zeile 8:

	Then this connection between two networks must be secured.		Then this connection between two networks must be secured.
		+
		+	Secured means: Both the connection must be encrypted and each incoming connection must be authenticated and authorized.
		+
		+	There are two possibilities for this. The bridging of the networks by means of VPN or the secured publication of the HVS32 functions to the Internet with IRIS, a software developed by Heidler Strichcode.

	== VPN vs IRIS ==		== VPN vs IRIS ==