Skip to content
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

Geoserver Security JDBC as role service option #562

Closed
ghelobytes opened this issue Oct 23, 2024 · 3 comments
Closed

Geoserver Security JDBC as role service option #562

ghelobytes opened this issue Oct 23, 2024 · 3 comments

Comments

@ghelobytes
Copy link

Geoserver Security JDBC

The classic Geoserver has an option of creating a role service using JDBC. This option is not currently available on Geoserver cloud. Is there an architectural difference between the two (classic vs. cloud) that's why this isn't available by default?

Is it possible to add this option to Geoserver cloud?

So far I tried to add it as a dependency in pom.xml as indicated here https://github.com/camptocamp/geoserver-cloud-geoserver/packages/2022730 but that didn't really seem to work:

<dependency>
  <groupId>org.geoserver.security</groupId>
  <artifactId>gs-sec-jdbc</artifactId>
  <version>2.26.0.0</version>
</dependency>
Geoserver classic Geoserver cloud
@groldan
Copy link
Member

groldan commented Oct 25, 2024

Hi @ghelobytes, indeed both the JDBC and LDAP security plugins aren't integrated. No reason other than having not needed them so far.

I just did, one this pull request #564 is merged you can try with the 1.9-SNAPSHOT docker images.

@ghelobytes
Copy link
Author

Hi @ghelobytes, indeed both the JDBC and LDAP security plugins aren't integrated. No reason other than having not needed them so far.

I just did, one this pull request #564 is merged you can try with the 1.9-SNAPSHOT docker images.

Thank you! I'll give this a try for sure. Is there a general guidelines/pattern on how to add plugins/extensions?
Or is it unique or a case to case basis?

@ghelobytes
Copy link
Author

ghelobytes commented Oct 30, 2024

The PR #564 by @groldan has resolved this issue. Thanks a lot!

Just a note that it will be even greater if we can figure out a guidelines/patterns/steps on how to port over plugins/extensions.
Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants