Cloud Managed Networks

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

were the onboard app and profile installed successfully? are these APs running AOS10 firmware?

may be there is a device level configuration for the staff2 WLAN.

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

We are seeing a similar pattern.

Aruba TAC found an issue in the WLAN where names weren't consistent (I cannot remember which ones).

This needed a new onboarding link, + removing all references in manage known wifi on the clients - their theory was the certificate had different names and thus was flagged by windows.

However we are still seeing the issue, particularly if staff have multiple entra-joined windows 11 devices as wireless profiles are shared between the devices.

AOS10.6, CloudAuth using EntraID.

were the onboard app and profile installed successfully? are these APs running AOS10 firmware?

may be there is a device level configuration for the staff2 WLAN.

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

were the onboard app and profile installed successfully? are these APs running AOS10 firmware?

may be there is a device level configuration for the staff2 WLAN.

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

See my response. There is not a device level configuration.

were the onboard app and profile installed successfully? are these APs running AOS10 firmware?

may be there is a device level configuration for the staff2 WLAN.

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

Yes, we are seeing the same thing!

TAC found an issue within the WLAN SSIDs, causing a certificate error which meant the client sometimes rejected the cert, needing the click on connect.

We needed to re-issue the onboarding link and reset as well as removing the old wifi config.

However, we are still seeing this behaviour after this fix.

APs running AOS10.6.

Original Message:
Sent: Sep 16, 2024 07:55 AM
From: BatmanDL44
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

Yes, we are seeing the same thing!

TAC found an issue within the WLAN SSIDs, causing a certificate error which meant the client sometimes rejected the cert, needing the click on connect.

We needed to re-issue the onboarding link and reset as well as removing the old wifi config.

However, we are still seeing this behaviour after this fix.

APs running AOS10.6.

Original Message:
Sent: Sep 16, 2024 07:55 AM
From: BatmanDL44
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

Here is what I am seeing in screenshots.

Occurs to  entra joined devices, but had other issues on hybrid devices.

Original Message:
Sent: Sep 26, 2024 03:21 PM
From: garrymacg
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Yes, we are seeing the same thing!

TAC found an issue within the WLAN SSIDs, causing a certificate error which meant the client sometimes rejected the cert, needing the click on connect.

We needed to re-issue the onboarding link and reset as well as removing the old wifi config.

However, we are still seeing this behaviour after this fix.

APs running AOS10.6.

Original Message:
Sent: Sep 16, 2024 07:55 AM
From: BatmanDL44
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

This is exactly what we are experiencing as well and our machine are Entra ID joined / Intune Managed but this also happens on personal Windows machines and Macs managed by Mosyle MDM

Does it sometimes make you choose the certificate? See video attached

Here is what I am seeing in screenshots.

Occurs to  entra joined devices, but had other issues on hybrid devices.

Original Message:
Sent: Sep 26, 2024 03:21 PM
From: garrymacg
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Yes, we are seeing the same thing!

TAC found an issue within the WLAN SSIDs, causing a certificate error which meant the client sometimes rejected the cert, needing the click on connect.

We needed to re-issue the onboarding link and reset as well as removing the old wifi config.

However, we are still seeing this behaviour after this fix.

APs running AOS10.6.

Original Message:
Sent: Sep 16, 2024 07:55 AM
From: BatmanDL44
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

Have you configured Intune and Mosyle to provision the devices with a client certificate and SSID configuration?

The message displayed means that the client does not trust the (RADIUS/RadSec) server certificate, or that there is no configuration at all on the client. Central Cloud Authentication Onboarding should take care of that, but you should see as well 'Hotspot 2.0' and the (friendly) name of your network/organization on the SSID in Windows.

In most cases, either Intune/MDM is used to provision the SSID and client certificates for managed devices, then use ClearPass or another RADIUS service to authenticate the devices. Or for unmanaged devices, you use Central Cloud Authentication for the provisioning as well as for the authentication.

