<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
0D54z00009yaCYCCA2Okta Classic EngineIntegrationsAnswered2025-09-13T09:01:51.000Z2024-01-25T19:28:55.000Z2024-01-26T15:37:11.000Z

MarcoL.56602 (Customer) asked a question.

SWA Authentication Details & Explanation

Hello,

 

We are currently in the process of implementing OKTA as our IDP in our School District. This said, we have a few question/s which we hope you can shed light on:

 

  1. What is SWA authentication to a service provider from OKTA and what is/are the step-by-step process for it?
  2. Given the set-up where Active Directory is the "source-of-truth" (authentication) for OKTA. For 3rd party service providers previously authenticating via LDAP from the same AD (prior to OKTA implementation) :
  3. Is it possible for OKTA to "pass-thru" user credentials to use for SWA since the service provider/s authenticate via the same AD/LDAP server anyway?
  4. Can OKTA act as an "alternate" LDAP source so 3rd party service providers can be pointed to OKTA instead of the on prem AD/LDAP server/s?

 

Thank you...any insight and/or clarification regarding these is most helpful.

 


This question is closed.
Loading
SWA Authentication Details & Explanation