a_cutler2 asked a question.
We are experiencing an issue where checking out a Catalog Item and enabling either License Check or Advanced License check causes App Broker to completely freeze and therefore fail the checkout processes. The connection to FNMS appears to be working just fine in every other area of App Broker. Any ideas why this might be occurring? Screenshot shows the view that freezes up when we try to check out.
We have tried it during multiple different times of the day and it consistently happened so I don't think it's related to a reconciliation. This is on 2019R1. Actually looking at the FNMS Integration log did shed some more light on what the issue is related to - the log shows the message "The provided URI scheme 'http' is invalid; expected 'https'" in many places, which is an error I have run into before with this customer in the App Portal UI. The first time I ran into the error it was caused by a WebAPI.config file for FNMS that included entries for serviceURL that were http instead of https, so I changed the config file to use https instead and the problem was resolved. Now it appears that there may still be some parts of the configuration trying to use http that I will need to identify and fix.
Strictly from an App Portal/FNMS integration perspective, here are places to look (assuming you're using the Flexera Service Gateway):
We have tried it during multiple different times of the day and it consistently happened so I don't think it's related to a reconciliation. This is on 2019R1. Actually looking at the FNMS Integration log did shed some more light on what the issue is related to - the log shows the message "The provided URI scheme 'http' is invalid; expected 'https'" in many places, which is an error I have run into before with this customer in the App Portal UI. The first time I ran into the error it was caused by a WebAPI.config file for FNMS that included entries for serviceURL that were http instead of https, so I changed the config file to use https instead and the problem was resolved. Now it appears that there may still be some parts of the configuration trying to use http that I will need to identify and fix.