<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
0D51Y00009mPUYbSAOOkta Classic EngineIntegrationsAnswered2024-04-16T10:10:43.000Z2020-10-21T16:45:18.000Z2020-10-22T18:17:44.000Z

kw7fz (kw7fz) asked a question.

Does Okta Saml2p Single Sign On always generate an entityId starting with http and not https in the metadata?

Our Service Provider failed to integrate with our client's Okta IDP due to the IDP's EntityID being insecure, (starts with http and not https). Is there a way to make their EntityID begin with https?


  • User15851122134349081871 (North Central-Enterprise)

    The EntityID string should be whatever the person configuring Okta enters it to be; Okta doesn't even require it to be a real URL, it just needs to be whatever the SP is expecting.

    performance_new1

This question is closed.
Loading
Does Okta Saml2p Single Sign On always generate an entityId starting with http and not https in the metadata?