Okta Authentication conflict with InterSoft's File Upload Control
We have a web application that uses some of InterSoft's controls, http://intersoftsolutions.com/. We have one customer that also uses your Okta authentication SSO. When we try to use InterSoft's FileUploader control, only the first 48kb are uploaded. We have other customers without Okta where it works just fine and if I remove the okta module reference in web.config the files upload fine.
I have worked with InterSoft's support and this is what they said, "Hi Ryan, our preliminary test shows that Okta http module redirect the response and thus stop giving the response bytes to the other modules. We think this should be better addressed by the Okta's guy.
Have you tried to reach their support? Do they have a way to bypass their process based on a whitelist URL? Or perhaps based on certain rules. If they do, we can look into this further and setup something that satisfy their rules, or rules that configured by end developers."
What else do you need from me to be able to figure out a solution?
I'm not familiar with what the "Okta http module" you reference is. Is that an InterSoft module? A module that one of your customers wrote?
Also I'm not clear what files you're trying to upload with the FileUploader and whether or not you're trying to upload to Okta, or download from Okta. What is type of data you're trying to move?
From InterSoft's response to you: "Do they have a way to bypass their process based on a whitelist URL?" Sounds like they may not be authenticating correctly to get that data, or some other problem on their end. But until I can better understand what you're trying to do, I'm not 100% sure.
The "Okta http module" that I refer to is your product. It is your SAML SSO dll that we use in our web application. It is blocking a 3rd party control (InterSoft) that allows users to upload files to our IIS directory. Does this make sense?
Ok. This sounds like there's a SAML configuration problem somewhere and some link in the chain is not authenticating properly. There are several possible causes for this, so I'd recommend opening a case with support to see if they can better help determine the root cause. You can do that here: https://support.okta.com/help/open_case
My name is Wafi, I'm an Escalation Engineer with the Okta Support team. Wils is correct, this should really be looked at by our Support team to get a better undertsanding of where this is falling over and the best path to resolve it.
You mentioned that you are working with an Okta customer. Can you please have that customer open a support case with us? Once we have the case, we can work with them and you through that case to determine the best path forward. Thanks!