Fix #12504 - Migrate to GeoStore 2.6#12518
Conversation
|
here @mahesh-wor the update for 1.6 with documentation changes too |
Thank you will go through and and update the configuration changes on #12459 accordingly. |
tdipisa
left a comment
There was a problem hiding this comment.
@offtherailz
I would like to review the structure of the OIDC paragraphs. At the moment OpenID connect, Google, Keycloak seems three different things:
Since Google, Keycloak are both examples of the same OIDC connect but for different providers they should be at the same level of the example we provided for Entra .
|
i ran a local setup with
I tested login, role assignment and it's working well. @offtherailz @tdipisa Once you have this PR merged, i will update #12459 and we can proceed with the implementation in dev/qa. |
tdipisa
left a comment
There was a problem hiding this comment.
@offtherailz there are failing checks now. Can you please check?
|
The cause of this failure is unclear, it looks to be generated randomly For this reason, to split this changes from something that looks to be more related to particular execution cases, I created And going to block this on #12526 |
|
thank you @mahesh-wor We improved also di entra doc please take a look. |
|
hi @offtherailz i checked the updated docs, looks comprehensive.
|
@mahesh-wor we will have to review this once merged, I guess. |
|
Successfully created backport PR for |



Description
Aligns MapStore with GeoStore 2.6's new dynamic OIDC provider mechanism and documents the migration path for users and custom projects.
Changes
applicationContext.xml(framework + project template): add ignoreInvalidKeys=true to the order-10 PropertyOverrideConfigurer so oidc_providers can be set directly in mapstore-ovr.properties without causing a startup failure.Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
Fix #12504
What is the new behavior?
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information