Basically I would like to extend the guest registration form by adding new fields and adding some custom business logic used to implement the validation of these fields.
More in details a guest should provision him self by providing also the badgeID received at the reception and by providing the organizational unit of his sponsor and then the "guest portal" should ensure the the value provided by the guest are valid by checking against some external system (ldap and a database).
I know these are quite special requirements and usually "legacy web application" cannot be extended in this way because it's very difficult: I would like to know what is the best way to implement these special requirements to implement extremely custom "Guest provisiong" in a Cisco environment.
Why not have the receptionist create the guest account for them and hold them accountable for creating the usernames in that specific format? The purpose of guest management and the guest portal is to force some sort of AUP and identity of the guests as they enter the network. You can modify the fields in the portal to include what you are wanting them to enter....
For example you can create the username based on the email address they provide their first and last name, under the username settings. However, you can modify the first name and last name field to have the guest enter the fields you want so the username can be constructed from that.
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...