<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009u1CyyCAEOkta Classic EngineAuthenticationAnswered2026-06-04T21:46:49.000Z2023-12-13T16:53:29.000Z2026-06-04T21:46:49.000Z

12n9q (12n9q) asked a question.

Confluence landing page showing error

Hi Team,

When we are trying to open Confluence from the tile of the okta we are unable to get the landing page and getting a page not found error. when we are trying to open Confluence using a URL without Okta it's working fine.

We have raised a Atlassian ticket below is the reply from them.

---->As part of Atlassian’s commitment to Trust and Security, regarding CVE-2023-22522, the latest Confluence versions will no longer allow JSP files to be loaded from the <confluence-install-dir>. Any custom JSP file placed in the <confluence-install-dir> must now be converted to Velocity .vm file format. Corresponding apps that attempt to load customized JSP file(s) must be updated to refer to the converted .vm file.

Based on the affected URL, it appears that Okta is trying to load a JSP file at runtime, which would result in the action being blocked and causing users to encounter a 404 error.

You can find more details regarding this behavior change in the following article:

  • Resource name must end with .vm, .vmd, .css or .xml error after Confluence is upgraded

Please share the above information with the Okta Support team. Okta support team will need to review where in the IDP they are redirecting the authentication back onto <confluence-base-url>/okta_acs.jsp and have this updated to:

  • Either <confluence-base-url>; or
  • A new implementation that does not use JSP but velocity such as <confluence-base-url>/okta_acs.vm

 

Thanks,

Indra


  • Paul S. (Okta, Inc.)

    Hello @12n9q (12n9q)​ Thank you for reacting out to our Community!

     

    We apreciate you bringing this to our attention, our engineering team is aware of this matter and are working to resolve it, this matter is tracked internally under ticket OKTA-674540.

    Please keep an eye on release notes and see when this has been resolved.

     

    Community members help others by clicking Like or Select as Best on responses. Try it today.

     

    Ask Away: OIG Product Experts Answer Your Questions Thru Thur., Dec 14

     

    Earn Today: New Okta Community Badges Have Arrived 

    Expand Post
    Selected as Best
    • GrishaL.15276 (Schrodinger)

      Hi @Paul S. (Okta, Inc.)​, I see in the release notes for 2024.01.0 that OKTA-674540 is resolved. And indeed, the SAML instructions page for our Confluence on-prem apps now has an okta_acs.vm file to use in place of okta_acs.jsp.

       

      However, the redirect from Okta is still to the old <confluence-url>/okta_acs.jsp URL. Should we expect the integration to be updated at some point so that it redirects to <confluence-url>/okta_acs.vm instead?

       

      (As a workaround, I've added a 307 redirect from the .jsp to the .vm location on my deployments)

      Expand Post
    • Hi @Paul S. (Okta, Inc.)​ ,

       

      Like @GrishaL.15276 (Schrodinger)​ said even after applying the latest configuration, Confluence still redirects us to okta_acs.jsp instead of .vm

       

      Any workarounds or fixes for this?

      Expand Post
    • 7hcmd (7hcmd)

      We are getting the same error. Has the fix worked for anyone?

      • No.... and this is getting outrageous as most probably this redirect is being done somewhere in the JAR file, but they forgot to change the path in the app as Confluence tries to redirect the users to okta_acs.jsp even that most probably we all created the okta_acs.vm

         

        @Paul S. (Okta, Inc.)​ - any updates?

        Expand Post
      • Paul S. (Okta, Inc.)

        Hello @User16824474792767951389 (Customer)​  From what I can see engineering are still working on this matter. I would recommend to reach out to Support if you require additional assistance with this issue.

      • si89l (si89l)

        According to the Atlassian tech I'm working with, an Okta rep on another ticket said to get rid of the Okta files and use the SSO for Atlassian add-on. I have tried that, but then SSO doesn't work at all. I have looked through the .jar and do not see any mention of the .jsp.

    • AlexL.88292 (Customer)

      Hey all, we were able to get it resolved with the help of Okta support rep assigning another version of the Confluence onprem to our Okta tenant. It now redirects correctly to the okta_acs.vm file.

10 of 17
This question is closed.
Loading
Confluence landing page showing error