Skip to Content
Last modified by Alexander Mott on 2023/07/07 15:17
From version 12.1
edited by Craig Lewis
on 2021/09/22 14:51
Change comment: There is no comment for this version
To version 21.1
edited by Mark Kohlmann
on 2021/10/27 02:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.craig\.lewis@chiefintegrations\.com
1 +XWiki.mark\.kohlmann@chiefintegrations\.com
Content
... ... @@ -1,23 +1,48 @@
1 +===== Use ShowRunner version 3.010 or later =====
2 +
3 +Terminology:
4 +
5 +* Client Processor - Processor that will interact with hardware attached to the host procesor.
6 +* CWS - Crestron Web Server, the processor's internal web server
7 +* Host Processor (Server) - Processor that hosts the physical hardware
8 +* LWAPI - Lightweight API (CoAP)
9 +* User Page Auth - Requires a username and password to access the internal web server (CWS) on the processor.  3-series always has this enabled if authentication is activated.  4-series processors have an option to have user page auth on or not (default is off).
10 +
11 +Steps:
12 +
13 +1. [[Setup Host Processor>>||anchor="Host processor (LWAPI Server) Setup (DIN-AP3 @ 10.44.5.91)"]]
14 +11. Verify processor configuration
15 +11. Verify LWAPI is enabled
16 +11. Create API User
17 +11. Create CWS User (if necessary)
18 +11. Save the configuration
19 +1. [[Setup Client Processor>>||anchor="Client processor (LWAPI Client) Setup (DIN-AP4) Version 3.011 or newer"]]
20 +11. Define the remote system
21 +11. Setup auth for the remote system
22 +11. Save the configuration
23 +
1 1  ===== Host processor (LWAPI Server) Setup (DIN-AP3 @ 10.44.5.91) =====
2 2  
3 3  Steps 1-3 and 5 always needed.
4 4  
5 5  1. If 3-series, Enable Authentication [##authentication on##] or SSL [##ssl self##] if not already enabled.  4-Series have authentication enabled by default.  User Page Auth should be turned off on 4-series.
6 -1. Enable LWAPI In Config (@ root level):
29 +1. Enable LWAPI
30 +From Console (v 3.011 or later):
31 +## sr lwapi enable true##
32 +In Config (@ root level):
7 7  ## "LwApiEnable": true,
8 8   "LwApiSecurityLevel": "Auth",##
9 -1. Create an API User and record the Key and Secret.  User group must have //LWAPI //role and //Execute //permissions.  //Lightweight API Users// group has been created for this purpose:
35 +1. Create an API User and record the Key and Secret.  User group must have //LWAPI //role and //Execute //permissions.  This allows the  //Lightweight API Users// group has been created for this purpose:
10 10  ##DIN-AP3>sradmin add api user "Central Control" "Lightweight API Users"
11 11  API User Central Control generated with Group permissions Lightweight API Users and Key: (% style="color:blue" %)**YTd2pQn7sjwiOWD9NqCIWw**(%%) Secret: (% style="color:orange" %)**OeiQEFo_-EDfc7sQe_qRpeQzSkZjylV2roa76utpJLI**(%%)##
12 -
13 -1. If 3-series w/ auth enabled or 4-series with user page auth enabled then add a remote user with permissions to connect to the control system.  This is done by adding a local user to the system with connect privileges.  Sample values shown, do not re-use these.
38 +1. If 3-series w/ auth enabled or 4-series with user page auth enabled then add a remote user with permissions to connect to the control system.  This is done by adding a local user to the system with user privileges.  Sample values shown, do not re-use these.
14 14  ##DIN-AP3>adduser -N:(% style="color:purple" %)**lwapi**(%%) -P:(% style="color:darkgoldenrod" %)**dMFN9pJJXjWLGd7t**(%%)
15 15  User account was successfully created.
16 -DIN-AP3>addusertogroup -N:lwapi -G:Connects
17 -'lwapi' was successfully added to group 'Connects'.##
18 -1. Save the configuration and restart ShowRunner™
41 +DIN-AP3>addusertogroup -N:lwapi -G:Users
42 +'lwapi' was successfully added to group 'Users'.##
43 +1. Save the configuration
19 19  
20 -===== Client processor (LWAPI Client) Setup (DIN-AP4) =====
45 +===== Client processor (LWAPI Client) Setup (DIN-AP4) Version 3.011 or newer =====
21 21  
22 22  Steps 1-3 and 6 always needed.
23 23  
... ... @@ -28,6 +28,25 @@
28 28   "Label": "HUB-1-1",
29 29   "ConnectionType": "LWAPI"
30 30   },##
56 +1. Add Users :
57 +if CWS User is not needed:
58 +##DIN-AP4>sr remote system auth (% style="color:darkcyan" %)**1**(%%) (% style="color:blue" %)**YTd2pQn7sjwiOWD9NqCIWw**(%%) (% style="color:orange" %)**OeiQEFo_-EDfc7sQe_qRpeQzSkZjylV2roa76utpJLI**(%%)##
59 +if CWS User is needed:
60 +##DIN-AP4>sr remote system auth (% style="color:darkcyan" %)**1**(%%) (% style="color:blue" %)**YTd2pQn7sjwiOWD9NqCIWw**(%%) (% style="color:orange" %)**OeiQEFo_-EDfc7sQe_qRpeQzSkZjylV2roa76utpJLI **(% style="color:purple" %)**lwapi**(%%)** (% style="color:darkgoldenrod" %)dMFN9pJJXjWLGd7t(%%)**
61 +Success##
62 +1. Save the configuration
63 +
64 +===== Client processor (LWAPI Client) Setup (DIN-AP4) Version 3.010 or earlier =====
65 +
66 +Steps 1-3 and 6 always needed.
67 +
68 +1. Define remote system in the config:
69 +## {
70 + "SystemId": (% style="color:darkcyan" %)1(%%),
71 + "IpAddressOrHostname": "10.44.5.91",
72 + "Label": "HUB-1-1",
73 + "ConnectionType": "LWAPI"
74 + },##
31 31  1. Add remote user for LWAPI (this is the key and secret created on the host):
32 32  ##DIN-AP4>sradmin add remote user HUB-1 (% style="color:blue" %)**YTd2pQn7sjwiOWD9NqCIWw**(%%) (% style="color:orange" %)**OeiQEFo_-EDfc7sQe_qRpeQzSkZjylV2roa76utpJLI**(%%)
33 33  Remote User HUB-1 ((% style="color:green" %)//**1a920b8b-3ab8-44bd-bc7b-0fc77abf0a13**//(%%)) added with Group permissions Remote Connection##