BasitM.18927 (Customer) asked a question.
Hi,
I made my application SAML enabled. Integrate it with OKTA and check it locally with Single Sign On and Single Logout. It was working fine. Then I deployed the application on the Azure Server. Which is our Proto server. I configure the application in OKTA with respect to the Proto server URL. On localhost it was http. But on Proto it is https. Anyways. now when I open the application URL. I got the OKTA login page. After entering username and password. When I click on the Sign In button. I got 404 error.
But when I click on the application icon in OKTA.
I successfully login into the application. Now there is no error.
Now If I logout from the application. I come to my login screen
Now if I click on Login with OKTA button. I get the 404 error
Any idea why it is happening? Either it is a CORS problem ? IIS problem ? Do I need to allow some URL ?
Is there any difference while login from OKTA by clicking on the application or from my application on proto?
Thanks
Hello, my name is Catalin from Okta Support, your problem requires some troubleshooting and this cannot be done on the Help Center - Discussions page. To properly handle your issue please proceed in creating a case with the exact information you provided above. You can create a case by clicking Get Support (in the bottom right part of the screen) followed by Open a Case.
Thank you.
Hi, Thanks for the reply. The problem has been resolved. Actually it was my mistake. What was happening that on the client application we provided the page where client can copy and paste the Single Sign On URL, Issuer etc from OKTA. For the Single Sign On URL, we provided the input type text filed on the user interface. The text filed length was 100 like <input type="text" id="username" name="username" maxlength="100" />. The Single Sign On URL that OKTA provided had 105 characters. So when I copy paste the text in this field then the whole URL was not pasting. The last 5 characters were lost. On my local development the URL was less than 100 characters so it was working fine.
As URL was invalid that's why when I was trying to login from the application then I was getting No Page Found error. Or you can say from Service Provider side I was getting Page not found.
But from OKTA or from IDP side. The OKTA was using the correct Single Sign On URL that's why from OKTA it was working fine.
Anyways when I fixed the input text length then URL became right and problem resolved. It took my whole day to find such a silly problem. But anyways hopefully this answer will help others too, if some one face the same situation.
Again thank you so much for your reply 🙂