I have recently aqquired a Cisco ASA device with the intention of setting up a CLientless SSL VPN Portal.
My question is, can i control who has access to which portal page via LDAP Group membership?
For now, we have a staff portal at device.domain.com/staff
a computing portal at device.domain.com/computing
I would like to only permit members of the Staff group access to the staff portal and only memeber of computing to the computing portal.
I have LDAP authentication working ok for both profiles and i applied LDAP Attribute Maps that mapped the memberOf attribute to the IETF-Radius-Class attribute on the ASA, but i am not sure i am doing it correctly!
I did go through that link initially. As far as i understand it, that works by applying a specific grou policy to an AD group, but id didn't seem to stop otehr groups from being able to access that profile too.
What i ended up doing is defining a separate AAA Server group for both the staff and computing profiles and changing the BASE DN in the LDAP lookup to be the Staff and Computing OU's respectively, That way, if a user is not in the Staff OU in AD, they cannot authenticate against that profile,
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...