iPSK on Azure WebAPP

[rodrigopcrj]

I'm implementing iPSK web part in a Azure webAPP, with an external MySQL Flexible server. I am facing some issues...
1- it's not possible for me setup different docummentRoot's, for each "adminportal" and "portals" as the Apache instructions. WebAPP uses Nginx. at least for testing, I edited the nginx default site file to root /home/site/wwwroot/adminportal. I can get to it and execute the installation until the point that it creates the iPSK database in the external Mysql server, but then it shows "not found"
I tried both ways, setting the root and letting it default and adding "adminportal/" to the URL, both ways end up the same "not found"

1. Question - Would it be any kind of incompatibility?
2. Question - in case I don't want to change the docummentRoot, the scripts would work if I just add "adminportal" or "portals" to the URL?

Thanks in advance.

[rodrigopcrj]

Another question, is it compatible with secure MySQL connection? if it is, how to make it to work?

[ciesinsn]

While you could try and hack things as you mention I think you'll run into some of the mod_rewrite and the non-admin portals. Is there any chance you can use the Docker container version of iPSK Manager and run in Azure WebApp for Containers?

As for the secure mysql connection the code would have to be modified to make the SSL conection.

[rodrigopcrj]

As I mentioned before, I cannot change anything out of the "/home" in Azure webapp due to not persistence of changes, that means that I cannot do any mod_rewrite.

I overcame the situation by having two webapps, one for "adminportal" and another one for "portals", and I put the content of each directory in their respective wwwroot and put "supportfiles" in /home/site, so the scripts could keep "../supportfiles/..." location.
This is the directory hierarchy: /home/site/wwwroot

a small change would be necessary to allow portals configuration to use HTTPS (443), which is not possible at the moment. I suspect that's because adminportal is using it and the application doesn't consider it will run in two different instances,

I know this doesn't prevent the portal to work but that will impact the output for the created portals:

Please, understand that although I have advanced Linux knowledge and good programming skills (not on PHP) and I am used to build solutions by creating or modifying stuff due to my previous job, the rest of the team doesn't have this background and I am an employee of a multi-national oil company that thrives for simplification, standardization and going cloud aiming to use cloud managed services whenever possible.

I appreciate the effort you put on maintaining this awesome tool!

[ciesinsn]

The comment I was making around mod_rewrite was about using nginx and possibly some items of the non-admin portals not functioning as that portal makes use of mod_rewrite in apache.

As for the port 443 you just need to add 443 as a option in the platform configuration section and then you can select it when defining a portal.

[rodrigopcrj]

Regarding the 443, actually it's already there, but it's not a selectable option under the portal configuration.

I see what you mean about the user portal, it doesn´t work...

[ciesinsn]

Are you sure its defined as I can select it on my instance. There should be nothing that blocks it as all its used for is building the URL that shown when you view the portal config and then use with ISE.

The rewrite rules are

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !(404.php)
RewriteCond %{REQUEST_FILENAME} !(favicon.ico|robots.txt)

RewriteRule ^(.*)$ index.php?portal=$1 [L,QSA]

The last one would take any URL and rewrite to to index.php?portal=$1 where $1 is the path user before re-write and any query params in original query.

This is part of the original code from the original author of this project and I don't know off the top of my head in what situations this may cause problems if it wasn't present. I was just making mention of it to you as there could be a issue.

[rodrigopcrj]

it is... it comes by default.

but in portals it's not selectable for me, as shown in the previous image.

[ciesinsn]

I am unfortunately not able to reproduce what you are seeing for the 443 port not appearing in the drop down within the portal configuration. I've tried a few different things to try and get to the same behavior and I am not able to. Do you have other portals configured? Does the db table for 443 look the same as the other ports? Just trying to figure out what is different.