Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| technical:pp-connect [2025/07/22 18:05] – [Simplicity is king] system | technical:pp-connect [2025/07/22 22:59] (current) – [Rd-Connect Mobile App] system | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| ====== Hotspot 2.0/ | ====== Hotspot 2.0/ | ||
| * One of the critical factors of a Hotspot2.0 deployment is the ease to onboard users. | * One of the critical factors of a Hotspot2.0 deployment is the ease to onboard users. | ||
| - | * The initial Hotspot 2.0 standard included Online Signup functionality (OSU) | + | * The initial Hotspot 2.0 standard included Online Signup functionality (OSU). |
| * This included a Signup Server which used XML and SOAP to communicate between it and the client' | * This included a Signup Server which used XML and SOAP to communicate between it and the client' | ||
| * If you think Hotspot 2.0 never took off, the OSU functionality ultimately failed even more to gain traction. | * If you think Hotspot 2.0 never took off, the OSU functionality ultimately failed even more to gain traction. | ||
| Line 27: | Line 27: | ||
| ------ | ------ | ||
| - | |||
| ====== Rd-Connect ====== | ====== Rd-Connect ====== | ||
| * We do something similar to the OpenRoaming Portal with Rd-Connect. | * We do something similar to the OpenRoaming Portal with Rd-Connect. | ||
| - | * Rd-Connect is a work in progress with extended functionality in mind in MDU deployments that uses a combination of Private PSK and Hotspot 2.0. | + | * <color #c91302>Rd-Connect is a work in progress with extended functionality in mind in MDU deployments that uses a combination of Private PSK and Hotspot 2.0.</ |
| * We currently have the following functionality / options | * We currently have the following functionality / options | ||
| * Choice to install as an mobile app on Android and Apple. | * Choice to install as an mobile app on Android and Apple. | ||
| Line 47: | Line 46: | ||
| * Certificate Authority and allowed FQDN for EAP Certificates | * Certificate Authority and allowed FQDN for EAP Certificates | ||
| </ | </ | ||
| + | |||
| + | ------ | ||
| ===== Install Rd-Connect (Server Side) ===== | ===== Install Rd-Connect (Server Side) ===== | ||
| + | * Rd-Connect runs on the same server as RADIUSdesk | ||
| + | <code bash> | ||
| + | cd /var/www | ||
| + | sudo git clone https:// | ||
| + | cd / | ||
| + | #For the RD-Connect Mobile UI | ||
| + | sudo ln -s ../ | ||
| + | </ | ||
| + | ------ | ||
| ===== Configure Rd-Connect ===== | ===== Configure Rd-Connect ===== | ||
| + | * Rd-Connect work as part of a RADIUSdesk deployment and rely on two items in RADIUSdesk to be configured properly in order for it to work as intended. | ||
| + | * Each RADIUS Realm in RADIUSdesk has optional configuration related to Hotspot2.0/ | ||
| + | * To allow user registration we will latch onto an existing Login Page where the User Registration is already configured. | ||
| + | * Once these two items have been configured we can do the last tweaks on Rd-Connect' | ||
| + | |||
| + | |||
| + | ------ | ||
| + | |||
| + | ==== Realm -> Hotspot2.0/ | ||
| + | * See the screenshot below as reference. | ||
| + | {{: | ||
| + | * If you use the FreeRADIUS config that is part of RADIUSdesk, the CA file is as follows: | ||
| + | <code bash> | ||
| + | -----BEGIN CERTIFICATE----- | ||
| + | MIIEMjCCAxqgAwIBAgIBATANBgkqhkiG9w0BAQUFADB7MQswCQYDVQQGEwJHQjEb | ||
| + | MBkGA1UECAwSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHDAdTYWxmb3JkMRow | ||
| + | GAYDVQQKDBFDb21vZG8gQ0EgTGltaXRlZDEhMB8GA1UEAwwYQUFBIENlcnRpZmlj | ||
| + | YXRlIFNlcnZpY2VzMB4XDTA0MDEwMTAwMDAwMFoXDTI4MTIzMTIzNTk1OVowezEL | ||
| + | MAkGA1UEBhMCR0IxGzAZBgNVBAgMEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UE | ||
| + | BwwHU2FsZm9yZDEaMBgGA1UECgwRQ29tb2RvIENBIExpbWl0ZWQxITAfBgNVBAMM | ||
| + | GEFBQSBDZXJ0aWZpY2F0ZSBTZXJ2aWNlczCCASIwDQYJKoZIhvcNAQEBBQADggEP | ||
| + | ADCCAQoCggEBAL5AnfRu4ep2hxxNRUSOvkbIgwadwSr+GB+O5AL686tdUIoWMQua | ||
| + | BtDFcCLNSS1UY8y2bmhGC1Pqy0wkwLxyTurxFa70VJoSCsN6sjNg4tqJVfMiWPPe | ||
| + | 3M/ | ||
| + | YgNW8IoaE+oxox6gmf049vYnMlhvB/ | ||
| + | rOme9Hg6jc8P2ULimAyrL58OAd7vn5lJ8S3frHRNG5i1R8XlKdH5kBjHYpy+g8cm | ||
| + | ez6KJcfA3Z3mNWgQIJ2P2N7Sw4ScDV7oL8kCAwEAAaOBwDCBvTAdBgNVHQ4EFgQU | ||
| + | oBEKIz6W8Qfs4q8p74Klf9AwpLQwDgYDVR0PAQH/ | ||
| + | MAMBAf8wewYDVR0fBHQwcjA4oDagNIYyaHR0cDovL2NybC5jb21vZG9jYS5jb20v | ||
| + | QUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmwwNqA0oDKGMGh0dHA6Ly9jcmwuY29t | ||
| + | b2RvLm5ldC9BQUFDZXJ0aWZpY2F0ZVNlcnZpY2VzLmNybDANBgkqhkiG9w0BAQUF | ||
| + | AAOCAQEACFb8AvCb6P+k+tZ7xkSAzk/ | ||
| + | GE8mTgHj5rCl7r+8dFRBv/ | ||
| + | Rt0vxuBqw8M0Ayx9lt1awg6nCpnBBYurDC/ | ||
| + | G9w84FoVxp7Z8VlIMCFlA2zs6SFz7JsDoeA3raAVGI/ | ||
| + | l2D4kF501KKaU73yqWjgom7C12yxow+ev+to51byrvLjKzg6CYG1a4XXvi3tPxq3 | ||
| + | smPi9WIsgtRqAEFQ8TmDn5XpNpaYbg== | ||
| + | -----END CERTIFICATE----- | ||
| + | </ | ||
| + | * **Domain Suffix Match** should then also be **uam.mesh-manager.com**. | ||
| + | * **Domain Name** and/or **RCOI LIST** should match the config of the Hotspot2.0 AP. | ||
| + | * See screenshot below where we set the Hotspot 2.0 Domain to **radiusdesk.com** on the Hotspot2.0/ | ||
| + | {{: | ||
| + | * We then choose an SSID in APdesk where we apply this Profile to: | ||
| + | {{: | ||
| + | |||
| + | |||
| + | -------- | ||
| + | |||
| + | ==== User Registration ==== | ||
| + | * Select a Login Page in the same cloud as the Realm where you configured the Realm -> Hotspot2.0/ | ||
| + | * Enable User Registration. | ||
| + | {{: | ||
| + | * The last remaining item is to configure Rd-Connect. | ||
| + | |||
| + | ------- | ||
| + | |||
| + | ==== Adjust Rd-Connect ==== | ||
| + | * Refer to the file: /// | ||
| + | |||
| + | <code JavaScript> | ||
| + | window.AppConfig = { | ||
| + | pageTitle | ||
| + | pageHeader | ||
| + | pageFooter | ||
| + | loginPageId : 50, | ||
| + | i18n : ' | ||
| + | }; | ||
| + | </ | ||
| + | * Most items are self explanatory. | ||
| + | * The **loginPageId** should match the **dynamic_id** value when you preview the Login Page where you configured User Registration e.g. https:// | ||
| + | |||
| + | ------ | ||
| ===== Rd-Connect Mobile App ===== | ===== Rd-Connect Mobile App ===== | ||
| + | * Everything is now in place for you to use Rd-Connect. | ||
| + | * Adjust the URL to match your RADIUSdesk server. | ||
| + | * http:// | ||
| + | * You can also install the app on your phone as a PWA. | ||
| + | * See screenshots below. | ||
| + | {{: | ||
| + | {{: | ||
| + | {{: | ||
| + | * After you logged in, you can download and install the Hotspot2.0/ | ||
| + | * In the next screenshot you can see where my phone used the downloaded and installed Hotspot2.0/ | ||
| + | * Note the Security is indicated as **Passpoint**. | ||
| + | * You will also see the name matches the name we specified under the Realm -> Hotspot2.0/ | ||
| + | {{: | ||
| + | * As you can see from this page that Rd-Connect makes user registration and on-boarding on Hotspot2.0/ | ||
| + | |||