<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
0D54z00008biDy6CAEOkta Classic EngineSingle Sign-OnAnswered2024-08-11T09:04:05.000Z2022-12-29T22:36:58.000Z2022-12-30T17:34:05.000Z
  • DonF.81354 (Customer)

    Hi Thanks for the question! I took a look at this and I cannot seem to find anything that indicates that this is Okta owned.

     

    Do you have a “Report-URI” integration configured in your environment? You find the link here Report-URI Integration Information and here Report URI

     

    A quick overview seems to indicate that this tool might employ Content Security Policies and perhaps in your case, they may be named “Oktacsp”? I am reaching a bit with that conclusion, but based on the domain, it would appear to be related to “Report URI”.

     

    I would also state that if your users are not experiencing any outages in relation to Okta (coming from your company owned network), and your agents are working well, then this is most likely not a core feature of Okta being blocked, but might require further investigation internally (outbound vs inbound, origin IP, traceroute, flow logs, WireShark, etc.)

     

    Please do let us know what you find and we would be happy to assist. Thanks!

    Expand Post
This question is closed.
Loading
Unknown okta site access requests