<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
0D54z00007eRCKGCA4Okta Classic EngineSingle Sign-OnAnswered2024-04-16T12:59:15.000Z2022-05-16T10:52:18.000Z2022-05-17T17:39:29.000Z

j03xj (j03xj) asked a question.

How to setup OKTA Auth for self-hosted elastic stack

I have a self-hosted elastic stack on google cloud and I wish to integrate Okta for SSO and authentication but I keep running into errors accessing the SSO page via the URL. Every time I go through my URL with the path /api/security/v1/saml, I get an error page API loader of "{"statusCode":404,"error":"Not Found","message":"Not Found"}

". But If I run my URL with just the / path, I access the application, which means the SSO page did not get to me as I wanted.

 

Could someone please advise on the best cause of action?

 

For some contexts, I have a K8s ingress where this is running and the path is also updated in the manifest file as required and the elastic.yaml file while following the configurations here https://nettweets.com/2019/08/22/integrating-kibana-in-elastic-cloud-with-okta-step-by-step/

 

I'd appreciate any help.


This question is closed.
Loading
How to setup OKTA Auth for self-hosted elastic stack