Access systems are messy. Wait, let me rephrase that, Poorly planned access systems are messy.  We’ve all seen it happen a thousand times. Someone comes running into the security cave

Demanding Admin: “We have a new web property going up and I need to give remote admin access to the team at the north pole! Santa must have access!”

Security Monkey: “Ok, does anyone else need access?”

Demanding Admin: “Nope, just Santa.. oh and his elves. And maybe the Polar bear consortium. They are going to be blogging about the entire web experience”

Security Monkey: “Anyone else?”

Demanding Admin: “Nope, not at all. For sure.  Well, except for the secret project group A, but they only should have access to the subterminal C.  And we need to be able to create new users and eliminate old ones from the main auth system”

Security Monkey:monkey

“Apprehensive monkey is apprehensive”

It’s at this point, that we have should pick up the marker and start walking the system. It always makes more sense when drawn out. Well, most of the time.  Sometimes it ends up like a Picasso-like portrait that belongs in the Louvre.

photo So here is what we end up with.

All users hit the APM login page.
User logs in at AD AUTH:
Good credentials –> proceed to ROLES
Bad Credentials –>  DENY

ROLES
(check AD to find the user’s groups):
Admin –> Allow full admin access/resources
Blogger –> Give a protected path to blogs
Project A –> Allow into secret project A
No role –> DENY!

Easy Peasy Lemon Squeezy!  Lets get to it!

Making it Happen Captain:

Access the APM, click on Access Profiles, can click Create.

For our policy, we are going to give it a name and add english as the accepted language.

1
Now, Click edit on the policy and let the fun begin. 2
We click the plus sign and start picking the access path items. Logon Page first. 3
Next, we know we want to Authenticate the user against AD. We will need to specify an AD server here. 4
Define the AD Server that will be used here:
Access Policy –> AAA Servers –> Active Directory.  Define a Name, the domain that users belong to, and give it a domain guest account to connect with.
6
Now, we go back and add the ROLES Query. In the APM terms, we want an AD Query.   We will need to tell it a search filter.  For us, we’ll use the logon name:
(samAccountName=%{session.logon.last.username})
And, since we plan on setting the user’s primary groups, we’ll tell the query to fetch those.
7
Now to set the success paths, depending on group. Here we click on branch rules under the AD Query.  We need to know the group ID for this.  You can ping your AD admins, or if you have access, run the query against the AD Server:

C:\me>dsget group "CN=Group here" -sid
  sid
  S-1-1-11-000000000-0003009999-9876543211-130
dsget succeeded

The groups ID is:  130

8
We build all 3 branches here based  on the Primary groups. NOTE: we can also do “member of” or any number of other conditions. 9
Now we need to think about who gets what resources. Based on the requirements we are going to build the following:

Admin: Full webtop/Network Access
Blog: Simple Connectivity Access
Secret Project: Directed Network access

Start with the Network Access Settings:
Access Policy –> Network Access –>Create
Once you’ve named it, you have to edit the policy to define the network path. For us, we want a split tunnel (only send traffic for 1.1.1.0/24 through the tunnel).
10
Now we need a Network webtop for our Blog/Project Access. Click on Webtops->create.  Add a name and select “Network Access” 11
We also need a Full webtop for our admins. This creates an actual interactive webtop of all resources they can use. It’s a container for any Webtop Links we create (under Webtops->Links) 12
Sweet, now we can go back to the policy editor and assign out rights. At this point, we just add a Full Resource assignment to each path, and select the resources we want them to access.
Admin: Full webtop with links
Blog: monkeylink and monkeylink network access
Secret:  same as blogger, for now.
13
Last Policy change is to set the fallback for the success paths to Allow. 15
Finally, we apply the access policy to a virtual server, and boom,  APM in place. 16

 

So, it takes a bit of clicking to put it all in place. But once you have the foundation laid down, you can easily add new paths or make changes to current access roles.  I highly recommend that anytime you are going to make a large change, copy the current policy, and edit on the copy (better safe than sorry).

 

 

 

Comments on this Article
Comment made 25-Mar-2014 by B.Earp 185
Hi - thanks - great post. When you say "We build all 3 branches here based on the Primary groups." - What does "here" mean - it looks like you have deleted the "User Primary Group ID is 100" branch and added 3 new ones - but then there is a screen grab with you editing the "User Primary Group ID is 100" branch and changing it to 999 - but then that also disappears from your next screen grab.

Would you be able to clarify?

Thanks very much,

Ben
0