<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
0D51Y00006qbQQsSAMOkta Classic EngineIntegrationsAnswered2024-04-26T14:35:38.000Z2019-10-25T19:46:34.000Z2019-11-09T02:55:28.000Z

s5e6u (s5e6u) asked a question.

Locally installed app no SAML, ADFS, or API method

We have a locally installed legacy app that does not have any API, SAML, or ADFS integration. We were told by a sales engineer that we would be able to still have Okta manage the passwords for this system. We've signed up for the 30 day trial, and I'm looking for some direction on how do have Okta manage and enter the username and passwords when the application is launched?


  • Does the locally installed legacy app reply on HTTP header name-value pairs? If yes, you can use mod_auth_openidc and Apache to translated Open ID tokens into HTTP header name value pairs.

    Selected as Best
  • Does the locally installed legacy app reply on HTTP header name-value pairs? If yes, you can use mod_auth_openidc and Apache to translated Open ID tokens into HTTP header name value pairs.

    Selected as Best
This question is closed.
Loading
Locally installed app no SAML, ADFS, or API method