vSZ 5.1.x Administrators - Active Directory

[james_mcmillan_]

Hi

I have a vSZ (v5.1.2.0.302), and am trying to configure an AAA server for SmartZone Administrators.  The manual doesn't seem to be giving me what I need - or at least, I'm not seeing the wood for the trees.  I also have a couple of questions to follow..

I've configured an AAA AD server: Administrators -> Admins & Roles -> AAA:

Name: domain.local
Type: Active Directory
Realm: domain.local
Default Role Mapping: Off
IP address: 1.2.3.4
Port: 389
Windows Domain Name: dc=domain,dc=local

Test AAA is a success, but:

1. How do I actually add AD users or groups to 'Administrators'?
2. How can I add a second Domain Controller?
3. Port 389 is essentially LDAP in plain text - if I choose port 636 (LDAPS) - it fails.  How do I secure comms to the Domain Controller?

New to the World of SmartZones, so forgive me for the basics..

Cheers, James

[Anonymous]

I just got off the phone with Ruckus to figure this out as well.  For starters, the second answer given to you here is just weird/wrong, don't go that direction with running lpd.exe on the AD server.

What follows relates to release 5.2.0.0.699.

1. How do I actually add AD users or groups to 'Administrators'?

Review pages 426-427 of the Ruckus SmartZone 100 and Virtual SmartZone-Essentials Administrator Guide, 5.1.2.  Where I got stuck though is they had a typo on the AD Group name you have to create which I'll highlight below.

So here's how it works, and if you ask me, this is retarded compared to the way ZoneDirector did it, but at least it gets us back to what we had before.

Under Administration -> Admins and Roles, do the following:

AAA Tab:
 - Setup an AD entry just like you have listed above with Default Role Mapping off, port 389.

Administrators Tab:
 - Create a local user on the SZ, for example call it "SuperAdmins".  Put in some crazy long and difficult password as this will NEVER be used for actually signing.  It doesn't even matter if you remember it afterwards.

Groups Tab:
 - Create a group (Example call it "Super Admins Group" with all rights) and then assign the user you just created to this group (in this case, assign the user "SuperAdmins" to this group.)


Back on your AD server, do the following.
   - Create a group in AD called "Ruckus-WSG-User-[username]" (this is the typo on their docs, they have it listed as "Ruckus-WSG-[username]" which is wrong.)
      - As example, create the group "Ruckus-WSG-User-SuperAdmins"
   - Assign the users to this group that you want to have Super Admin Group access.

Back to your SZ, go to the AAA tab and test with a user, and it should be assigned the "Super Admin Group" (or whatever) Role.


2. How can I add a second Domain Controller?

- You can't for AD (currently.)  You can for Radius, but not for AD.  How fun!


3. Port 389 is essentially LDAP in plain text - if I choose port 636 (LDAPS) - it fails.  How do I secure comms to the Domain Controller?

- You can't.  We apparently lost that security feature in SZ.  You can have TLS encryption when you use AD for standard user authentication such as to authenticate to a portal, but not for the Administrator login to the web site.  Brilliant, right?  All we can do is complain to gain this feature back.

[peter_riederer_]

Thank you so much for this easy and simple explanation. Pity i didnt find your post earlier!

[Anonymous]

This comment should be starred and giving 200 thumbs up. Thank you so much for laying out those instructions so simply. The online knowledge base for VSZ has been so frustrating to dig though and it seems they have majorly over complicated these processes compared to how they worked on the ZD. THANK YOU!

[Anonymous]

Do you know if this process work for 6.0 ?

[Anonymous]

I found this topic accidentally and it reminded my unsuccessful fight for getting the AD-authentication working for management over a year ago for our vSZ cluster 5.1.2.0.302. I also had a ticket open then but it turned out that AD/LDAP is barely supported.

I would like to upgrade to 5.2 and then try once again if there are any changes and perhaps look for the above posts in this thread but I thought I'd put here some moments from the ticket as copy-paste's that I wrote then since I did some extensive testing to get it working and found "interesting" things. This is my first experience with Ruckus and it was a brand new setup.

1. The Administration\Admins and Roles\AAA server with type LDAP and the dialogue window has two mistakes:
1.1. "Admin Domain Name" is wrong, it is actually "Admin Distinguished Name" or shorter "Admin DN" as I saw here: 

https://support.ruckuswireless.com/articles/000009128?_ga=2.49082158.94637583.1577430772-1372812910....