Hi there, I’ve been trying to integrate Okta SSO using saml I’ve faced errors trying to directly redirect from the Okta app or using the raw link to access directly from the browser.
Process followed to find the issue:
Followed the Opensearch documentation to enable saml in the OpenSearch cluster and the Dashboard.
After some errors I’ve found the [BUG] SAML endpoint still using _opendistro instead of _plugins and finally after setting this I was allowed to log in from the URL of the services where we set. But in the other hand when I try to log using the APP in Okta portal it redirects me into https://myservice.com/_opendistro/_security/saml/acs but showing and 500 Internal Server error. Opensearch-dashboard logs below:
Checking in the forum we have seen that if we use https://myservice.com/_opendistro/_security/saml/acs/idpintiated in the url as Anthony says it works from the Okta APP but not directly from the link, throwing similar logs as before.
When I was using Opendistro the two ways were available using https://myservice.com/_opendistro/_security/saml/acs you could login vie Okta APP or from the link.
Do you know if this is the normal behavior in OpenSearch or if there may exist a bug?
Using this config I am able to login coming from APP in OKTA and opensearch url (in my case localhost:5601).
If you have the same setup but still not able to connect via either of the methods, can you please post your opensearch_dashboards.yml and config.yml (feel free to redact any sensitive details)
Hi @Anthony thanks for the response an sorry for the late reply. In Okta I have a similar config as yours but Requestable SSO URLs check the picture below
@jhaos The config seems ok, similar to mine, I don’t have the exchange_key, but this shouldn’t have impact. Can you try adding the Requestable SSO URLs pointing to …/saml/acs
Hi @Anthony it seems is working adding that option in the Okta dashboard, correct me if I’m wrong but I understand now that option is like an alternative URL to give the access right?