ISE IPSK Manager Portal Issue

[zhenningx]

Hello, I installed the IPSK Manager. The Admin portal on port 443 is working and I am able to login the admin portal, but the end user portal on port 8443 always shows the 404 page. Also when I click Portals > Add Portal on the admin page, nothing happens.

Anyone has any ideas about this?

Thanks!

[Greg Gibbs]

My guess is that you've missed something in the Apache setup or configuration. I would suggest starting over from scratch and following the pre-requisites and installation steps exactly as per the GitHub project documentation.

If that still fails, you would be best filing and Issue in that project including as many details as possible in the description. This tool is community developed and supported and leverages multiple open source components, so there is no support from Cisco TAC.

[Nick Ciesinski]

Did you ever figure this out @zhenningx ?

For the non admin portals it will always show a 404 error unless you have the portal id in the url.  The portal id is gotten from the admin portal page view screen of a portal. 

The issue of clicking portal add and nothing coming up is it needs other configuration items created before you can make a new portal.  I recommend working your way backwards on the menu and do the add portal last.  Then it should pop up.  

Nick

[zhenningx]

Thanks @Nick Ciesinski for your suggestions. 

I checked other configuration items and did not find what was missing according to the instructions on the Github page. Can you be more specific which configurations are needed for this?

I installed ipsk manager on RedHat, and the Github instruction is for Ubuntu. Does this work on Redhat?

Thanks.

[Nick Ciesinski]

@zhenningx Redhat should be fine, it just hasn't been tested, but as long as you followed the setup items in the README for Apache, MySQL, PHP, it should be fine.  If you got through the installer of iPSK Manager then its a pretty good sign you did all those steps properly. 

The configuration I was talking about isn't in the README as it is application configuration.  You can't just make a portal as the first thing you do.  Within the application you have to configure other items that are used in the portal configuration. 

On the side menu start by creating a Wireless Network, then create a Authorization Template, then Endpoint Grouping, then Portal Grouping.  At this point when you attempt to create a Portal it should pop up to create. 

It is a item on the enhancement list to popup a notice saying you need these other things configured before you can make a Portal but the way the code is today it just doesn't display anything if you don't have the other items configured first. 

[zhenningx]

Thanks @Nick Ciesinski. I have created Wireless Network, Authorization Template, Endpoint Grouping, Portal Grouping. Then I am able to create a portal. But when I access the portal URL, the page displays a warning "Warning: Trying to access array offset on value of type bool in /var/www/iPSK-Manager/portals/index.php on line 104", and an unloaded image under the warning. Then I see my portal name and "Please Login" sign. After I login, the page displays "File not found. ".

Any ideas about this?

I hope Cisco can create an complete guide of setup and configure iPSK manager. I cannot find any guide which mentions the steps you mentioned in the above posts. And what about the "Cisco ISE ERS Integration Settings", do I need to configure this?

Thanks!

[Nick Ciesinski]

What are you using for the URL for the portal and what type of portal did you choose?  The portal pages work differently than the admin portal page and you need to format the URL properly otherwise the page will generate a 404 error which it sounds like you are getting with the broken image comment. 

If you go into the admin portal and the portals menu item you should see a view option next to each portal you made. Click that and use the URL it shows for that particular portal.  

As for ERS it is not required but it allows you to do things if you configure it. For instance when choosing to bulk import endpoints if you have ERS configured you’ll see an option to import endpoints from ISE endpoint groups.  You’ll also be able to see a button to create the ISE authorization profile.

The ISE monitoring integration is used for sending COA to reauthorize an endpoint.  

I would recommend configuring both but neither is absolutely required.  

[zhenningx]

Thanks @Nick Ciesinski for your reply. Yes I was using the Portal URL from the View Portal window and I had the issue above. The portal type is Captive Portal, and Authentication Directory is Internal, and the App Port is Https(8443).

Thanks.

[zhenningx]

Hello,

> If you go into the admin portal and the portals menu item you should see a view option next to each portal you made. Click that and use the URL it shows for that particular portal. 

Yes I used that URL, and I still sees the warning "Warning: Trying to access array offset on value of type bool in /var/www/iPSK-Manager/portals/index.php on line 104". After login from the portal, I still sees "File not found. ".

I have tested the portal type to be both Sponsor Portal and Captive Portal, and both internal and external authentication. The same results. Any ideas about this?

Thanks!

[Nick Ciesinski]

"Warning: Trying to access array offset on value of type bool in /var/www/iPSK-Manager/portals/index.php on line 104" is going to be a cosmetic message in the log since the SAML setting is probably not set.  It isn't going to cause things not to work. 

Captive Portals require more in the URL then what is shown when pressing view.  You should look at the documentation where it builds that URL in a ISE authorization response i.e. sessionId= and client_mac=

The Sponsor Portal would just use what is seen in the view screen and if that isn't working you either have a incorrect Apache configuration or, you used the wrong port in the portal config for a Sponsor Portal and when you copy the URL it goes to the wrong port because of that.

[bearman97]

I've been banging my head on this issue for a month, wondering if files are missing, or permissions in the container weren't allowing the portal settings to be written properly.  That tip about putting the portal ID in the URL would have been very helpful in the README.

From what I've been able to discover on my own I believe this will be a very useful tool in my environment.  However, the lack of centralized documentation and tips (like the order of completion for side-menu items) may be preventing others from fully adopting this software.  Is there a centralized wiki or community area where such documenation and tips may be found?

[Nick Ciesinski]

The only places where documentation exists currently is the old and now read-only community post (https://community.cisco.com/t5/security-knowledge-base/ipsk-identity-pre-shared-key-manager-portal-server-for-ise/ta-p/3904265) and the iPSK Manager GitHub page (https://github.com/CiscoDevNet/iPSK-Manager).  I've tried to move over most of the community documentation to GitHub but there is for sure more work that could be done.  If you'd like to help out, would be happy to take pull requests on the project for documentation. 

The discussion feature is also enabled on the GitHub page for people to ask questions etc.   I know its not what you are looking for exactly, but, it is what is there is currently.   The feedback is helpful as there has been a few questions about setup confusion on the order of completion so I've added a popup for a new installation to point this out.   

Sometimes you don't know what to improve unless feedback is given

[MHM Cisco World]

I send you PM 

MHM

[zhenningx]

After spending plenty of time, I am still not able to make this software working. I still get the "File not found. ". error after logging in the portal. Can Cisco do something to make this software more easier for people to setup and use? A complete video for the setup process would definitely help!