Differences

This shows you the differences between two versions of the page.

--- indigo_2024.1_documentation:indigo_web_server_certificates [2024/09/15 17:03] – [Chrome] davel17
+++ indigo_2024.1_documentation:indigo_web_server_certificates [2025/04/15 01:48] (current) – [Node Red Example] davel17
@@ Line 15: / Line 15: @@
 === Safari MacOS ===
-  - Open Keychain.
+**<color #ed1c24>Note:</color> Users who have upgraded to Sequoia (macOS 15).** Apple has replaced the default application for managing passwords with the Passwords app and moved the Keychain Access app to a system folder. The Keychain Access app is most easily found by opening Spotlight Search and searching for "Keychain Access.app". You can also reach it by browsing to ''///System/Library/CoreServices/Applications/Keychain Access.app//''.
+  - Open Keychain.
   - From the `File` menu, select `Import Items...`.
   - Point to //''../Web Assets/cert/indigo-cert.pem''// and select 'Open'.
@@ Line 21: / Line 22: @@
   - Keychain will mark the certificate with a warning that "This certificate has not been verified by a third party."
   - Double-click the certificate to open its info pane.
   - Maximize the //''Trust''// settings and find "When using this certificate:" and select "Always Trust".
   - Keychain should require a password to save the change.
   - You may need to click away from the certificate and then re-select it for the updated settings to be displayed in the Keychain list.
@@ Line 65: / Line 66: @@
 === Node Red Example ===
-;asldkfj;al
+The following example shows how to configure a Node Red flow that uses the Indigo Web Server (IWS) API to operate a lamp device. The example is only meant to show how to use a self-signed certificate and public key to enable the flow to connect to the IWS using ''//https//'' instead of ''//http//'' when using the IWS on a local network via ''//10.0.1.123//'', ''//127.0.0.1//'', or ''//localhost//'' (using the API via the Indigo Reflector Service uses a different CA-approved security certificate and the flow is configured the same as it would be using any API via ''//https//'').
+{{:indigo_2024.1_documentation:node_red_1_flow.png?600|Noe Red Image}}
+Using the flow via ''//https//'' requires a few settings. Enter the preferred URL to point at the local IWS address ''//10.0.1.123//'', ''//127.0.0.1//'', or ''//localhost//'' with the URL:
+<code>
+https://<INDIGO IP ADDRESS>:8176/v2/api/command/
+</code>
+for example,
+<code>
+https://10.0.1.123:8176/v2/api/command/
+</code>
+{{:indigo_2024.1_documentation:node_red_6_http_request_node.png?400|Node Red 6 HTTP Request Node Image}}
+select TLS, and use bearer authentication along with a valid token key (from your Indigo Account Authorizations).
+Then, use key and certificates from local files and point them to the certificate and public key files located in
+<code>/Library/Application Support/Perceptive Automation/Indigo 2024.1/Web Assets/cert/
+</code>
+{{:indigo_2024.1_documentation:node_red_7_http_request_node_tls_config.png?400|Node Red 7 HTTP Request Node Image}}
+Several other screenshots complete the example:
+|{{:indigo_2024.1_documentation:node_red_2_inject_node_turn_on.png?400|Node Red Inject Node Turn On Image}}|
+|{{:indigo_2024.1_documentation:node_red_3_inject_node_turn_on_json.png?400|Node Red Inject Node Turn On JSON Image}}|
+|{{:indigo_2024.1_documentation:node_red_4_inject_node_turn_off.png?400|Node Red Inject Node Turn Off Image}}|
+|{{:indigo_2024.1_documentation:node_red_5_inject_node_turn_off_json.png?400|Node Red Inject Node Turn Off JSON Image}}|
+|{{:indigo_2024.1_documentation:node_red_8_http_debug_node.png?400|Node Red HTTP Debug Node Image}}|