BUG? ISE Sponsor Portal Login Preview Does Not Show Banner Title

[Scott Gillies]

Tested on ISE 2.2 and 2.4.

Have I found a bug?

On the ISE Sponsor Portal Login Preview it does not display the Banner Title, just the Logo.

When you select the Desktop Preview it also does not display the Banner Title, just the Logo.

If you browse to the Portal test URL it does display the Banner Title.

The problem comes if you cannot access/browse to the Portal test URL e.g. it can only be accessed from a customer network which you remotely manage and therefor cannot DNS resolve the Portal test URL.

Other Portals I have tried do not have this Preview issue.

Is this a bug or a feature?

[Jason Kunst]

Other portals like what? My devices portal? This maybe issue with DNS and interface NAT etc. Did you try it from same network and does it work fine? If think a bug then work through with TAC

[Scott Gillies]

Hi Jason.

This is nothing to do with DNS or NAT...

Taking your example of MyDevices Portal: As you'll see when I am configuring the Portal under the 'Portal Page Customization' tab the 'Banner Title' appears in the 'Preview' and also on the 'Desktop Preview' (below). Hence, I have confidence that this is how it will appear when my customer uses the My Devices Portal.

On the Sponsor Portal under the 'Portal Page Customization' tab the 'Banner Title' does not appear in the 'Preview' nor does it appear on the 'Desktop Preview' (below). Hence, I am not confident that this is how it will appear when my customer uses the Sponsor Portal and (because of firewalls and other security) I cannot remotely browse to the Sponsor Portal to confirm the user experience.

I have checked on my Lab model that when I browse to the Sponsor Portal the Banner Title does indeed appear though.

The bug I am pointing out is the fact that on the Sponsor Portal 'Portal Page Customization' page the Preview does not contain the Banner Title. This is inconsistent with the other Portal 'Portal Page Customization' pages I have looked at on both ISE 2.2 and 2.4.

I don't wish to raise a TAC case for this as it does not affect my customer. Hopefully a Cisco person reading this, like yourself, could highlight this back to the ISE development team....