-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace _opendistro route with _plugins #895
Conversation
@davidlago Could you have a look, please. |
This is a breaking change. Even though lagging behind the documentation, we should add the new named endpoint (and preserve the old one as deprecated). We can remove when 2.0 goes out. |
Makes sense. Do you know of a functionality to have multiple |
It looks like it is just a single value: https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/src/core/server/http/router/router.ts#L58 |
Ok, then I will try to figure out a way to move the handler function into a separate function. Only problem I see is that we would need to bind the |
UTs failing and it looks like this change that was breaking in 2.0 is affecting us here. It should be a quick fix, making the |
Please provide details as to how this was tested, thanks! |
Sorry for taking so long. |
@pc-jedi thanks for the help! I am sorry for the back and forth, but we are already starting to build 2.0 in |
8d9426e
to
b4362b6
Compare
@davidlago No worries. I have rebased and squash all things together. All routes should now be |
I guess the integration test failed, because this plugin was just bumped to 1.3.0 and Dashboards 1.x branch is already at 1.4.0? I think we have to wait for #892 |
Any timelines when the PR will be merged? |
There is a new PR for 2.0.0.0 bump: #928 |
Signed-off-by: Christian Düfel <[email protected]>
Rebased. Please have a look again. |
Any plans to merge this so we could have this still in for 2.0? Or is it already too late? |
This build can be re-run once #989 is merged. |
Last build went through. Should I bump it again to latest |
FYI: this is breaking change and was included in minor version 2.1.0. Not sure if this is good practice. For minor version both endpoints ( |
@cliu123, @peternied we also need to make corresponding changes in the |
@cliu123 @peternied are we working on fixing this? Seems this is breaking the SAML flow currently |
This reverts commit e4e4032.
…)" (opensearch-project#1035) This reverts commit e4e4032. Signed-off-by: Vasile Negru <[email protected]>
…roject#895)" (opensearch-project#1035)" This reverts commit c456883362610c61fcc5d54b2974d7a5c6327c1d. Signed-off-by: Vasile Negru <[email protected]> Signed-off-by: Vasile Negru <[email protected]>
…)" (opensearch-project#1035) This reverts commit e4e4032. Signed-off-by: Vasile Negru <[email protected]> Signed-off-by: Vasile Negru <[email protected]>
…roject#895)" (opensearch-project#1035)" This reverts commit c456883362610c61fcc5d54b2974d7a5c6327c1d. Signed-off-by: Vasile Negru <[email protected]>
Description
In the documentation for SAML the SSO URL and the white listed URL is already updated to
_plugins/_security
while the routes in the security plugin still are on_opendistro/_security
. That causes a 404 response when trying to login.This PR changes the route in the plugin and aligns with the documentation.
Category
Bug fix and Documentation
Why these changes are required?
To align with the new naming schema and have it working like it is documented.
What is the old behavior before changes and new behavior after changes?
Before this PR the whitelisted URLs for SSO have to be set to
_opendistro/_security/..
also the configuration in the IdP to forward to the correct endpoint had to be_security/saml/acs
.New behavior is that the URLs are now aligned with the documentation.
Issues Resolved
#836
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.