Timeline for How to use an existing database to authenticate users in GeoNetwork
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 10, 2023 at 10:20 | history | suggested | Campa | CC BY-SA 4.0 |
update broken link
|
| Mar 10, 2023 at 10:06 | review | Suggested edits | |||
| S Mar 10, 2023 at 10:20 | |||||
| Jun 17, 2014 at 9:04 | vote | accept | webrian | ||
| Jun 11, 2014 at 14:24 | history | edited | María Arias de Reyna Domínguez | CC BY-SA 3.0 |
added 143 characters in body
|
| Jun 11, 2014 at 14:22 | comment | added | María Arias de Reyna Domínguez | Remember that geoNetwork uses spring-security. If your app also uses this, maybe you can connect them. If you are trying to use a real production geoNetwork with existing users, I strongly advice you to move to some authentication/authorization system like LDAP instead of using your own. | |
| Jun 11, 2014 at 10:09 | comment | added | webrian | Yes, I'm talking about a customized user database. Currently the most promising solution is to work with views and a custom PasswordEncoder and / or to rewrite the user services and configure these custom services in config.xml. | |
| Jun 11, 2014 at 7:36 | history | answered | María Arias de Reyna Domínguez | CC BY-SA 3.0 |