This is exactly what we are experiencing as well and our machine are Entra ID joined / Intune Managed but this also happens on personal Windows machines and Macs managed by Mosyle MDM

Does it sometimes make you choose the certificate? See video attached

Here is what I am seeing in screenshots.

Occurs to  entra joined devices, but had other issues on hybrid devices.

Original Message:
Sent: Sep 26, 2024 03:21 PM
From: garrymacg
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Yes, we are seeing the same thing!

TAC found an issue within the WLAN SSIDs, causing a certificate error which meant the client sometimes rejected the cert, needing the click on connect.

We needed to re-issue the onboarding link and reset as well as removing the old wifi config.

However, we are still seeing this behaviour after this fix.

APs running AOS10.6.

Original Message:
Sent: Sep 16, 2024 07:55 AM
From: BatmanDL44
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

Have you configured Intune and Mosyle to provision the devices with a client certificate and SSID configuration?

The message displayed means that the client does not trust the (RADIUS/RadSec) server certificate, or that there is no configuration at all on the client. Central Cloud Authentication Onboarding should take care of that, but you should see as well 'Hotspot 2.0' and the (friendly) name of your network/organization on the SSID in Windows.

In most cases, either Intune/MDM is used to provision the SSID and client certificates for managed devices, then use ClearPass or another RADIUS service to authenticate the devices. Or for unmanaged devices, you use Central Cloud Authentication for the provisioning as well as for the authentication.

This is exactly what we are experiencing as well and our machine are Entra ID joined / Intune Managed but this also happens on personal Windows machines and Macs managed by Mosyle MDM

Does it sometimes make you choose the certificate? See video attached

Here is what I am seeing in screenshots.

Occurs to  entra joined devices, but had other issues on hybrid devices.

Original Message:
Sent: Sep 26, 2024 03:21 PM
From: garrymacg
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Yes, we are seeing the same thing!

TAC found an issue within the WLAN SSIDs, causing a certificate error which meant the client sometimes rejected the cert, needing the click on connect.

We needed to re-issue the onboarding link and reset as well as removing the old wifi config.

However, we are still seeing this behaviour after this fix.

APs running AOS10.6.

Original Message:
Sent: Sep 16, 2024 07:55 AM
From: BatmanDL44
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

No we have not configured Intune and Mosyle to provision the devices with client certificate and SSID configuration. Please send documentation if you know if any on how to do this as Microsoft and Mosyle do not know how.

As stated in previous posts the devices are using Aruba Onboard not Clearpass to authenticate to the Aruba Cloud Auth network. Around 50% of the devices are BYOD so we do not managed them from Intune or Mosyle so pushing any configuration would be impossible. We can create a profile in Intune (provide documentation if you know of any). My understanding is Aruba Onboard is used for BYOD environments, correct me if I'm wrong.

How do we resolve this message, "The message displayed means that the client does not trust the (RADIUS/RadSec) server certificate, or that there is no configuration at all on the client." Using the Aruba Onboard product? This authentication error is happening on All device types. Android, MAC, Windows, etc. the only exception to the rule is iOS.

Have you configured Intune and Mosyle to provision the devices with a client certificate and SSID configuration?

The message displayed means that the client does not trust the (RADIUS/RadSec) server certificate, or that there is no configuration at all on the client. Central Cloud Authentication Onboarding should take care of that, but you should see as well 'Hotspot 2.0' and the (friendly) name of your network/organization on the SSID in Windows.

In most cases, either Intune/MDM is used to provision the SSID and client certificates for managed devices, then use ClearPass or another RADIUS service to authenticate the devices. Or for unmanaged devices, you use Central Cloud Authentication for the provisioning as well as for the authentication.

This is exactly what we are experiencing as well and our machine are Entra ID joined / Intune Managed but this also happens on personal Windows machines and Macs managed by Mosyle MDM

