when you use Central cloud guest, the pre-auth user role is #guest#_" and the authenticated guests will have the name of SSID as the user-role.
The preauth role with Cloud guest only allows DHCP/DNS and the cloud guest captive portal URL and I don't think one can modify it.
------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
------------------------------
Original Message:
Sent: Oct 17, 2024 08:37 AM
From: Notknown
Subject: Client Role before Cloud Guest Registration?
We are currently testing to Implement a better and more manageable (Role Based) Guest WiFi into our Infrastructure, so we built a Test SSID that uses Centrals "Cloud Guest" feature with Self Registration via Mail (as on screenshot below if necessary). It works the way we want it to, after 5 minutes of not putting in Login Information, the device loses Access to the Internet.
But what I noticed during the test, a client that is connected but didnt successfully register yet, has a different role than a User who succssfully registered (ends with "_#guest#_"), and i have no way of seeing the first role anywhere, even less being able to change it. i also didnt find anything about it in the cloud guest /captive portal docus by Aruba.
what is that additional pre-Registration Role and what does it permit/deny access to?