geonetwork / geonetwork/core-geonetwork

Metadata identifier templates with slashes "/"

Open
#7,733 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
521
Forks
514
Avg merge
6d 13h
Merged PRs (30d)
19

Description

In **GeoNetwork**, it seems that it's not possible to have metadata identifiers with slashes.
Some portals expect to have unique identifiers like `https://www.myportal.com::{{uuid}}`.
Setting up such a template from the [Metadata identifier template](https://docs.geonetwork-opensource.org/4.2/administrator-guide/managing-metadata-standards/metadata-identifier/) administration works.
But then, when creating a metadata with such a template, the editor service throws an error of type
```
org.springframework.security.web.firewall.RequestRejectedException:
The request was rejected because the URL was not normalized.
```

I am wondering what core developpers think about this issue.

1. Do you think it's ok to have such metadata identifer templates ?
2. Do you think GeoNetwork should support that ?
3. Do you think that it's a bug right now ?
4. Why has the URL to be normalized ?
5. Would you imagine other potential drawbacks of fixing this issue ?

Thanks a lot for your expertise :pray:

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the metadata creation flow with an identifier template containing slashes, then trace the editor service request to the Spring Security firewall rejection. No source files or tests are identified in the issue; done would require a decided scope for supporting these templates, documented behavior, and regression coverage for the accepted or rejected identifier format.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
backend, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.