Does it sometimes make you choose the certificate? See video attached

Here is what I am seeing in screenshots.

Occurs to  entra joined devices, but had other issues on hybrid devices.

Original Message:
Sent: Sep 26, 2024 03:21 PM
From: garrymacg
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Yes, we are seeing the same thing!

TAC found an issue within the WLAN SSIDs, causing a certificate error which meant the client sometimes rejected the cert, needing the click on connect.

We needed to re-issue the onboarding link and reset as well as removing the old wifi config.

However, we are still seeing this behaviour after this fix.

APs running AOS10.6.

Original Message:
Sent: Sep 16, 2024 07:55 AM
From: BatmanDL44
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?

If you onboarded the client through Central, indeed for BYOD, you should not see any authentication prompts.

In case you do see warnings, please open a TAC case as there is nothing you can configure or change to my knowledge.

No we have not configured Intune and Mosyle to provision the devices with client certificate and SSID configuration. Please send documentation if you know if any on how to do this as Microsoft and Mosyle do not know how.

As stated in previous posts the devices are using Aruba Onboard not Clearpass to authenticate to the Aruba Cloud Auth network. Around 50% of the devices are BYOD so we do not managed them from Intune or Mosyle so pushing any configuration would be impossible. We can create a profile in Intune (provide documentation if you know of any). My understanding is Aruba Onboard is used for BYOD environments, correct me if I'm wrong.

How do we resolve this message, "The message displayed means that the client does not trust the (RADIUS/RadSec) server certificate, or that there is no configuration at all on the client." Using the Aruba Onboard product? This authentication error is happening on All device types. Android, MAC, Windows, etc. the only exception to the rule is iOS.

Have you configured Intune and Mosyle to provision the devices with a client certificate and SSID configuration?

The message displayed means that the client does not trust the (RADIUS/RadSec) server certificate, or that there is no configuration at all on the client. Central Cloud Authentication Onboarding should take care of that, but you should see as well 'Hotspot 2.0' and the (friendly) name of your network/organization on the SSID in Windows.

In most cases, either Intune/MDM is used to provision the SSID and client certificates for managed devices, then use ClearPass or another RADIUS service to authenticate the devices. Or for unmanaged devices, you use Central Cloud Authentication for the provisioning as well as for the authentication.

This is exactly what we are experiencing as well and our machine are Entra ID joined / Intune Managed but this also happens on personal Windows machines and Macs managed by Mosyle MDM

Does it sometimes make you choose the certificate? See video attached

Here is what I am seeing in screenshots.

Occurs to  entra joined devices, but had other issues on hybrid devices.

Original Message:
Sent: Sep 26, 2024 03:21 PM
From: garrymacg
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Yes, we are seeing the same thing!

TAC found an issue within the WLAN SSIDs, causing a certificate error which meant the client sometimes rejected the cert, needing the click on connect.

We needed to re-issue the onboarding link and reset as well as removing the old wifi config.

However, we are still seeing this behaviour after this fix.

APs running AOS10.6.

Original Message:
Sent: Sep 16, 2024 07:55 AM
From: BatmanDL44
Subject: Aruba Cloud Auth SSID asking users to connect even after authentication process is completed

Hello all, I'm relatively new to Aruba Central. We just installed our 67 535 APs 6 months ago. We are running an SSID using Cloud Auth to MS Entra ID. However, every time users connect to wifi they are being asked to physically click the network in settings and then click connect. They have the Aruba onboard app and profile installed in the app. I have opened a couple of tickets with Aruba TAC and they have no idea what is going on. To make matters more weird. We are seeing two of the same SSID even though there is only one in Aruba Central. When users click their wifi settings they can see Staff and Staff 2. We have never made a Staff 2 which confused Aruba TAC as well. Depending on the device type this shows up or does not. Its kinda random and inconsistent. But either way users still have to physically connect to Cloud Auth network by clicking a button.

Has anyone else see this happen?