11-13-2015 02:26 AM - edited 03-10-2019 11:14 PM
Hello,
I´m implementing ISE 2.0 for wireless environment and I´m having problems with sponsor portal and certificates portal.
I would like to use the "https://ISE_Policies_FQDN:8443/sponsorportal/" as I have seen in different manuals for older versions, but I always get the response "404 Resource not found". I also tested with IP address instead of FQDN and different ports (8000, 8444.....).
I wouldn´t like to create a new FQDN domain name for every of this pages I have to create.
But in ISE 2.0 manuals doesn´t seem to be possible to use the ISE policies server FQDN in sponsor portal:
Enter at least one unique FQDN and/or hostname for
your Sponsor or MyDevices portal. For example, you
can entersponsorportal.yourcompany.com,sponsor,
so that when the user enters either of those into a
browser, they will reach the sponsor portal. . Separate
names with commas, but do not include spaces
between entries.
If you choose to update the default FQDN, you should
also do the following:
• Update DNS to ensure that the FQDN of the
new URL resolves to a valid Policy Services
Node (PSN) IP address. Optionally, this address
could point to a load balancer virtual IP address
that serves a pool of PSNs.
• To avoid certificate warning messages due to
name mismatches, include the FQDN of the
customized URL, or a wildcard, in the subject
alternative name (SAN) attribute of the local
server certificate of the Cisco ISE PSN.
Does anybody knows if it is mandatory to create a new FQDN for any of the sponsor or certificates pages I want to create??
Is it possible to use the ISE policies server FQDN for this pages??
Thanks.