I2Rest secured gate - Revision history

Pavel.lobko at 09:36, 14 April 2020

2020-04-14T09:36:14Z

Pavel.lobko at 09:24, 14 April 2020

2020-04-14T09:24:50Z

Pavel.lobko at 09:23, 14 April 2020

2020-04-14T09:23:52Z

Pavel.lobko at 09:23, 14 April 2020

2020-04-14T09:23:07Z

Pavel.lobko at 09:21, 14 April 2020

2020-04-14T09:21:04Z

Pavel.lobko at 09:17, 14 April 2020

2020-04-14T09:17:22Z

Pavel.lobko at 09:15, 14 April 2020

2020-04-14T09:15:30Z

Pavel.lobko: Created page with "{{DISPLAYTITLE:Parameters for starting secured i2Rest server instance}} <> == SSL parameters == i2Rest can serve client requests using protected HTTPs connectio..."

2020-04-14T09:14:04Z

Created page with "{{DISPLAYTITLE:Parameters for starting secured i2Rest server instance}} <<Anchor(SSL)>> == SSL parameters == i2Rest can serve client requests using protected HTTPs connectio..."

New page

{{DISPLAYTITLE:Parameters for starting secured i2Rest server instance}}

<<Anchor(SSL)>>
== SSL parameters ==

i2Rest can serve client requests using protected HTTPs connection. i2Rest is using standard Global Security Kit (GSKit) APIs in order to protect client connections. All parameters of protection are defined in [[Create Server Application|Server Application]]. In order to use HTTPs protocol, it is necessary to set up the following parameters in server configuration:

1. Set up HTTPs protocol in "gates" section and define server application name in dcm_server_id:<<BR>>

"gates":
{
"main" : {"url":"https://192.168.0.233:22088", "dcm_server_id":"MYSERVER", ...},
"manager" : {"url":"http://192.168.0.233:8080", ...},
"session" : {"url":"file:///tmp/session_gate", ...}
}

(here https protocol will be used only for connections with [[i2Rest Gates#main_gate|Main gate]], and all SSL settings will be defined by DCM server application MYSERVER)

2. When sessions are obliged to use secured connections with session gate, it is required to define -dcm_client_id parameter in "submit" command:<<BR>>
{{{
"session_systems":
[
{
"name" : "*LOCAL",
"submit" : "SBMJOB USER(${user}) CMD(CALL I2REST/I2REST PARM('-session' '-url' '${surl}' '-dcm_client_id' 'MYCLIENT' '-uid' '${uid}' '-user' '${user}' '-init'))"
}
]
}}}

← Older revision		Revision as of 09:24, 14 April 2020
Line 1:		Line 1:
	{{DISPLAYTITLE:Parameters for starting secured i2Rest server instance}}		{{DISPLAYTITLE:Parameters for starting secured i2Rest server instance}}
−
	== SSL parameters ==		== SSL parameters ==

← Older revision		Revision as of 09:17, 14 April 2020
Line 1:		Line 1:
	{{DISPLAYTITLE:Parameters for starting secured i2Rest server instance}}		{{DISPLAYTITLE:Parameters for starting secured i2Rest server instance}}

−	~~<<Anchor(SSL)>>~~
	== SSL parameters ==		== SSL parameters ==

@@ Line 2: / Line 2: @@
 == SSL parameters ==
-i2Rest can serve client requests using protected HTTPs connection. i2Rest is using standard Global Security Kit (GSKit) APIs in order to protect client connections. All parameters of protection are defined in [[Create Server Application|Server Application]]. In order to use HTTPs protocol, it is necessary to set up the following parameters in server configuration:
+i2Rest can serve client requests using protected HTTPs connection. i2Rest is using standard Global Security Kit (GSKit) APIs in order to protect client connections. All parameters of protection are defined in [[Create Server Application|Server Application]]. <br> In order to use HTTPs protocol, it is necessary to set up the following parameters in server configuration:
 . Set up HTTPs protocol in "gates" section and define server application name in dcm_server_id:

@@ Line 15: / Line 15: @@
 (here https protocol will be used only for connections with [[i2Rest Gates#main_gate|Main gate]], and all SSL settings will be defined by DCM server application MYSERVER)
-. When sessions are obliged to use secured connections with session gate, it is required to define -dcm_client_id parameter in "submit" command:<<BR>>
+. When sessions are obliged to use secured connections with session gate, it is required to define -dcm_client_id parameter in "submit" command:
    "session_systems":
+   [

@@ Line 8: / Line 8: @@
    "gates":
+   {
-      "main"    :   <code>{"url":"https://192.168.0.233:22088", "dcm_server_id":"MYSERVER", ...},</code>
+      "main"    :   {"url":"https://192.168.0.233:22088", "dcm_server_id":"MYSERVER", ...},
-      "manager" :   <code>{"url":"http://192.168.0.233:8080", ...},</code>
+      "manager" :   {"url":"http://192.168.0.233:8080", ...},
       "session" :   {"url":"file:///tmp/session_gate", ...}
+   }

@@ Line 6: / Line 6: @@
 i2Rest can serve client requests using protected HTTPs connection. i2Rest is using standard Global Security Kit (GSKit) APIs in order to protect client connections. All parameters of protection are defined in [[Create Server Application|Server Application]]. In order to use HTTPs protocol, it is necessary to set up the following parameters in server configuration:
-. Set up HTTPs protocol in "gates" section and define server application name in dcm_server_id:<<BR>>
+. Set up HTTPs protocol in "gates" section and define server application name in dcm_server_id:
    "gates":
+   {
@@ Line 18: / Line 17: @@
 . When sessions are obliged to use secured connections with session gate, it is required to define -dcm_client_id parameter in "submit" command:<<BR>>
-{{{
+  "session_systems":
 "session_systems":
-−
+     {
+        "name"   : "*LOCAL",
-      "name"   : "*LOCAL",
+        "submit" : "SBMJOB USER(${user}) CMD(CALL I2REST/I2REST PARM('-session' '-url' '${surl}' '-dcm_client_id' 'MYCLIENT' '-uid' '${uid}' '-user' '${user}' '-init'))"
-      "submit" : "SBMJOB USER(${user}) CMD(CALL I2REST/I2REST PARM('-session' '-url' '${surl}' '-dcm_client_id' 'MYCLIENT' '-uid' '${uid}' '-user' '${user}' '-init'))"
-−
+  ]