<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
0D54z00009ZRrhCCATOkta Classic EngineIntegrationsAnswered2024-12-08T09:04:13.000Z2023-08-16T14:59:37.000Z2023-09-11T14:24:13.000Z

jwy5l (jwy5l) asked a question.

no manual for integration with IRIS Cascade (HR) how to get necessary parameters for OIDC/OAuth

Hi, I am trying to integrate our HR system with Okta, I got documentation from the Cascade team that suggests that we can do much more that the SWA integration available from the shop.

to quote:

 

"

Modern Authentication in Cascade can work with any external identity provider that supports OAuth 2.0 and OIDC standards. 

SAML is not supported.

"

as a list of prerequisites that I have to deliver, I got:

"

Authentication Provider(ie Azure, ADFS, Google, etc)

All providers must be able to supply 3 key pieces of information.

Authority Endpoint(URL)

Client ID 

Client Secret 

"

Now, 

how to create an OIDC bridge to get client and secret (I guess I can get endpoint from here: https://developer.okta.com/docs/concepts/auth-servers/*org-authorization-server ) without creating a local server, like for a native app?

 

I have to admit I am a little bit lost.


This question is closed.
Loading
no manual for integration with IRIS Cascade (HR) how to get necessary parameters for OIDC/OAuth