You are here
SEC0283 - ISE 2.2 Guest Access with Self-Registration (Part 1)
Difficulty Level:
Lab Document:
<Please login to see the content>
Category:
Security
Video Download:
Title: SEC0283 - Video Download $14.00
The video shows the third guest access deployment model on Cisco ISE 2.2 called Self-Registration guest. We will continue with our configuration from the previous lab and add guest ability to create an account. We will explore both automatic and manual account approval. At the end, we will allow guest to register additional non-user devices via device registration.
Part 1 of this video covers configuration and testing with auto-approved account
Topic:
- Guest Workcenter
- Guest Settings (Account Purge, Custom Field, Email Settings, Location/SSID, Username/Password Policy)
- Endpoint Identity Group
- Guest Type
- Guest Portal
- Guest account approval
- Sponsor Portal
- Authentication Policy (WLAN MAB)
-
Policy Element Result
- Authorization (Named ACL)
- Authorization (Authorization Profile)
- Authorization Policy
- Device Registration
About Author
Metha Chiewanichakorn, CCIE#23585 (Ent. Infra, Sec, SP), is a Cisco networking enthusiast with years of experience in the industry. He is currently working as a consulting engineer for a Cisco partner. As a founder of and an instructor at labminutes.com, Metha enjoys learning and challenges himself with new technologies.
3 comments
Guest Email approval using office365
Hello Metha,
Hope you are doing great!
Is it possible to use office365 email account to send/relay approval/password on self registration portal to the guest end user ?
Thank you.
Guest Email approval using office365
We don't see how that would be a problem. The sender email address is configurable. All that required is a valid outgoing SMTP server ISE can point to.
Guest Email approval using office365
Hello,
Because i could authenticate the account to smtp.office365.com on port 587 without enabling TLS/SSL checkbox successfully, but whenever i make a self registration, the portal shows that's the ise couldn't send the mail.
Does that i mean i need to point the ise to MX record of that client domain smtp ? or that account hasn't relay permissions ?
Thank you in advance.