Difference between revisions of "Using secured connections"
Pavel.lobko (talk | contribs) |
Pavel.lobko (talk | contribs) |
||
| Line 16: | Line 16: | ||
'-url' '${surl}' \ | '-url' '${surl}' \ | ||
'-uid' '${uid}' \ | '-uid' '${uid}' \ | ||
| − | <span style="background:#00FFFF;> '-dcm_client_id'<span style="color:red;"> | + | <span style="background:#00FFFF;> '-dcm_client_id' '<span style="color:red;">-dcm_client_id</span>'</span> \ |
'-user' '${user}')) \ | '-user' '${user}')) \ | ||
INLLIBL(I2REST)" | INLLIBL(I2REST)" | ||
Revision as of 13:24, 29 June 2020
i2Rest Server uses standard IBM i GSK API to protect connections. All required parameters are configured using DCM, see detailed guide.
Basic configuration SSL secured variant(differences are highlighted in blue):
{
"gates":
{
"main" : {"url":"https://<host_name>[:port](for example api.i2rest.com:1234)", "dcm_server_id":"dcm_server_id"},
"management" : {"url":"http://<host_name>[:port] (for example api.i2rest.com:4321)"}
},
"session_systems":
[
{ "name" : "*ANONYMOUS",
"submit" : "SBMJOB JOB(I2RESTA) \
USER(${user}) \
CMD(CALL I2REST \
PARM('-session' \
'-url' '${surl}' \
'-uid' '${uid}' \
'-dcm_client_id' '-dcm_client_id' \
'-user' '${user}')) \
INLLIBL(I2REST)"
}
],
"pcmls":
[
{
"pcml_mount" : "echo",
"pcml_file" : "<complete name of i2restecho.pcml on IFS (for example /tmp/PCML/i2restecho.pcml)>",
"valid_in_anonymous" : true
}
]
}